Skip to content
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

Closed
wixbot opened this issue Dec 29, 2014 · 8 comments
Closed

Package DTF binaries as separate NuGet packages #4633

wixbot opened this issue Dec 29, 2014 · 8 comments

Comments

@wixbot
Copy link

wixbot commented Dec 29, 2014

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.

Originally opened by heaths

@wixbot
Copy link
Author

wixbot commented Dec 30, 2014

This is planned.

Originally posted by robmen
AssignedTo set to robmen

@wixbot
Copy link
Author

wixbot commented Jan 8, 2015

Release changed from v4.x to v4.0

@wixbot
Copy link
Author

wixbot commented Jan 14, 2015

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.

Originally posted by heaths

@wixbot
Copy link
Author

wixbot commented Jan 14, 2015

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.

Originally posted by robmen

@wixbot
Copy link
Author

wixbot commented Mar 1, 2015

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 srv and srcsrv protocols for easy debugging.

Originally posted by heaths

@wixbot wixbot added this to the v4.0 milestone Dec 20, 2015
@apawsey
Copy link

apawsey commented Jan 30, 2018

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?

@robmen
Copy link
Member

robmen commented Jan 30, 2018

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.

@rseanhall rseanhall added sdk and removed extensions labels Jul 3, 2020
@rseanhall
Copy link
Contributor

Duplicate of #3981

@rseanhall rseanhall marked this as a duplicate of #3981 May 5, 2021
@rseanhall rseanhall removed this from the v4.0 milestone May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants