Re: [WiX-users] Use multiple files during CustomAction

2008-03-09 Thread BugBoy
Good idea. It's quite an amount of work (I use managed code), but I'll give it a try. I think it's a flaw in the MSI design... Paul Lalonde-2 wrote: > > You could embed the custom DLL in your CA's resources, then specify > when linking the CA that the DLL is delay-loaded. At runtime, the CA

Re: [WiX-users] Windows Service not removed on Uninstall

2008-03-09 Thread faheemitian
Bob Arnson-6 wrote: > > faheemitian wrote: >>> MSI (s) (FC:B4) [12:56:42:668]: Component: TestServExe; Installed: >>> Local; >>> Request: Null; Action: Null >>> > > Action:Null means that the component won't be installed, so MSI won't do > anything with the service. > > -- > sig://

Re: [WiX-users] Use multiple files during CustomAction

2008-03-09 Thread Paul Lalonde
You could embed the custom DLL in your CA's resources, then specify when linking the CA that the DLL is delay-loaded. At runtime, the CA could extract the DLL and put it in the TEMP directory. You could then supply a callback to the delay-load infrastructure in order to load the DLL from th

Re: [WiX-users] Use multiple files during CustomAction

2008-03-09 Thread BugBoy
This is bad, because I run it only during uninstall and this code is run at the end of the uninstall, so the dependencies are not there anymore. I really think this is bad. Because of UAC I need to use deferred execution :( Alexander Shevchuk wrote: > > Custom actions stored in Binary table mus

Re: [WiX-users] Use multiple files during CustomAction

2008-03-09 Thread Alexander Shevchuk
Custom actions stored in Binary table must be either self-contained or depend on pre-installed items. Because you run your UninstallAction after InstallFiles action you can just include your dependency dll into your install. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PR

Re: [WiX-users] Always change the product code?

2008-03-09 Thread Alexander Shevchuk
[inline] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Markus Kuehni Sent: Sunday, March 09, 2008 1:37 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Always change the product code? Hi Alex Thanks, this helps a lot! Three follow-up questions (I'll go on to try-

[WiX-users] Use multiple files during CustomAction

2008-03-09 Thread BugBoy
I have defined a WIX script that requires to run a .NET application with elevated rights during uninstallation. I added the following lines to my file: $BinaryComponents=2 It works fine if "Uninstall.exe" doesn't depend on a custom DLL. But I do need a custom DLL during the uninsta

Re: [WiX-users] Always change the product code?

2008-03-09 Thread Markus Kuehni
Hi Alex Thanks, this helps a lot! Three follow-up questions (I'll go on to try-and-error that - but maybe you know the answer straight away). 1. will UpdateVersion/ @MigrateFeatures="yes" schedule the MigrateFeatureStates action automatically or do I need to manually schedule in InstallExecut

Re: [WiX-users] Always change the product code?

2008-03-09 Thread Alexander Shevchuk
Hi Mark, Major upgrade (http://msdn2.microsoft.com/en-us/library/aa369786(VS.85).aspx) is the easiest of upgrades to implement. The only downside, I can think of, is the fact that it is a complete reinstall of the product, although by carefully scheduling RemoveExistingProducts (http://msdn2.

[WiX-users] Always change the product code?

2008-03-09 Thread Markus Kuehni
Hi After having read about all the gotchas of minor upgrades, including the necessity for msiexec command-line args, I think it's best (in our case) to always change the product code and be sure to always get a clean install. I expect it results in more file deleting/copying activity than woul

[WiX-users] CustomAction - Check for space

2008-03-09 Thread Riyaz Mogharabin
Hi everybody, Hope you are fine. I have created an installer with "WiXUi.InstallDir". I need to check the install path that the user selects and not let him continue the installation if the path contains a space. The installation is continued when the user choose a path which does not contain a s