#1348 Build output based on WLX culture not supported by proj. ref
-----Original Message-----
From: Neil Enns [mailto:Neil.Enns@microsoft.com]
Sent: Wednesday, September 24, 2008 1:02 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
Yes, that looks like it won't work. Can you log a bug on this in SourceForge?
Neil
-----Original Message-----
From: John Nannenga [mailto:John.Nannenga@microsoft.com]
Sent: Wednesday, September 24, 2008 10:54 AM
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
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</projectname>
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?
Discussion
This seems to be a duplicate of #2048669.