[WiX-users] Installation context issues when directory structure is defined in library project

I am trying to create a perUser installation package for an application that will install to the "ProgramFilesFolder" (which should be something like %LocalAppData%\Programs for a perUser installation). This works fine when everything is defined in the installer project, but when I make an insta

[WiX-users] Installation context issues when directory structure is defined in library project

I am trying to create a perUser installation package for an application that will install to the "ProgramFilesFolder" (which should be something like %LocalAppData%\Programs for a perUser installation). This works fine when everything is defined in the installer project, but when I make an insta

[WiX-users] Installation context issues when directory structure is defined in library project

I am trying to create a perUser installation package for an application that will install to the "ProgramFilesFolder" (which should be something like %LocalAppData%\Programs for a perUser installation). This works fine when everything is defined in the installer project, but when I make an insta

Re: [WiX-users] Installation context issues when directory structure is defined in library project

What OS are you installing on? The ProgramFilesFolder redirection only works on Windows 7 and above. -Original Message- From: Thomas Brodersen [mailto:t...@sharecon.com] Sent: February-18-14 5:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installation context issues whe

Re: [WiX-users] Installation context issues when directory structure is defined in library project

This will only work on Windows Installer 5.0+. You need to set ALLUSERS=2 and MSIINSTALLPERUSER=1 Dave On 2/18/2014 1:37 AM, Thomas Brodersen wrote: > I am trying to create a perUser installation package for an application that > will install to the "ProgramFilesFolder" (which should be somethin

[WiX-users] Heat.exe Exception with MSBuild and HeatDirectory

I have a HeatDirectory in wixproj and it works fine when i build from VS but when i try to build with MSbuild it crashes with the error below. Does any one have any idea why is this happening? Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'file:///E:\TFS\\to

[WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

I'm struggling with my Custom Boostrapper Upgrade issue. By following this stackoverflow thread , I'm using LaunchAction.Install. This does Upgrade the Product as well as Boostrapper, but older Bootstrapper remains

Re: [WiX-users] Bind-time variables not resolving when building project.

I tried the suppression option. It didn't work. Oh well. It's not a showstopper problem. Thanks anyway. Grant C. Anderson DMC, Inc.​ Main office: 312-255-8757 -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, February 17, 2014 5:39 PM To: General disc

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

The log file is you friend. -Original Message- From: Farrukhw [mailto:farru...@gmail.com] Sent: Tuesday, February 18, 2014 7:56 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version I'm struggling with

Re: [WiX-users] Event Source not populating on upgrade... [P]

Classification: Public Sorry the bootstrapper only has install/uninstall (the first install (rtm) is via bootstrapper, the upgrade is via bootstrapper [Latest TITUS News!] This message has been marked as Public by Steven Ogilvie on

Re: [WiX-users] Event Source not populating on upgrade...

Ok, and does doing a repair at the end actually restore the missing event sources? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Monday, February 17, 2014 9:05 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Event Source not pop

Re: [WiX-users] Scheduling a system reboot on restart manager failure

The difficulty is that you can see log entries saying a reboot is required but something will happen later that reverses that. Windows will not commit to a reboot if it turns out later to be unnecessary (because the app shut down, a Dll unloaded, or the app could be isolated in memory and release t

Re: [WiX-users] Event Source not populating on upgrade... [P]

I'm talking about the MSI. Ignore the BA for now. Do a manual MSI upgrade on a test VM and verify it has the same flaws. Then using the command line perform a repair on the upgraded package and see if the behavior is any different. The one thing I wonder is why you don't have a single event

Re: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory

Is E:\ local? I suspect it might be a network share. If the MSBuild process is using elevated privileges then all network shares (created when non-elevated) disappear. This only occurs with WindowsServer 2008R2 and above I believe (and I'm not sure if it's in Windows 7, but it's definitely in Wi

Re: [WiX-users] Scheduling a system reboot on restart manager failure

Thank you for the insight, Phil!I scanned through the logs again and i do see a "Info 1903" logged. MSI (s) (60:04) [15:51:30:283]: Verifying accessibility of file: 28253a39.rbfInfo 1903.Scheduling reboot operation: Deleting file C:\Config.Msi\28253a39.rbf. Must reboot to complete operation. Acc

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Hi Rob :) I should have attached the log file before.. Adding the log file from version 1.0.1.0 while updating 1.0.0.0. MyProdSoftwareInstaller.log Btw, to me, this doesn't show any indicat

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

I don't think that's the whole log file. I don't see the "Apply complete" line. Sean > Date: Tue, 18 Feb 2014 19:50:14 -0800 > From: farru...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side > by side with older ver

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Yes, that may be because before Apply Complete, it is not finished and -uninstall is failing. from last lines: 26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package: {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path: C:\Users\Farrukh\AppData\Local\Package Cache\{c0489d1d-654e

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

The line [26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package: {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path: C:\Users\Farrukh\AppData\Local\Package Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe, arguments: '"C:\Users\Farrukh\AppData\Loc

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Sean, There was Environment.Exist(this.FinalResult) in ApplyComplete(). Now replaced with: this.FinalResult = e.Status; //Storing the final status code. bootstrapperApplication.Engine.Quit(e.Status); Please find latest log attached with this reply. However, I've figured out that "this.Command.Get

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Well known command-line args are processed by engine and provided to BA in the Command struct. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Farrukhw [mailto:far

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

So when if found (Engine.Detect) that 1.0.0.0 is there, the Command got Uninstall automatically. But we are invoking our UI dialogs here like: if(MyViewModel.PState==PackageState.Absent) Application.Run(BootStrapDlgs.Welcome_Dlg); //Let's start with Welcome Dlg else Application.R