Re: [WiX-users] Version check for dll in compile

[Brian Rogers]

Everyone,

Sorry for the oversight on my part. Looking at his statement again:

To do:


The "Source" defines your local system during a compile, [SystemFolder] in
avaliable during an installation once the Package is running. WIX does not
using MSI properties while compiling the MSI.

I hope that helps clarify your statement:
Worked. But it fails the purpose of having [SystemFolder], which should have
checked for 32 or 64 bit versions.
Is there a way to check 32 or 64 bit version before compiling.
At this point I agree with Karthik. I would avoid using the System directory
as your source location. If possible, find a merge module and include it in
your build for these files so they are correctly installed.

Sorry for the oversight,

Brian

On 8/13/07, Brian Rogers <[EMAIL PROTECTED]> wrote:
>
> Hey Guys,
>
> I am not sure if this is what you are looking for, but I believe you can
> use [System64Folder] (
> http://msdn2.microsoft.com/en-US/library/aa372054.aspx ) to accomplish
> this feat.
>
> I would have to agree with Karthik, putting DLLs into the system directory
> can be a problem. I remember laying down that law at a company I worked for
> in the past. When at all possible keep your application's shared resources
> inside its installation directory. Unless it is architected differently.
>
> Hope that helps!
>
>
>  On 8/13/07, Karthik Krishnan <[EMAIL PROTECTED]> wrote:
> >
> > I'm no expert, but I can't imagine it is a good idea to use your
> > SystemFolder as a source. In our deployments, I usually make it a condition
> > : third party tools should be installed as prerequisites, with installers
> > provided (vb runtimes in your case).
> >
> > If you really need to have the files included, why not copy them to two
> > locations in your source directory, and use Msbuild. Set, say, $(dllsource),
> > then reference that within your wxs.
> >
> > If I had to take a stab in the dark, I'd say [SystemFolder] depends on
> > the context you are running under.
> >
> > K
> >
> > On 8/13/07, Ansuya Negi <[EMAIL PROTECTED] > wrote:
> > >
> > >
> > > Hi,
> > > I am using 64 bit machine and need to install few dlls.
> > > For files Msvbvm50.dll and Msvbvm60.dll:
> > >
> > > To do:
> > >  > > Source="[SystemFolder]Msvbvm50.dll" />
> > >
> > > Gave error:
> > > File of type 'File' with name '[SystemFolder]Msvbvm50.dll' could not
> > > be
> > > found.
> > >
> > > So used:
> > >
> > > 
> > >
> > >  > > Source="$(var.SystemSource)\Msvbvm50.dll" />
> > >  > > Source="$(var.SystemSource)\msvbvm60.dll" />
> > >
> > >
> > > light.exe : error LGHT0001 : Unknown error while getting version of
> > > file:
> > > C:\Windows\System32\msvbvm60.dll,
> > >
> > > system error: 2
> > >
> > > Exception Type: System.Runtime.InteropServices.ExternalException
> > >
> > > Stack Trace:
> > >at Microsoft.Tools.WindowsInstallerXml.Msi.MsiBase.FileVersion
> > > (String
> > > filePath, String& version, String&
> > >
> > > language)
> > >at
> > > Microsoft.Tools.WindowsInstallerXml.Binder.UpdateFileInformation(Output
> > > output)
> > >at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output)
> > >at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run (String[]
> > > args)
> > >
> > > - Finished
> > >
> > >
> > > So used proper system directory for 64 bit:
> > > 
> > >
> > >  > > Source="$(var.SystemSource64)\Msvbvm50.dll" />
> > >  > > Source="$(var.SystemSource64)\msvbvm60.dll" />
> > >
> > > Worked. But it fails the purpose of having [SystemFolder], which
> > > should have
> > > checked for 32 or 64 bit versions.
> > > Is there a way to check 32 or 64 bit version before compiling.
> > >
> > > Thanks,
> > > Ansuya
> > > --
> > > View this message in context: 
> > > http://www.nabble.com/Version-check-for-dll-in-compile-tf4264065.html#a12135302
> > >
> > > Sent from the wix-users mailing list archive at 
> > > Nabble.com
> > > .
> > >
> > >
> > >
> > > -
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a
> > > browser.
> > > Download your FREE copy of Splunk now >>   http://get.splunk.com/
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> >
> >
> > -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>   http://get.splunk.com/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
>

Re: [WiX-users] Version check for dll in compile

[Brian Rogers]

Hey Guys,

