[wix-devs] Static libraries across VS versions

[Bob Arnson]

Status report: The full build works on my machine! It fails on the build machine!

I believe Sean pointed out that the .NET Framework 4.0 reference assemblies aren't installed on the build machine, because they're no longer included in VS2022. That causes the DTF build to fail. I (temporarily) retargeted them and now the build fails with NuGet warnings because you're not supposed to use Microsoft.NETFramework.ReferenceAssemblies with SDK-style projects (or with central package versioning)... I don't know how to suppress NU1009 from a `nuget restore`. So that's where I'm at tonight.

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Bob Arnson via wix-devs
Sent: Sunday, 5 December, 2021 20:07
To: Rob Mensching <rob at firegiant.com>; WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Bob Arnson <bob at firegiant.com>
Subject: Re: [wix-devs] Static libraries across VS versions

Yep. I'm putting them in a `v14` directory in the nupkegs, just in case we need to handle an incompatible `v15`.

-----Original Message-----
From: Rob Mensching <rob at firegiant.com>
Sent: Sunday, 5 December, 2021 19:08
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Bob Arnson <bob at firegiant.com>
Subject: RE: Static libraries across VS versions

Frist, yay! My votes:

1. Yes.
2. No.
3. Yes (I've been working with WiX solely from VS2022 for a while now, everything is working well)

So `v143` for everything?


-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Bob Arnson via wix-devs
Sent: Sunday, December 5, 2021 3:21 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Bob Arnson <bob at firegiant.com>
Subject: [wix-devs] Static libraries across VS versions

I'll open an issue but wanted to get a head start. I gave myself the action item (oh god, I can't believe I just said that) to investigate whether we could build our static libraries with the latest VS and use them "down-level" on earlier versions of VS. The answer...

...is yes, we can. I built DUtil with VS2022 and with some tweak to the nupkeg was able to consume it from a project originally built with VS2019 and subsequently built with VS2017. It's not an exhaustive test - console, string, proc -- but I suspect that it was more of a pass/fail test.

Questions:


  1.  Should we do this? (I vote +1.)
  2.  Should we do this now, with VS2019 as the baseline?
  3.  Should we decide now to use VS2022 as the baseline?

____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/ ____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/