{"id":233918,"date":"2021-08-16T07:00:19","date_gmt":"2021-08-16T14:00:19","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=233918"},"modified":"2021-08-17T14:56:34","modified_gmt":"2021-08-17T21:56:34","slug":"debugging-external-sources-with-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/debugging-external-sources-with-visual-studio\/","title":{"rendered":"Debugging External Sources with Visual Studio"},"content":{"rendered":"

Have you ever needed to debug and step into a code of dependent NuGet or .NET libraries that do not build as part of your solution? Today, debugging through them is not so easy as debugging your projects that are part of your solution. Starting with Visual Studio 2022 Preview 3, we are adding a new “External Sources” node in the Solution Explorer which will make debugging external sources files much easier. This node appears while debugging and will show sources for managed modules with symbols loaded containing Source Link<\/a> or Source Server<\/a> information. You can effortlessly browse those sources files and debug through them by placing breakpoints if needed.<\/p>\n

Visual Studio 2022\u00a0 team is working to deliver the promise of personal and team productivity. Debugging external sources is a capability in diagnostics tools that is just one of the exciting features we are working on.<\/p>\n

Download Visual Studio 2022 Preview<\/a><\/div><\/p>\n

External Sources node in Solution Explorer<\/h2>\n

The feature adds a new top-level node to Solution Explorer, which appears when you are in a debugging session and any loaded symbol file<\/a> (.pdb) with Source Server information will appear under this node.<\/p>\n

\"InIn debug mode \u2013 collapsed state (default)<\/span><\/p>\n

 <\/p>\n

\"InIn debug mode \u2013 an expanded state with no modules with symbols <\/span>outside of the solution loaded<\/span><\/p>\n

 <\/p>\n

\"InIn debug mode \u2013 with one external module loaded and expanded<\/span><\/p>\n

You can browse for files by expanding the tree items. Then, double-click an item to download the file from Source Server and open it in the editor. The node will persist with the module sources across the debugging sessions if the modules are set to load symbols automatically.<\/p>\n

\"DemoDemo for External Sources<\/span><\/p>\n

If you are working with applications with multiple external libraries which have their components published to Source Servers e.g. Newtonsoft.Json, CsvHelper, xUnit.net, etc. this feature will give you an easier way to browse those sources and debug through them if needed.<\/p>\n

<\/h2>\n

Settings required<\/h2>\n

The Symbol loading and source downloading can be managed by options under debugging settings.<\/p>\n

Follow the settings checklist below to make sure modules can appear in Solution Explorer’s “External Sources” node.<\/p>\n

    \n
  1. In the Tools -> Options -> Debugging options\n