Debugging not hit breakpoints in .NET CORE MVC 6 application - asp.net-core-mvc

Question

I am working on .NET CORE 1.0 MVC 6 application and I stuck with the debugging point as it stopping hitting yesterday. with number of try I delete project and start again. First time it load symbols even due I have uncheck in Tool --> Debugging --> symbols, however it hit breakpoints. Now it only hitting C# class 'Startup.cs' if I choose 'Enable Just My Code' but in controller. I have Debug option from dropdown, not really sure why. Need help here.
I change as
Select Debug->Options->Debugging->General
Tick Enable .NET Framework source stepping.
but still no success
Module
Trying to Hit in Controller home class for MVC Core in Index and about
public class HomeController : Controller
{
public IActionResult Index()
{
var x = 2 + 3;
return View();
}
public IActionResult About()
{
var x3 = 2 + 6;
var xx = "dd";
ViewData["Message"] = "Your application description page.";
return View();
}
Debugging output

Answer 1

actually your screen shot was not the debug output, it was the build output.
If you disable the "Enable Just My Code", and enable/disable the Microsoft symbols Server under TOOLs->Options->Debugging->Symbols, and then debug your app after you re-open it, how about the result?
If I create a new app, the breakpoint was hit normally, if I re-open the solution, actually it still could hit the breakpoint, but it is very slow. Like the screen shot 1, if you visit the "debug" output window, it would list the symbols loaded one by one, after about 1min, it would hit the breakpoint like screen shot 2. Of course, I enabled the Microsoft symbols under TOOLS->Options->Debugging->Symbols and disabled the Enable Just My Code for the above steps.
So for your issue, one possible reason is that it just loads the symbols slowly, just wait for a moment.

Answer 2

While Jack Zhai-MSFT's solution worked I still had some weird behavior: breakpoints were working partially. Found solution here that works perfectly: Breakpoint Failed to Bind - Visual Studio 2015
While the above link is loaded with tons of solutions in my case changing configuration from Release to Debug under Build menu Configuration Manager solved all my breakpoints related problems.

Answer 3

I thought I was running into this same behavior except in my case it was caused by Temporal Coupling in the Startup.cs class of my .NET Core MVC application.
I had included my app.UseMiddleware() call below my app.UseMvc() call and because of this my middleware component would initialize but was never hit by requests coming into my application. Moving my call to app.UseMiddleware call above the app.UseMvc call fixed this and now my requests are being properly routed through my custom middleware.
app.UseMVC MUST BE THE LAST "app.Use()" call in the Configure method of your Startup.cs class

Answer 4

I faced the same problem and none of the above solutions worked.
Finally I figured out below setting works like a charm.
Go to Tools->Options->Debugging->General->Uncheck "Use Managed Compatibility Mode" checkbox

Answer 5

Worked for me by enabling following Debugging option "Enable .Net framework source stepping"

Answer 6

This solved my problem
-> Close visual studio. -> Deleting .vs folder reopen visual studio. Doing this solved the problem breakpoint couldn't be hit