[WiX-users] Toggling between per machine and per user installs.

I have an app that I've currently authored the setup to always install unelevated per user. When I created my components to deploy files I had to include a registry value in each one and make it the KeyPath of the component to make the validation happy. Now I need to support a per machine opti

[WiX-users] ShellExec launching a Binary.

I have a button that was previously using the WixShellExec custom action to launch a URL in the browser. Now I'd like to change it to launch an RTF file I've stuck in the Binary table. I've played with it some, but I can't get it to work. What's the best way to do this? -J --

[WiX-users] Problem with MessageResult in DTF?

I'm trying to implement a files in use dialog and I've noticed a discrepancy between the values in Microsoft.Deployment.WindowsInstaller.MessageResult and the values of the dialog box command ID's in WinUser.h. Here's what I see in MessageResult: public enum MessageResult {

[WiX-users] Changing default UILevel for uninstall.

The default UILevel for uninstall appears to be 3 (Basic). I need to run at UILevel 5 (Full) in all cases but 2 (None). I have tried adding a custom action to the InstallExecuteSequence that changes the UILevel property to 5 - checking the setup log, I can see my custom action runs and the UI

Re: [WiX-users] Changing default UILevel for uninstall.

just fine in my daily testing: msiexec /x myproduct.msi /qf /lv*x .\install.log qf is for full UI and you can put product code instead of msi filename since you are not supposed to know where is installed/downloaded msi file. -Original Message- From: Joe Coplen [mailto:[EMAIL PROTECTED

[WiX-users] Change in output behavior?

I've just upgraded to a newer v3 build and all of my post-build steps that expect $(TargetPath) to point to my build output are broken because OutDir, TargetPath, TargetPdbPath are all pointing to the wrong place. OutDir is shown as "bin\Debug\", for example whereas the build is really dumping