4
votes

Sometimes while debugging in Visual Studio 2013, I get hollow breakpoints and this message for them:

The breakpoint will not currently be hit. Unexpected symbol reader error while processing App_Web_i5dbbmvv.dll (Server-side symbols).

When this happens, the breakpoints will not be hit (obviously). Additionally, if I get an exception while running in this state, I'll get the message "The source file is different from when the module was built. Would you like the debugger to use it anyway?"

Building again does not fix this. Sometimes a clean-and-rebuild will do the trick, other times I have to clean -> exit VS -> reopen VS -> build.

This is the same error as this post VS 2012 debugging Unexpected symbol reader error while processing <file.exe>

but the posted solution is for C++, and that option appears to not exist when developing C#.

1
Are you using ASP.NET? - demoncodemonkey
yes, it is an MVC application + a WCF service. - friggle

1 Answers

3
votes

If you're using ASP.NET then try deleting your generated temp files.

clean up %windir%\Microsoft.NET\Framework\ VERSION \Temporary ASP.NET Files