Ok. Let me think about this tonight, there are likely a couple of solutions to this that will work.
Neil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: Thursday, September 11, 2008 2:27 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land In prebuild events I execute a custom process that carries out a process that does full signing of all assemblies that were built using public key only delay signed build output. In postbuild events I execute a custom process that carries out publisher signing of msi build output. I also execute a robocopy command that copies our set of service deliverable specific automated distributed msi deployment processing xml to the same folder as the service deliverable msi build output. With this new build output folder scheme this means that pre/postBuild steps that may have been using the $(TargetPath) macro value which is no longer valid now have to use a set of $(TargetDir)<lang-local>\$(TargetName) steps, e.g. $(TargetDir)en-us\$(TargetName). I guess I was just thrown off by the assumption that there might be something like a default / language neutral culture which lands in the bin\$(Configuration) folder and only non-default / language neutral culture output lands in bin\$(Configuration)\<lang-locale> folder. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Thursday, September 11, 2008 1:53 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land Sorry, my mistake. I looked at my changes to the WiX build process and you'll get the different output locations any time you have a localized build (one that has .wxl files in it). What are you trying to do in your Pre- and Post-Build steps? Depending on what you are doing there may be existing things in the wix.targets file you can leverage (much like VS does) to make small tweaks to your targets that work with the output file locations. Neil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: Thursday, September 11, 2008 1:43 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land Thanks for the response. I currently only have a single Resources\Strings.wxl in my project settings which has the Culture="en-us" attribute set. Should I just remove that string resources file Culture attribute setting to get build output landing in bin\$(Configuration) again? <WixLocalization Culture="en-us" xmlns="http://schemas.microsoft.com/wix/2006/localization";> For now since we only build Language="1033" setup output getting msi and msp build output to land in bin\$(Configuration) again is super helpful in terms of TFS automated build processing where being able to have postBuild events simply reference $(OutDir) makes the desktop vstudio and tfs build agent server pre/postBuild event authoring more straight forward. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Thursday, September 11, 2008 1:37 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land Robert, This happens when you have multiple .wxl files in your project with different cultures in them. Setting the Cultures field in properties will control which languages get built, but the output will still go into the sub-folder (this is so you can set up different configurations, for example, to control which languages get built for different types of builds). The only way to disable this is to remove the .wxl files from the project that are for other languages. You could also perhaps do some tweaking to the project file to conditionally include those .wxl files based on a flag somewhere, but that would be some additional work and tweaking. Neil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: Thursday, September 11, 2008 1:33 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land This is really got me in a tail spin. In my existing project started with 4004 and recently migrated to the latest wix drop regardless of whether I do or do not have a <wixProject> | properties | build | cultures field value specified my light.exe output is getting directed to bin\$(Configuration)\en-us. In any file | new | wix project regardless of whether I do or do not have a <wixProject> | properties | build | cultures field value specified my light.exe output is getting directed to bin\$(Configuration). Diff'ng both wixproj files I am unable to find anything different that would suggest why. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, September 10, 2008 6:47 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] what setting causes current wix build output to land in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to land Robert O'Brien wrote: > If I clear my <wixProject> | properties | build | cultures to build field and > rebuild I'm still getting output in the bin\$(Configuration)\en-us folder. > Is there a way to restore build output landing in bin\$(Configuration) ? > Not that I'm aware of. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