I am not sure if this is what you are looking for, but I believe you can use
[System64Folder] (http://msdn2.microsoft.com/en-US/library/aa372054.aspx) to
accomplish this feat.

I would have to agree with Karthik, putting DLLs into the system directory
can be a problem. I remember laying down that law at a company I worked for
in the past. When at all possible keep your application's shared resources
inside its installation directory. Unless it is architected differently.

Hope that helps!


On 8/13/07, Karthik Krishnan <[EMAIL PROTECTED]> wrote:
>
> I'm no expert, but I can't imagine it is a good idea to use your
> SystemFolder as a source. In our deployments, I usually make it a condition
> : third party tools should be installed as prerequisites, with installers
> provided (vb runtimes in your case).
>
> If you really need to have the files included, why not copy them to two
> locations in your source directory, and use Msbuild. Set, say, $(dllsource),
> then reference that within your wxs.
>
> If I had to take a stab in the dark, I'd say [SystemFolder] depends on the
> context you are running under.
>
> K
>
> On 8/13/07, Ansuya Negi <[EMAIL PROTECTED]> wrote:
> >
> >
> > Hi,
> > I am using 64 bit machine and need to install few dlls.
> > For files Msvbvm50.dll and Msvbvm60.dll:
> >
> > To do:
> >  > />
> >
> > Gave error:
> > File of type 'File' with name '[SystemFolder]Msvbvm50.dll' could not be
> > found.
> >
> > So used:
> >
> > 
> >
> >  > Source="$(var.SystemSource)\Msvbvm50.dll" />
> >  > Source="$(var.SystemSource)\msvbvm60.dll" />
> >
> >
> > light.exe : error LGHT0001 : Unknown error while getting version of
> > file:
> > C:\Windows\System32\msvbvm60.dll,
> >
> > system error: 2
> >
> > Exception Type: System.Runtime.InteropServices.ExternalException
> >
> > Stack Trace:
> >at Microsoft.Tools.WindowsInstallerXml.Msi.MsiBase.FileVersion(String
> > filePath, String& version, String&
> >
> > language)
> >at
> > Microsoft.Tools.WindowsInstallerXml.Binder.UpdateFileInformation (Output
> > output)
> >at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output)
> >at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
> >
> > - Finished
> >
> >
> > So used proper system directory for 64 bit:
> > 
> >
> >  > Source="$(var.SystemSource64)\Msvbvm50.dll" />
> >  > Source="$(var.SystemSource64)\msvbvm60.dll" />
> >
> > Worked. But it fails the purpose of having [SystemFolder], which should
> > have
> > checked for 32 or 64 bit versions.
> > Is there a way to check 32 or 64 bit version before compiling.
> >
> > Thanks,
> > Ansuya
> > --
> > View this message in context: 
> > http://www.nabble.com/Version-check-for-dll-in-compile-tf4264065.html#a12135302
> >
> > Sent from the wix-users mailing list archive at 
> > Nabble.com
> > .
> >
> >
> >
> > -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>   http://get.splunk.com/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
Brian Rogers
"Intelligence removes complexity." - BR
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Version check for dll in compile

[Karthik Krishnan]

I'm no expert, but I can't imagine it is a good idea to use your
SystemFolder as a source. In our deployments, I usually make it a condition
: third party tools should be installed as prerequisites, with installers
provided (vb runtimes in your case).

If you really need to have the files included, why not copy them to two
locations in your source directory, and use Msbuild. Set, say, $(dllsource),
then reference that within your wxs.

If I had to take a stab in the dark, I'd say [SystemFolder] depends on the
context you are running under.

K

On 8/13/07, Ansuya Negi <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
> I am using 64 bit machine and need to install few dlls.
> For files Msvbvm50.dll and Msvbvm60.dll:
>
> To do:
>  />
>
> Gave error:
> File of type 'File' with name '[SystemFolder]Msvbvm50.dll' could not be
> found.
>
> So used:
>
> 
>
>  Source="$(var.SystemSource)\Msvbvm50.dll" />
>  Source="$(var.SystemSource)\msvbvm60.dll" />
>
>
> light.exe : error LGHT0001 : Unknown error while getting version of file:
> C:\Windows\System32\msvbvm60.dll,
>
> system error: 2
>
> Exception Type: System.Runtime.InteropServices.ExternalException
>
> Stack Trace:
>at Microsoft.Tools.WindowsInstallerXml.Msi.MsiBase.FileVersion(String
> filePath, String& version, String&
>
> language)
>at
> Microsoft.Tools.WindowsInstallerXml.Binder.UpdateFileInformation(Output
> output)
>at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output)
>at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
>
> - Finished
>
>
> So used proper system directory for 64 bit:
> 
>
>  Source="$(var.SystemSource64)\Msvbvm50.dll" />
>  Source="$(var.SystemSource64)\msvbvm60.dll" />
>
> Worked. But it fails the purpose of having [SystemFolder], which should
> have
> checked for 32 or 64 bit versions.
> Is there a way to check 32 or 64 bit version before compiling.
>
> Thanks,
> Ansuya
> --
> View this message in context:
> http://www.nabble.com/Version-check-for-dll-in-compile-tf4264065.html#a12135302
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users