Re: [WiX-users] Environment variable "ProjectPath" is expanded, possible to turn off?

The build engine for Visual Studio is MSBuild. In MSBuild environment variables are accessed just like properties. The build event macros are defined as properties wix2010.targets. That's where your name collision comes in. One of the attributes that gets set on the Light MSBuild task is WixProject

Re: [WiX-users] Environment variable "ProjectPath" is expanded, possible to turn off?

Thanks for the reply but I'm not sure if I understand you correctly. Why would the value of an environment variable called ProjectPath influence Visual Studio's build event macro $(ProjectPath)? I also can't find any reference to either ProjectPath or $(ProjectPath) in the WiX project files so

Re: [WiX-users] Environment variable "ProjectPath" is expanded, possible to turn off?

Those properties are build event macros (http://msdn.microsoft.com/library/42x5kfw4.aspx) and are thus reserved. > Date: Sat, 20 Jul 2013 21:35:12 +0200 > From: andreas.jons...@noventus.se > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Environment variable "ProjectPath" is expanded

Re: [WiX-users] passing command args to MSI from bundle [P]

Mark, you simply need to use an MsiProperty element as a child to your MsiPackage one. A burn variable is only involved if you are not hardcoding the value you are passing to MSI. > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net > Date: Fri, 19 Jul 2013 18:53:53 + > Su

Re: [WiX-users] Cannot install the patch by double clicking on msp

http://www.joyofsetup.com/2007/07/01/semi-custom-actions/ Why are you copying the files that the patch will be replacing? MSI already does that for you. > From: jacob.hoo...@greenheck.com > To: srinu_...@yahoo.com; wix-users@lists.sourceforge.net > Date: Fri, 19 Jul 2013 14:34:07 + > Subje