[wix-devs] v4 - which .NET Framework?

[Rob Mensching]

The primary goal is to avoid upgrading a machine's .NET Framework as much as possible. So, if WiX Toolset can run on vanilla .NET Framework v4.0 or v4.5 then we should do that.

Think of the devs still using VS2010.

So the BA should require the highest version of .NET Framework that any of the WiX Toolset functionality require. When its requirements are not met, it will fall back to installing a .NET Framework.

Now. when we must install a .NET Framework, we should install a supported version. We shouldn't put something on the user's machine that is immediately going to need to be upgraded.

In that light, v4.6.1 seemed like the most forward looking version to install. But Phil points out that won't support Vista. So, I think we should support v4.5.2. I don't really want to have people complaining that their "Vista build machines" (as ever unlikely as that is) are now broken because WiX Toolset won't just install. Yes, they could manually go get a lower version of .NET Framework (and chances are they already have one on the machine if it's a build machine) but it's easier if we just pick a supported working version. I could be convinced otherwise though if someone felt strongly about v4.6.1.

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Sean Hall
Sent: Tuesday, August 2, 2016 7:51 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: [wix-devs] v4 - which .NET Framework?

This is continuing the discussion started at https://github.com/wixtoolset/wix4/pull/209.

In order to avoid upgrading someone's NETFX just for WiX, we will need to setup an InstallCondition for the .NET package.  This is because those packages have no InstallCondition by default, so even if the BA can run without going through the prereq bundle, the bundle is still going to install the package we include.

Bob said we should avoid installing anything below v4.5.2 because that's the oldest supported version.  If we're caring about what Microsoft supports, then why are we still targeting an unsupported framework?  It seems like we're basically trying to get into the position where our bundle never installs NETFX.  I think if we keep targeting .NET 4 and only include .NET 4 in our bundle, we would almost never install NETFX anyway.