I'm currently trying to profile a way too slow usecase where the CPU spend most of its time in the EntityFramework.ni.dll module.
Unfortunatly as it's a .ni.dll, I don't have the related PDB file, so VS can't associate function calls inside it to the corresponding source code.
I saw on SO there is a way to build it back, but it takes to have the corresponding EntityFramework.pdb file and I don't have a clue on how to spot that file on my system anyway.
On the other hand I saw that I do have several EntityFramework.PDB files here and there.
So I'm wondering if there is a way to prevent usage of .ni.dll during profiling / debugging sessions thanks a VS configuration option or such ?
Please notice that right now the reference to the EntityFramework in my project is coming from the corresponding NuGet package and I'd rather avoid changing anything at this level if possible.
I agree that if such a trick exist, it will result in loading a distinct module than the one the performence trouble have been spoted. But I hope it can at least help me either diagnose the trouble if it's still slow or to spot where to find the original EntityFramework.dll thanks to Module window at debug time.
Thanks in advance for your help ! ;)