I've been using VS2019 for some things that I hadn't used it for in the past, and have come up with a couple minor annoyances that I'd like to confirm with others.
1) If you add a reference to some other dll or project, and choose Browse, the Recent list is ALWAYS empty. I have yet to see it contain anything, despite having just added a dll of my own creation. Navigating to the dll works just fine, but what's the point of a recent list if it has nothing in it...ever?
2) If you reference a Release version of a dll, you can't step into it while debugging. Frankly, this is how it really SHOULD work, because the release version won't have the symbol information that a debug version would have, and might have optimizations such that the code and the execution don't necessarily line up. However, in VS2010, there was no problem with stepping into release versions. In fact, this was done to an extent that was darn near magic, since you could dynamically load a release version dll from a folder that was not related to the project that created the dll, and VS would STILL let you step through the source code, complete with comments, which meant that VS was finding the project where the dll was created, and taking you to the source code from that project. I have yet to confirm that the same functionality is no longer available, but since VS2019 won't let you step into a referenced dll if the dll is a release build, I can only assume that it won't help you out any more than that for a dll that is dynamically loaded.
So, my question is: Is there a setting I have wrong such that the recent list holds nothing? Is there a setting that is preventing me from stepping into a release build?
1) If you add a reference to some other dll or project, and choose Browse, the Recent list is ALWAYS empty. I have yet to see it contain anything, despite having just added a dll of my own creation. Navigating to the dll works just fine, but what's the point of a recent list if it has nothing in it...ever?
2) If you reference a Release version of a dll, you can't step into it while debugging. Frankly, this is how it really SHOULD work, because the release version won't have the symbol information that a debug version would have, and might have optimizations such that the code and the execution don't necessarily line up. However, in VS2010, there was no problem with stepping into release versions. In fact, this was done to an extent that was darn near magic, since you could dynamically load a release version dll from a folder that was not related to the project that created the dll, and VS would STILL let you step through the source code, complete with comments, which meant that VS was finding the project where the dll was created, and taking you to the source code from that project. I have yet to confirm that the same functionality is no longer available, but since VS2019 won't let you step into a referenced dll if the dll is a release build, I can only assume that it won't help you out any more than that for a dll that is dynamically loaded.
So, my question is: Is there a setting I have wrong such that the recent list holds nothing? Is there a setting that is preventing me from stepping into a release build?