IndexSources TFS 2015 build step fails with Microsoft.IdentityModel.JsonWebTokens.pdb

[Saurbaum]

I'm seeing this in my overnight builds using the latest released build on nuget 5.3.0

Indexed source information could not be retrieved from d:\dev\Binaries\Win32\Release\Microsoft.IdentityModel.JsonWebTokens.pdb. Error: Symbol indexes could not be retrieved.

This is triggered before we publish our symbols to our server using https://msdn.microsoft.com/en-us/windows/desktop/microsoft.teamfoundation.build.workflow.activities.indexsources. and we are using Team Foundation Server 2015 Update 3.

If I'm reading this error message properly the pdb produced and packaged in nuget is made using a portable format. Can you confirm that is the case and is there anything I can do to get around the error?

[brentschmaltz]

@Saurbaum is this happening for any other assemblies?

[Saurbaum]

So far it's only that one but it's entirely possible that the rest of the IdentityModel assemblies have the same issue.

Unfortunately the Build step bails out on the first error so I'm unsure if it will affect the others.

[Saurbaum]

If I'm right https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/nuget#symbol-packages has the suggestions on how to distribute pdbs using nuget.

https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg

That then keeps the pdbs out of the nuget package and away from the Index Sources build step.

[brentschmaltz]

@Saurbaum we will try and get this into the next release.

[dozer75]

Stumbled into the same issue today and searched quite a bit on the net before I found this issue here.

Anyway, during that search I found that this seems to be an issue with the fact that the pdb file delivered with the nuget package is portable even for .NET targets. Not all external tools (like Visual Studio 2015, .NET versions 4.7.1, symbol server) supports this (see portable information at the dotnet/core team).

So I think that the solution here is the solution referenced here. It seems to have fixed problem with their nuget package.

[GeoK]

@Saurbaum We are going to ship our .pdbs in separate .snupkg packages (#1172). This should unblock you.
@dozer75 Thank you for chiming in. You are right, portable PDBs are not supported everywhere but the main advantage is that they can be created and read on all platforms.