What to do when NuGet does not have the latest updates?

Question

My project has a dependency on a specific NuGet package ( Jint to be specific). A bug fix was handed over to the trunk of this project a couple of months ago, which I need to have in my project, but the update has not yet been ported to NuGet.org.

What are some recommendations for resolving this situation?

Things I reviewed:

• Pull the source and put it right in my project. I really do not want to do this, because it will pollute my repo with the source of some other project.

• Create the source code and copy it .dll into your project, possibly placing the .dll in the repo. Everything seems to be in order, but usually I don’t like checking binary files for my original control.

• Build the source package, the package in the NuGet package, and place it in the NuGet private feed. This seems like the worst solution, but a lot of pain.

If someone has successfully dealt with this scenario before, I would like to hear what your approach is.

Answer 1

I would recommend going with option # 2:

Create the source code and copy it .dll to my project, possibly .dll in the repo. Everything seems to be in order, but I usually don't like checking for binaries in my source control.

That's why:

• Easy
• Quickly and easily unlock all the problems that you have.
• The authors of the libraries are updated regularly, so I think you will post your fix soon.

Now, if authors are rarely updated, I will be more inclined towards option No. 3. In addition, if you work in a corporate environment and you see that this package (and others) is shared between development groups, again, No. 3 will have more sense. Finally, if your company had a strong presence in the legal team, again No. 3 would make more sense, as it would give you control over which packages were used internally.

Based on what you have above, it looks like you just need something specific for your project, in which case sometimes make a link to the DLL to unlock yourself under the assumption that the fix will be published shortly after bringing you back to NuGet.