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

Rob Mensching rob at firegiant.com
Thu May 21 09:03:52 PDT 2020

I do not expect WiX v4 to have a feature for this scenario.

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

From: Frederic Forjan <frederic.forjan at aveva.com>
Sent: Thursday, May 21, 2020 8:25 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>; Christopher Painter <chrpai at iswix.com>
Cc: Rob Mensching <rob at firegiant.com>
Subject: RE: Creating a NuGet package from a WiX Library

As you are talking about nuget ,

Today, We cannot consume a nuget package directly as the package contains multiple platform of the DLL.
Our workaround is to have a fake C# project which targets our application platform (.Net 4.0, .Net 4.7.2 or others).
By doing so we know that in the build output  of this fake project, we have the correct dlls to our application platform.
Our WXS then reference those dlls by using the project reference to the fake project and use the output variables.

Are you planning to have direct support to reference nuget packages from the WIX project without having to go through this workaround ?

Frederic FORJAN
Software Architect

D +1 949 638 8198
M +1 949 353 7922

Twitter<https://twitter.com/AVEVAGroup> | YouTube<https://www.youtube.com/user/AVEVAGroup> | LinkedIn<https://www.linkedin.com/company/aveva> | Facebook<https://www.facebook.com/avevasolutions/> | aveva.com<https://www.aveva.com/>

From: Rob Mensching via wix-users<mailto:wix-users at lists.wixtoolset.org>
Sent: Wednesday, May 20, 2020 6:45 PM
To: Christopher Painter<mailto:chrpai at iswix.com>; WiX Toolset Users Mailing List<mailto:wix-users at lists.wixtoolset.org>
Cc: Rob Mensching<mailto:rob at firegiant.com>
Subject: Re: [wix-users] Creating a NuGet package from a WiX Library

CAUTION - This message originated outside AVEVA
[External email: Use caution with links and attachments]


In v4, the WiX Toolset MSBuild integration will be available via NuGet (as an SDK-style project) and the wix.exe is a dotnet tool will be available via NuGet (dotnet tool -i).

We're also updating all of the projects to play better with NuGet so you can (for example) use .nupkgs in managed custom action projects and (if all goes well) reference WiX extensions via NuGet.

Basically, v4 is designed in a world where NuGet is the package manager for the Microsoft build system.

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

From: Christopher Painter <chrpai at iswix.com<mailto:chrpai at iswix.com>>
Sent: Wednesday, May 20, 2020 5:30 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Cc: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>
Subject: Re: 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?

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

This email has been scanned by the Symantec Email Security.cloud<http://Security.cloud> service.

Please note, my email address has changed to frederic.forjan at aveva.com<mailto:frederic.forjan at aveva.com>. Please update in your Contacts list.

AVEVA Group plc is registered in England at High Cross, Madingley Road, Cambridge, England CB3 0HB. Number 2937296.

More information about the wix-users mailing list