New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package DTF binaries as separate NuGet packages #4633
Comments
This is planned.
|
|
I can open another bug if you desire, but I was thinking about also putting dutil into its own nupkg for native code as well. I've used our internal dutil for a few projects (you really get used to it after a while!) and pulling this in as a nupkg from our internal gallery would be much easier. So just adding the note here in case you feel like that would be good externally as well.
|
Yes, dutil (and wcautil,) as a NuGet package was planned. This was discussed during the triage meeting but notes were not transcribed in this issue. I think we're okay right now.
|
As a side note, be sure to set up an account with http://symbolsource.org so symbol packages you submit to http://nuget.org are made available. This implements the
|
So two years ago this was planned? Is there any reason not to release the current versions, considering all that's required is a nuget wrapper around the assembly? |
This is part of WiX v4. WiX v4 is close to a prerelease but not quite ready yet. We're not going back and releasing NuGet packages for WiX v3 content. |
Duplicate of #3981 |
DTF provides some popular wrappers around the Windows Installer APIs, but to reference them you either need the WiX toolset installed on your build machine (not a best practice) or check in the binaries to your repo, which for DVCS like git and hg is expensive to pull if you frequently update the binary versions.
Instead, it would be better to package these as NuGet packages and, because not all assemblies may be needed in all cases and because almost all of them can stand alone ( with the exception of Microsoft.Deployment.Resources.dll ) create them as separate packages with dependencies defined as needed.
The text was updated successfully, but these errors were encountered: