I'm trying to debug a StackOverflow in the EntityFramework NuGet package (version 6.1.3). In order to see the stack frames I need the PDB file for EntityFramework.DLL and EntityFramework.SqlServer.DLL. However, I can't seem to get Visual Studio to download this from either the MSFT symbol sources or from SymbolSource.org (I can get other System PDBs and things like NewtonSoft.json). Are the EF PDBs available anywhere?

- 230,703
- 74
- 448
- 575

- 20,860
- 17
- 88
- 152
-
Did one of these answers worked for you? – Stefan Jul 20 '19 at 19:46
3 Answers
Now with pictures (as it took me about an hour of trial and fail)
Get DotPeek from Jetbrains (Standalone version)
Open
DotPeek
->File
->Open
-> browse to your projectbin
folder and openEntityFramework.dll
Right mouse button on
EntityFramework
then chooseGenerate Pdb...
Go to folder where you exported it and open
EntityFramework.pdb
folder (I know right!) then dig deeper till you find a fileEntityFramework.pdb
and copy it to yourbin
folder (next toEntityFramework.dll
).Go to
Visual Studio
->DEBUG
->Options and Settings...
->Symbols
then add yourbin
folder toSymbol file (.pdb) locations
- Run project and pray those breakpoints turn ripe red....
Edit: It sometimes starts running EF in optimized
mode that renders debugging pretty much useless which is a whole point of this question - if this happens
- Go to
Visual Studio
->Debug
->General
-> (at the very bottom)Use Managed Compatibility Mode
. Tick and Run project (if it gets optimized then untick and run, then tick again and run, then ....)
- To see if
EF
runs optimized without having to wait till it hits breakpoint Go toVisual Studio
->Debug
->Windows
->Modules
. Then when you run solution modules (2) should appear. Click it and findEntityFramework.dll
there should be column that says Optimized(Yes
= bad,No
= you can debug it).
Hope this saves you some time.

- 58,075
- 31
- 238
- 265
-
1
-
It seems that DotPeek doesn't hook itself to VS2017, but you can do the same process by using the GUI that is installed along. – Samir Aguiar Mar 30 '17 at 12:43
-
2For anyone else who is still setting Optimizations on there dll make sure the `Supress JIT Optomization on Module load` is checked – johnny 5 Feb 15 '18 at 16:50
-
1Do you really need to do step 5 if you already put the `.pdb` in your `bin` directory? I mean, you will have to change it for every project if you hardcode it... – JHBonarius Dec 09 '21 at 12:28
Download the source code: entity framework on codeplex
The download button is in the sub-menu on the Source tab
Once downloaded:
Build the solution/project
Navigate to the bin directory NB: it is not in the normal location, its set to
"..\..\bin\Debug\"
. See Project properties.
The EntityFramework.pdb and the EntityFramework.SqlServer.pdb are both there.
Also would of thought, it would be available by default or easier.

- 2,417
- 2
- 15
- 32
-
2
-
I'm surprised i didn't get any cred, #justsaying ;-) totally agree tho... had to dig to only get to this... – Seabizkit Nov 12 '15 at 10:05
-
-
One note: I didn't need the pdb file myself. I was hoping to get more info of my Exception. But the info was already there. I just had to inspect the $exception variable in the local variable window of visual studio. – Thomas Nov 12 '15 at 10:28
-
The problem with this answer is that it has to be the exact same version that you are running in your project. And EF hasn't always had a sensible versioning scheme – George Mauer Jan 06 '17 at 18:16
One of the ways is to use dotpeek as symbol server (load entity framework dll and add dotpeek serer address copied from dotpeek settings) - what is great about this approach, that it generated pdb matching used dll version automatically, what is not so great - it will not contain original comments from source code, etc.

- 8,430
- 6
- 50
- 91
-
This also works without the Symbol Server mode. You can generate a pdb file for an assembly and point Visual Studio to the folder dotPeek creates. – Fabrice May 25 '16 at 10:28