Ok, I finally figured out the real problem! The scenario is described
here:
http://lukianol.wordpress.com/2011/04/04/visual-studio-msbuild-copy-local-pr
ivate/
I have Microsoft.Deployment.WindowsInstaller.dll in the gac. In that
scenario the lack of a Private element isn't enough. It has to be Private
True to work.
(If you are asking why I have this DLL in the GAC it's because it's a
kickass library that we use in custom powershell cmdlets and it's deployed
across our entire enterprise.)
----------------------------------------
From: "Christopher Painter" <chr...@iswix.com>
Sent: Thursday, October 24, 2013 9:38 PM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>,
"wix-devs@lists.sourceforge.net" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Issue 4147 - DTF References Inclusion Behavior
Change - still works for me
I just did a couple hours VM testing with VS2010 SP1 WiX 3.5, 3.6, 3.7,
3.8 (both weekly builds) and everything works fine.
And yet I know in my environment here and at work that I've seen this
copy local bug over and over. It's to the point that I know exactly how to
fix the build. Checkout the csproj, select True and checkin.
The wix C# csproj always starts like:
xml... Reference Include="Microsoft.Deployment.WindowsInstaller"
For other references this means False. But for this assembly it'll say
true. If I add the child element Private with innertext True it'll work.
If I add Private with innertext False it will work.
And yet I've seen situations where the lack of the Private element doesnt'
work. I've seen repeatedly tonight that it does but I swear to God that
I've seen it where it fails. I have build logs and changeset histories to
prove it.
So the only thing I can think of is that there is *SOMETHING* jacked in my
environment that is changing the default behavior that is expressed by the
lack of the element. I don't know what yet but I will do my best to
isolate it.
Either way I'm convinced that this bug can be closed. For now atleast. :)
----------------------------------------
From: "Sean Hall" <rhal...@hotmail.com>
Sent: Thursday, October 24, 2013 4:21 PM
To: "wix-devs@lists.sourceforge.net" <wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] Issue 4147 - DTF References Inclusion Behavior Change -
still works for me
I can't reproduce this issue. I went back to WiX 3.5.2519.0 and WiX
3.6.3303.1. If there is actually an issue here, I don't think it was
introduced in 3.8.
Sean
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
