The someone you out in this example is Microsoft, not WiX. Yet the bug is
WiX's, not Microsoft's.
The problem in 3872 is the use of a specific assembly that the NetFx doesn't
provide for newer CLRs yet VS adds the config to enable use on newer CLRs.
Is/should it be WiX's responsibility to provide configs for what is third-party
code to run on newer CLRs? Or are we supposed to never use assemblies that
Microsoft provides for in order to create MSBuild tasks? Should we drop MSBuild
as an unreliable partner?
WiX itself runs just fine without the net2 CLR. The problem is WiX's dependence
on the Microsoft.Build.Utilities assembly. NetFx didn't think it should be
forward compatible, but VS disagreed, and as a result, bug #3872. WiX is
neither party. How are we supposed to arbitrate?
And, for the client I'm working for right now, we had to give up writing an MBA
because we explicitly target file and hyper-v servers with a fairly complex
installation, so now we are stretching the limits of StdBa as enhanced by
StdBaEx and incorporated into 3.8.
The difference between the WiX BA using WPF and a managed CA is that WiX
already requires NetFx as a prereq, so any CAs in the toolset's own
installation package would be just fine, while the CAs that the toolset
provides may be used by my client who's customers are a large part of that 1%
who won't have NetFx on their boxes.
I appreciate that I can use WiX with my client due to the CAs included in the
toolset not being managed code.
From: chr...@iswix.com
To: wix-devs@lists.sourceforge.net; wix-devs@lists.sourceforge.net
Date: Sat, 9 Nov 2013 09:12:48 -0800
Subject: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is
shown twice (on Windows XP) if bootstrapper contains driver-installation
I typically build my CA's for CLR 2.0 and then provide a customaction.config
that allows for running on newer CLR's. I haven't witnessed any problems with
this approach as .net framework rarely breaks backwards compatibility. The
point you reference is where someone failed to do that.
As for the Server 2012 example, I use LaunchConditions to gate against this. (
Based on a C# custom action that merely sets a CaJitted =1 property and
ignores failure ) If someone is actually using server core it's probably for
a Hyper-V server or file server and they can't expect to be able to install
generally available applications in the first place. Still, I will tell them
why I can't install and leave it up to them. 99% of machines will have .NET
though.
I guess Rob just needs a few more years to back down from his opinion. He's
slowly getting there now that the WiX BA uses WPF. ( Really, how is that any
different then a managed ca? )
From: "Rob Mensching" <r...@robmensching.com>
Sent: Saturday, November 09, 2013 10:24 AM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown
twice (on Windows XP) if bootstrapper contains driver-installation
Heh, and beyond that *which* version of the CLR is on Vista and beyond?
http://wixtoolset.org/issues/3872/ is a good example of the root issue.
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: Saturday, November 9, 2013 6:36 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown
twice (on Windows XP) if bootstrapper contains driver-installation
On 11/9/2013 2:00 PM, Christopher Painter wrote:
That's exactly how I've felt about native vs managed custom actions for years.
Any chance we are reaching the tipping point for a world view sea change for
you? A version
of the CLR is on the box for sure once you start talking about Vista and
beyond. And it can and should be there on XP.
Not sure if anyone would ever do this since it also removes PowerShell, but on
a Server 2012 Core machine you can uninstall .NET features.
--
Bruce Cran
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
