Is this change not compatible with the "List of Supported Project References"?
Before this change, I had a reference in my MSI WiX project to a merge module WiX project. I then referred to the built merge module via $(var.<ProjectName>.TargetPath). This worked just peachy, until this change was introduced. Now (WiX 3.0.4519.0), during a build this continues to resolves to: ...\bin\Release\MyMergeModule.msm instead of where the file was actually built to, ...\bin\Release\en-us\MyMergeModule.msm Within the Wix.chm under "List of Supported Project References", I don't see anything for specifying culture. The var.ProjectName.TargetPath example indicates it should resolve to the full filename of where the item was built to (but it isn't, anymore)... Thoughts? -----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. ------------------------------------------------------------------------- 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
