Portable PDB format support

switchblade

It appears that when you are profiling an application that references another assembly using the new portable PDB format introduced by Microsoft; ANTS reports that it does not have the source code for that referenced assembly and therefore can only provide method level timings at best via the decompiler.

Spec:
https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md

Repro:
I have a .NET 4.5 application that references a class library project that targets multiple framework versions (.NET Core, .NET Standard, .NET 2.0/3.5/4.0/4.5) using the new csproj format under VS2017. Attempting to profile the .NET 4.5 app does not provide any source code view for the referenced class library project. The class library project uses the new Portable PDB format instead of the traditional Windows only format.

Russell D

Hi, whilst this is a known issue, I'm afraid we don't have an ETA on when we'll fully support portable PDBs.

dke2

Hi, Has there any progress been made since mid '17? We are evaluating the current ANTS version (which happens to be 9.8.0.767 at the time of writing), but there seems to be still no way to see any source code for .NET Core or .NET Standard assemblies. At least for us, that's really a show stopper, because we usually use 'old' .NET Framework assemblies only as startup frame any more (if at all). The only workaround that we could think of so far, are Shared Projects, but that's not really a preferable way, is it?
Thanks for your reply in advance!

Russell D

@dke2 you'll need to upgrade to ANTS 10 which introduces full support for .NET Core (2.0). See https://forum.red-gate.com/discussion/83549/ants-performance-profiler-10-released / https://forum.red-gate.com/discussion/83550/ants-memory-profiler-10-released for more details.

dke2

Thanks Russel, brilliant timing ;-)