Visual Studio 2013 breakpoint issue with Razor

Question

For some reason, I cannot set a breakpoint in @functions when using Visual Studio 2013 . Here is an example:

However, the same type of breakpoint works in Visual Studio 2012 :

• If you move the @functions block at the top of the razor page in VS2013 , you can set the breakpoint at @functions .

• You cannot set a breakpoint in @functions if the block is somewhere in the HTML.

Does anyone know why? Maybe a mistake? . This is a big inconvenience if you port a web application from MVC4 or earlier, where @function blocks appear in HTML.

Answer 1

This seems like a known issue. See Error Message in MS Connect.

Description:

"After my upgrade to VS 2013, I can no longer debug javascript in MVC razor files."

http://connect.microsoft.com/VisualStudio/feedback/details/807088/unable-to-debug-javascript-from-the-vs-2013-ide-unable-to-set-breakpoint

Answer 2

I had all the same problems with "This is not a valid place for a breakpoint", and I also did not have code highlighting or intellisense on any of the Razor code. None of the solutions I could find resolved. First of all, because my problem was caused by a very stupid observation on my part, but just in case someone was here and made the same mistake, I thought I would share it.

If you have not physically created the view in Visual Studio, for example, if it was created with the NuGet package (Umbraco in my case), or if you opened an existing solution that does not belong to you ... The view may not be included in the project. You can see something like this

Please note that the Homepage.cshtml file is located there, and I can edit, compile, display it, etc. But I could not insert a breakpoint anywhere. Right-clicking on the file and selecting "Include in Project" was a fix for me.

Answer 3

What worked for me: Exclude the file, and then Include it again. Raised breakpoints right away.

Hope this helps!

Answer 4

What helped me overcome this problem was to enable the "ASP.NET" parameter in the project properties. See screenshot: