Profiler prompts for location of source code which is not your own source code
Published 28 August 2014
This article relates to both ANTS Performance Profiler and ANTS Memory Profiler.
ANTS Performance/Memory Profiler may prompt for the location of a source code file that is not your own source code when viewing the results.
When ANTS Performance/Memory Profiler produces performance profiling results in detailed mode or during memory profiling, information is collected about the assembly being profiled, including the method and object names, as well as the path to the source code files for these items. In some methods internal to the Microsoft .NET Framework, assemblies are compiled dynamically from source code internally without your knowledge. ANTS Performance/Memory Profiler also adds these methods and the source code file to its result set. Because the source code is created, compiled, and disposed of by the .NET Framework, it is no longer available and clicking on some internal Framework objects will trigger ANTS Performance/Memory Profiler to ask for the new source code location because the source code used to create these temporary assemblies no longer exists.
When this happens, the source code file name being requested is normally in the form of a globally unique identifier, for instance 'aaaaaaaa-bbbb-bbbb-bbbb-cccccccccccc.vb'
This message can be safely ignored. Alternatively, .NET Reflector can be used to decompile source code from the executable.