Nuget download debug version of package

 · Basically per my understanding, publish the release version of your dll is the best choice since your user wont debug into your dll, they will only care about how they code works. Base on your scenario, I think create the Nuget package from project seems a good approach, we can have the configuration from csproj file: bltadwin.ru  · Towards the seamless debugging ¶ Having a NuGet server with symbols support and some code in a hosted GitLab instance I was able to put together a rough tutorial that should help you achieve the first-class debugging experience for NuGet packages. Publish debug symbols ¶.  · Debug a Nuget Package. Let's see now how to debug a referenced Nuget package with Visual Studio and the bltadwin.ru symbol server. It is pretty simple, you just have to follow the Recommended configuration on bltadwin.ru, I put it here for consistency with the post: Go to Tools - Options - Debugger - General.

Perform the following steps to download jQuery using NuGet Manager: In the NuGet Package Manager, as shown in the following screenshot, select the jQuery package from the left-hand side panel. In the right-hand side panel, select the Version that you would like to use in your web project from the drop-down menu. Click on the Install button. Available NuGet Distribution Versions · Windows x86 Commandline · Visual Studio · Visual Studio 8 Answers · Selected your nuget server / source · Find and select the nuget package your want to install an older version · Uninstall current. With all of the canonical debugging tools unavailable, our eventual solution was to take the reins from NuGet. Be Your Own NuGet. Okay, obviously you do not want to stop using NuGet altogether! But you can manage a single package on your own, just for debugging purposes: 1. Make a new branch for debugging the package.

Debugging a NuGet Package NuGet adds and manages DLL files in bltadwin.ru project, but not any source or symbol files. This can make debugging packages without extra tools like ReSharper rather challenging, since you’re basically left analyzing the source code without stepping through it at runtime. Build and compile the NuGet package on your local machine; Copy bltadwin.ru you've just compiled into your local NuGet packages feed folder (On my machine, this is C:\Users\matt\.nuget\packages\), overwriting the existing NuGet bltadwin.ru That's it! You should be able to step into the package while debugging. Debug a Nuget Package. Let's see now how to debug a referenced Nuget package with Visual Studio and the bltadwin.ru symbol server. It is pretty simple, you just have to follow the Recommended configuration on bltadwin.ru, I put it here for consistency with the post: Go to Tools - Options - Debugger - General.