Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?

2014-11-24 Thread Klaus Gütter
: {5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with higher versioned keyfile exists. RemoveRelatedProduct does however happily remove the component. Looks like an Installer limitation. Klaus Gütter -Ursprüngliche Nachricht- Von: Phil Wilson [mailto:phildgwil...@gmail.com

[WiX-users] Force overwrite DLL with previous version in MajorUpgrade?

2014-11-24 Thread Klaus Gütter
afterInstallExecute, ThirdPartyDll version 2.5 is not overwritten (as expected by the Installer rules) - when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is removed, but version 2.4 is not installed. If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version 1.2 with WiX 3.9. Klaus

Re: [WiX-users] Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

2012-01-01 Thread Klaus Gütter
Windows Installer 4.5? Is there a bug trackinng this work? If not, it probably got lost. On Thu, Dec 15, 2011 at 11:44 AM, Klaus Gütter wrote: > > Rob Mensching-7 wrote > > > > Burn will support an immediate (aka: forced) restart. You should map > > exit codes from the MS

Re: [WiX-users] Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

2011-12-15 Thread Klaus Gütter
ike candle is missing > suport for that. Heh, the engine (Burn) supports it but the authoring does > not. That's a bug. > Any news on this one? ExeEngine/ExitCode seems not to be in 3.6 Beta. Is there any workaround? Regards, Klaus Gütter -- View this message in context: http://windows-