[WiX-users] Changing uninstall string of an update

Hi, I have noticed that Windows Installer create a registry entry upon product installation and puts an uninstall string there. It is being used when uninstalling the product from control panel. I did not find a similar entry for update although it looks similar in control panel. Any idea how c

[WiX-users] Looking for up to date example for Burn project

Hi, I have download the latest build of WiX 3.6 and tried to create a simple chainer with no luck. I have looked into the sources and got even more confused. It looks like there are some pieces of code using old stand alone Burn tool and some using Candle and Light for creating a target executa

Re: [WiX-users] .NET Custom Action fails intermittently on some machines

Hi, I'm facing the same problem for quite some time. Same OS (W2K8R2), same conditions (VM) without a decent explanation. I have an immediate custom action gathering some info and finally setting a property. Sometimes it fails without a reasonable explanation. Investigating the DFT source code s

[WiX-users] MakeSfxCA do not copy file version from C# assembly to output dll.

Hi, I am using MakeSfxCA utility (Wix 3.0) to create a DLL with CSharp custom actions. Recently I have noticed that this DLL has the file version info exactly as the SDK "sfxca.dll" . I have tested it with both build #5217 & #5332 . When reverting the SDK in use to build #4827 I have gained the

[WiX-users] How to identify the custom action type in run time.

I’d like to write a generic custom action which can be run either immediate or deferred. In order to pass arguments to this custom action I need to use two different approaches since it is a given fact of Windows Installer behavior. On the caller side (Wix) it is quite clear. I have a problem w

Re: [WiX-users] Wrong Assembly version in MsiAssemblyName table after

Bob Arnson wrote: > >It appears to be by design, based on this comment in the code: > IMHO, it is a bug, by design, but still a bug. According to Aaron Stebner's blog http://blogs.msdn.com/astebner/archive/2005/02/12/371646.aspx the fusion bug was fixed long time ago (.Net 1.1 SP1 & .Net 2.0) a

Re: [WiX-users] Wrong Assembly version in MsiAssemblyName table after

Bob Arnson wrote: > Sounds familiar -- try upgrading to the RC2 release for a fix. > Well, I've tried both "3.0.5217.0" and "3.0.5224.0". Still the same. Any idea? Thanks, Dov -- Register Now & Save for Velocity, the

[WiX-users] Wrong Assembly version in MsiAssemblyName table after

Hi, I have a .Net assembly file with file version "4.0.763.0" and assembly version "4.0.0.0". In order to install it into the GAC I have used latest Wix3 toolset and faced a wrong registration issue. Taking a look into the MSI file with Orca tool shows that in MsiAssemblyName table the file ver