[wix-users] Creating a NuGet package from a WiX Library

[Christopher Painter]

It's become an essential part of .NET Core / Standard development.   Personally I got along just fine without it for many years for .NET framework development.  It's just a big easy button and I've always wondered if new developers will actually understand what's happening behind the scenes if they never have to do it themselves. I guess it doesn't matter.

But anyways I wasn't really asking about the application development / build side of it.  I was wondering more about the deployment side of it.   Would nuget ever feed into WiX to automate aspects of installation authoring.  I guess it's not really ever possible as just because a DLL comes in doesn't mean it'll become any given component.  It could go into an application directory  or one or more  webapp\bin directories and be associated with N number of features/subfeatures.

Alas I have IsWiX so it's really easy for me to manage since I'm always thinking about application dependencies as a first class citizen.

BTW I still despise the word 'modern'.  There is nothing 'modern' about MSI and I'm fine with that!  I've been using it for 20 years now and it gets the job done without me having to relearn everything every other month.

________________________________
From: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>
Sent: Thursday, May 21, 2020 9:36 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Christopher Painter <chrpai at iswix.com>
Subject: RE: Creating a NuGet package from a WiX Library

NuGet is an essential part of dev.  Instead of having to go hunt around for DLL's, add them to a lib folder, manually update project files if needed etc. etc. etc.  With modern dev you just add the package if you need say MVVM lib and it's up to the NuGet package owner to get all the stuff correct.  Then on the build server it gets the package and it works.

Anyways, that's not really the point, is it?  I worked for a company where we took over a product that was created using only Notepad, as if that somehow made it more sophisticated.  😊

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Christopher Painter via wix-users
Sent: Wednesday, May 20, 2020 7:30 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Christopher Painter <chrpai at iswix.com>
Subject: EXT: Re: [wix-users] Creating a NuGet package from a WiX Library

I talked to (the) (one of the?) nuget guys years ago.  I didn't see how NuGet did anything for deployment.  To me it's an NPM type package manager that is an easy button for developers to pull dependencies in.   If you happen to use publish profiles / cloud deployment your not even thinking about deployment actually.  If your thinking MSI your thinking  merge modules,  wixlibs, chaining and so on.  I mentioned all of this and I got the impression he thought I didn't know what I was talking about and was ready to get off the phone.

Where do you see WiX v4 and NuGet working together?

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Rob Mensching via wix-users <wix-users at lists.wixtoolset.org>
Sent: Wednesday, May 20, 2020 3:27 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Rob Mensching <rob at firegiant.com>
Subject: Re: [wix-users] Creating a NuGet package from a WiX Library

As you've found, NuGet doesn't really play well with WiX v3 (WiX v3 was designed long before NuGet came to be). This is improving in WiX v4.


--
Short replies here. Complete answers here: https://www.firegiant.com/services/

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Vanniekerk, Tyrel (GE Healthcare) via wix-users
Sent: Wednesday, May 20, 2020 1:05 PM
To: wix-users at lists.wixtoolset.org
Cc: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>
Subject: [wix-users] Creating a NuGet package from a WiX Library

Hi,

This is probably an odd question 😃, but do you happen to know what I have to do to get the output from a WiX library into a NuGet package that will work correctly when added to a WiX setup project?  I download the source code for the Wix.Toolset NuGet package and that adds some XML to the wixproj manually.  I assume I will have to do something similar.

The second question is how to get a regular NuGet package to work with the Wix Setup project.  I have a base CustomActions assembly that we have in a NuGet package on our local NuGet server.  When I try to add that I get an error that my NuGet package does not support the targets type of “Unsupported”.

Thanks,
Tyrel


You are trying to install this package into a project that targets 'Unsupported,Version=v0.0'

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

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

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