Problem with SymbolSource Server

We are setting up a local SymbolSource server for our development team. We followed a good article written on the SymbolSource server . We use TeamCity for construction. For each assembly, it .symbols.nupkgis placed on the local SymbolSource using the command nuget push, and the nuget package is transferred to the local NuGet server.

The problems we are facing:

For the nuget package MyPackage.1.1.0, if we click the same thing on the character server, it creates a hash and how it links each version folder to the file upload .pdband .cs. (This is my understanding. Please correct me if I am wrong.)

After configuring the symbol server configuration in Visual Studio, we will try to debug the project. We are faced with the fact that the hash created by Visual Studio to download characters is completely different from the hash generated when registering with the help of nuget pusha character server that ends with 404. (See. Attached file with script status code.) If we create the folder manually with the same hash on the Symbol server, we get the desired result, i.e. take a step into the code.

Why are there two different hashes for the same version of the dll / nuget file?

Two different guid's generatedFiddler output

+4
source share
1 answer

, , ( ), GUID. DLL - PDB GUID . DLL GUID, ! , PDB - ​​ DLL. , GUID, , DLL. , , , :

  • nuget dll nuget. , , , .
  • DLL nuget, , .
  • dll nuget

, , , Visual Studio, -, GUID , GUID PDB . , (), .

- , DLL. dumpbin, , PDB DLL

dumpbin.exe /headers mypackage.dll

, - PDB (!) GUID, DLL PDB. GUID DLL , DLL/PDB , , .

+2

Source: https://habr.com/ru/post/1536687/


All Articles