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. Thanks for your understanding. We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.

Thanks for helping make community forums a great place. Click HERE to participate the survey. Done badly it may gravely impede development and result with mediocre quality. Sharing source code per se has lots of problems on its own. Therefore, virtually every technology stack has a way of distributing versioned binaries instead. NuGet is the standard for sharing binaries in the. NET world. The next step is an ability to debug third-party binaries if debugging symbols are present.

This, however, requires the source code to be downloaded and the debugger to be pointed to it. Source Link is an attempt to make the whole experience seamless. Whilst we genuinely thought there would not be hundreds of packages and we were right on that! OK, maybe it is not really an obvious problem, but given the title of this blog, I hope it comes as no surprise! The screen-shots that follow have been taken from a scaffolded Console Application with no meaningful changes - I used the.

Net Framework 4. NetCore, etc. Below is a very simple Main method. As you can see, it will create a new Contact and then write the details to the screen.

I am sure the above output will not surprise you. However, below is the output when the Contact Id is not set:. Now, in an ideal world, the exception would tell us which parameter was out of range and what that expected range was. Whilst this is a very basic error to locate as the class below will reveal in a moment , in a real-world example, we may have to go through many classes before we reach the source of the error. The first step required is to create a local NuGet folder to host the debug NuGet packages.

You can even create your own internal NuGet server if you want but that is outside of the scope of this article. The screen-shots below are from Visual Studio but, other than potential location changes for some of the options, the steps should work for VS and upwards. All being well, a screen like the one below will be shown:.

The screen will update as shown the blue-highlighted option is the newly created, default source :. From Visual Studio Graham Graham 1, 12 12 silver badges 19 19 bronze badges. Not sure if it is a bug but anyone trying this in VS clicking "Debug Source Files" doesn't show the correct window, it seems to show the configuration manager.

Choco Smith I have the same problem. Has always worked fine for me in VS I used this today on VS Enterprise , version If it's not just a rogue extension messing up your menus, perhaps create a Microsoft Connect issue? I wish i could up vote you again..

I got here earlier in the year and forgot about this, now I need to do the same and. You used an archive link. Fantastic answer. Karl Harnagy Karl Harnagy 5 5 silver badges 10 10 bronze badges. Why do I need a 'symbol server' If I already have the. Can't Visual Studio just read this file directly? Visual Studio needs to first find a remote. A symbol server like ProGet will reindex the pdb file and serve files based on that.

See inedo. I had to modify the "Symbol Server" settings for my feed and disable the setting "Strip symbol files from packages downloaded from this feed". Show 1 more comment. In your. Then, add a reference to the NuGet package project in your solution.

Right click References, add Reference, choose Projects and tick the box for the project I had to do it this way when I the method I wanted to debug inside the NuGet package was called by the framework and not by my code, thus I couldn't step into it. Matt Frear Matt Frear This method is error prone and time consuming to do every time. Setting up a symbol server is a one time setup — hofnarwillie. Thanks for that.

Although my downvoted answer is laborious, I stand by it as it allows me to debug both my code and the NuGet package without a source server — Matt Frear. I wouldn't like anyone in my team to do it because it is error prone and time consuming. Down voting because I think that it is not the right way to approach it.

I'm sure if enough people agree with you that it is a sensible way to do it then they will up vote it and I will be thoroughly corrected. Just use source control properly to undo your changes.