Symbols are not loaded about klondike

[sberserker]

Appears I was going to wrong server that's why url mismatch. After I updated the settings Visual Studio was able to load the symbols.

The only problem remains is visual studio crashing when trying to pull the sources to step into but at the same time resharper go to implementation works. So it might be visual studio issue since endpoint works: /api/source/Library.Test/0.3.0/Library.Test/Class1.cs

The key settings is this in csproj file. So Klondike still works with .net standard libraries.

   <PropertyGroup>
     <DebugType>full</DebugType>
     <DebugSymbols>True</DebugSymbols>
   </PropertyGroup>

[chriseldredge]

I'm not sure how well Klondike handles .net packages built on ecosystems later than .net 4.5, but if you look in your Symbols directory on the filesystem, you should see the files there (e.g. Library.Test.pdb/92BD31265460470A86142B33172F2B57ffffffff/file.ptr). If you do not, Klondike's log file (~/App_Data/Logs/Klondike.log) may provide additional clues.

I haven't kept up to date with recent tooling, so it's certainly possible that the Windows Debugger Kit that Klondike uses to process symbols is not compatible with .net standard packages, assemblies and symbols.

[sberserker]

I don't see Library.Test.pdb folder generated.
I tried also setup on the same machine where Visual Studio is. I can see only this:

What is responsible for generating pdb? Can update Nuget dll help with this?

[chriseldredge]

I'm not sure, as I haven't tried much of anything in .net standard. Honestly I'm surprised Klondike works with these newer packages at all.

Klondike uses srctool, pdbstr and symstore from Debugging Tools for Windows to process symbols. The source code can be reviewed at https://github.com/themotleyfool/NuGet.Lucene/blob/master/source/NuGet.Lucene.Web/Symbols/SymbolTools.cs.

Did you take a look at Klondike.log? There isn't much in the way of diagnostic logging, but if any exceptions are being raised they would show up there.

[sberserker]

No exceptions or something which stands out from the logs.

[sberserker]

One step closer. Added this to .csproj file

   <PropertyGroup>
     <DebugType>full</DebugType>
     <DebugSymbols>True</DebugSymbols>
   </PropertyGroup>

Now i can see pdb info is generated after i pushed new package.

The only problem that Visual Studio is requesting different path

SYMSRV:  HTTPGET: /api/symbols/Library.Test.pdb/92BD31265460470A86142B33172F2B571/Library.Test.pdb
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND

SYMSRV:  HTTPGET: /api/symbols/Library.Test.pdb/92BD31265460470A86142B33172F2B571/Library.Test.pd_
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND

SYMSRV:  HTTPGET: /api/symbols/Library.Test.pdb/92BD31265460470A86142B33172F2B571/file.ptr
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND