Re: [WiX-users] Reinstall a component during "Change" install

Would doing the following work? * Create a feature that contains all of the components that you might want to reinstall * Set REINSTALL=FeatureX during a "Change" install * Add conditions to the components that cause them to be included (or not) depending on the appropriate feature states. This mi

Re: [WiX-users] creating executables using wix

--Original Message----- From: Gavin Bee [mailto:[EMAIL PROTECTED] Sent: 17 November 2008 13:39 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating executables using wix Sean, It sounds like you might be looking for an exe that installs pr

Re: [WiX-users] creating executables using wix

Sean, It sounds like you might be looking for an exe that installs prerequisites and then launches your installer, a.k.a a bootstrapper. Resonable options are SetupBld or the GenerateBootstrapper task. There is also a fully featured WiX bootstrapper under development. Gavin :) -Original M

Re: [WiX-users] Always Reinstall a Component

Thanks to everyone for jumping in and providing exactly the information that I needed. Here's what I ended up with: Installed AND NOT (REMOVE ~= "ALL") AND NOT REINSTALL Thanks again, Gavin :) -Original Mes

Re: [WiX-users] Always Reinstall a Component

led or not. The MSI SDK talks about KeyPaths in detail. A verbose log file should give you a pretty good idea what the Windows Installer has decided to do with your Component. -Original Message- From: Gavin Bee [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2008

[WiX-users] Always Reinstall a Component

We have a WIX v3 installer and are trying to force a component that contains only registry values to reinstall when the user presses “change” in Add/Remove programs. The registry values are populated from properties that are set by our installer UI and can be changed when running the installer

[WiX-users] Always Reinstall a Component

We have a WIX v3 installer and are trying to force a component that contains only registry values to reinstall when the user presses "change" in Add/Remove programs. The registry values are populated from properties that are set by our installer UI and can be changed when running the installer aga

Re: [WiX-users] Build Fails with NAnt. The format ofthefile 'NAntTasks.dll' is invalid.

Eric Latendresse -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Bee Sent: Wednesday, July 23, 2008 2:54 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Build Fai

Re: [WiX-users] Build Fails with NAnt. The format of thefile 'NAntTasks.dll' is invalid.

Sounds like you need to pass the desired output path to msbuild from nant. You can use the /property command line argument to msbuild.exe to pass property values from NAnt into MSBUILD. We use the a NAnt exec task that looks something like the following:

Re: [WiX-users] Build Fails with NAnt. The format of the file 'NAntTasks.dll' is invalid.

We execute msbuild from nant to build our products and wix installers. The key to making this integration relatively painless was Szymon Kobalczyk's Xml Logger for MSBuild. Have a look at http://geekswithblogs.net/kobush/articles/xmllogger.aspx for details. Gavin :) -Original Message- F

Re: [WiX-users] Wix and MSBuild

Murray, You said that you were "trying to figure out how to bind the files into the wixlib" instead of just having references to paths. I believe that the property you are looking for is "LibBindFiles" in msbuild. When set to true , lit.exe will include all of the referenced files into the wixli