On Thu, Jan 22, 2009 at 2:56 AM, Rob Mensching <rob.mensch...@microsoft.com> wrote: > VS2008? Yes. VS2005? No, I think that was make.exe... but I'm not an > expert on the VS build systems. I find modifying build systems in VS to be > painful since there are so many tiny boxes to type data in and a weird split > between "debug" and "release". <shrug/>
MSBuild was in first appeared in VS 2005 FWIW, if you know what you are doing, there is an option in VS to unload project and for an unloaded project there is an option to Edit <projectname>.csproj that lets you edit away as xml. For certain things, I find this faster/easier/less painful. > > -----Original Message----- > From: Colin Fox [mailto:greenene...@gmail.com] > Sent: Wednesday, January 21, 2009 16:06 > To: General discussion for Windows Installer XML toolset. > 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 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
