Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature Request - Support adding NuGet packages into WiXProj Projects (MSI project or WiXLib) #5861
I would like to create wixlibs based on packages that we store in our private package repository, both .NET and native projects included.
Right now when I try and do this I get an error
"Could not install package 'BLARH 126.96.36.199". You are trying to install this package into a project that targets 'Unsupported, Version=v0.0' but the package does not contain any assembly references or content files that are compatible with that framework, contact the package author"
Adding a package of any sort should not matter to a wixproj.
If this issue is a bug:
3.11, 3.14.1703, 4.X (error occurs everywhere)
2017 Enterprise (15.8.0)
4.5, 4.6, 4.7, C++ (Win32 Native)
Being able to source content from a nupkg would be an amazing way to ensure that installers are 1) fast to build, 2) decoupled from application 3) more easily managed.
The teams I have worked on typically have a large number of applications (EXEs or Web Apps) that go into an installer. Instead of having crazy build/copy scripts set up it would be fantastic to simply go into the package management UI in the installer project and upgrade an application, test the installation, and check it in. Updating the wxs file's path shouldn't be a problem as an additional manual step, although it could easily be extracted out and automated as a wix variable of some kind $(.installpath).
I am trying to add a nuget package of ANY kind to a WiXProj project in Visual Studio. This way installers are easily upgraded and maintained.
For now, I would (read: not currently doing it) need a manually maintained packages.config file and pre-build steps to get all nuget packages for each application.
Allow for a wixlib to have any nupkg added, regardless of target frameworks, dependencies, etc. Just install them in a local packages folder. Maybe automatically add wixvars for Source location roots to eliminate the need to update wxs files on every upgrade.
At the end of the day, I want to promote packages to stable/release, not code. This will go a long way in doing that.