Colin, When you say "setting the 'OutputName' field" do you mean through the UI or through manually editing the project file. Theoretically, you should be able to edit this in the project file and it will work (using the '$(xxx)' syntax), but the VS IDE doesn't let you do so through its own UI.
However, there isn't a $(xxx) (environment or MSBuild variable) that I'm aware of that will get you the property you want. You may need an MSBuild extension or something for this. We've abandoned building WiX projects via the IDE and doing so via the MSBuild targets that are provided with WiX in favor of our own build script. There, you have all the power of MSBuild at your disposal and none of the "assumptions" made during the WiX development or the VS2005 development in your way. It works good for us, except that you lose the pleasantness of being able to build directly from VS, but I can't say I've really missed that much on our installers anyway, since our installers are of monster size (not like Office or anything, but they take a good 15-30 minutes to build) so I can't say I really want to hang my IDE for that long anyway :) Kelly Colin Fox <greenene...@gmail.com> 2009-01-21 04:10 PM Please respond to "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> To "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> cc Subject Re: [WiX-users] Setting the output name with a variable If we're building with Visual Studio (or devenv.exe) are we still using msbuild under the hood? On Wed, Jan 21, 2009 at 3:57 PM, Rob Mensching <rob.mensch...@microsoft.com>wrote: > You need to separate the WiX toolset from MSBuild in your mind. Treat the > WiX toolset the way you would treat csc.exe or vbc.exe or (actually more > like) cl.exe/link.exe. Anything written in the language being compiled is > completely contained within the compilation process. MSBuild (or NAnt or > make.exe or whatever you want to use) is driving the outputs from those > tools in a coordinated manner. You need some MSBuild syntax to set the > property you want. I'm not an MSBuild guru so I'm not much more help than > that. Sorry. > > > -----Original Message----- > From: Colin Fox [mailto:greenene...@gmail.com] > Sent: Wednesday, January 21, 2009 15:52 > To: wix-users > Subject: [WiX-users] Setting the output name with a variable > > I've asked this before but haven't gotten a solid answer, so I'll try one > more time. > > I need to be able to incorporate a modified form of the package version > into > the .msi name. > > What would be ideal would be the ability to reference the > "!(bind.fileVersion.MyPackageEXE)" as part of the output name, something > like: > > DeluxeInstaller_!(bind.fileVersion.MyPackageEXE).msi > > I've had no luck shooting in the dark with different forms of the variable. > > Setting the "OutputName" field to include either a $() variable or a !() > bind variable doesn't work, and the bind variable seems to no longer be in > scope at the post-build-event stage (where I could simply write a line of > DOS that renames the file. > > Is the only option to me at this point truly to write a separate > stand-alone > application that will have to go get the version information from the > binaries itself and do a rename? > > That seems incredibly lame, since all the information I need is available > during the wix processing, but I just don't seem to be able to get at it. > > I REALLY don't want to have to make an ugly hack just to add the version > number into the filename. > > Please don't tell me that that is the only way. > > -- > Regards, > cf > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Regards, cf ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ************************************************************************************** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless otherwise noted in this email or its attachments, this communication does not form a Statement of Actuarial Opinion under American Academy of Actuaries guidelines. ************************************************************************************** ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
