I’ve blogged in the past about symbol server, to recap here is the scenario.
In your organization you have some sort of common .NET code that is shared between projects, but you have to face and resolve some problems.
- How to compile dlls
- How to distribute dlls
- How to make debugging easier for the user of the dll.
We have clearly some standard solution for all the parts.
You MUST compile dll in a build server.
The first point is clear, you MUST create a continuous integration pipeline that build dlls so you can have reproducible builds. I usually use Azure Pipelines for this purpose.
I’ve started doing this almost 12 years ago, starting with TFVC, and I’ve been using it for a while.
You should use Nuget, but, you can simply tells developer to look at pipeline output and grab compiled dll directly from the artifact of a build. Clearly nuget has a better experience, but it does not adds any magic, it just makes locating and using dll easy.
Figure 1: Pipeline output includes artifacts
By default a pipeline will publish all dll and pdb files to the build server, so you can download from the build output.
Figure 2: Download the dll from pipeline artifacts detail
Now you can simply download that dll, reference from your project and debug.
If you create a standard pipeline for TFVC (I know, Git is better :D but this is a revamp of old code), it will include for you a nice debug experience because it will index for you the pdb files.
Figure 3: Default pipeline will publish everything for you
This is a classic Azure DevOps pipeline (I know, you should use YAML :D but this is a revamp of 10 years old code). The interesting part is point (1), where indexing and publishing of symbols takes place. This is really important, you can publish symbols to network share, or you can publish with IIS but, frankly, Azure DevOps has an integrated symbol server that makes everything easier. Just go to Visual Studio debugging options, and configure your Azure DevOps accounts as symbol server, that is everything you need to do.
Figure 4: Configure Visual Studio to use Azure DevOps as symbol server
How everything works.
I’m simply downloading the dll from the build artifacts output and references from a project
Nothing fancy, and I’ve not downloaded the LogLibrary.pdb files from artifacts, I’ve downloaded only the .dll file. Now I can simply start debugging and I’m able to look at the code of the library even if I have only the dll.
Figure 5: I’m debugging LogLibrary code, only referencing the .dll file
Fore some people it seems like magic, just reference a Dll and I’m able to debug the code?????
There is no magic, here is what happens thanks to Azure DevOps pipeline. During the execution of the pipeline, Azure DevOps does two main things in the Publish Symbols path step.
- It modifies the .pdb files including information on the exact version of the code used to compile the dll, this is the TFVC changeset and TFVC file path
- Upload those modified .pdf files inside Azure DevOps symbol server.
Since you have configured Visual Studio to use Azure DevOps as symbol server (Figure 4), When Visual Studio Loads the .dll during debugging, it uses an unique identifier of the dll to ask to symbol server to download the corresponding .pdb file. If you open that .pdb file you can see, even if it is binary, that some part are textual and contains information on where to locate the source
Figure 6: Indexed .pdb file
Normally in .pdb files the compiler writes local path of the files that produces that symbol, indeed in Figure 6 you can see that the file is s:\a_work … that is the path of my build server, but then, after that part a special section starting with *VSTFSSERVER* starts containing TFVC path of the file as well as the exact changeset.
This means that during debugging, Visual Studio can query Azure DevOps to get THE EXACT VERSION OF THE FILE USED TO GENERATE THAT SPECIFIC DLL giving you the ultimate debugging experience.
Even if library developers will modify the code, publishing other version of the LogLibrary.dll, your Visual Studio can Determine the exact version of the code used to compile it and grab the exact version from Azure DevOps so you can debug original code even if the dll is 10 years old.
And everything comes for free, Thanks to Azure DevOps pipeline and support for Symbol server.