Cannot debug IIS deployed ASP.NET Core MVC on full .net framework

Question

I am stuck for over an hour already trying to debug my ASP.NET Core MVC application. It is using Full .Net Framework 4.6.1

Debugging using IIS Express works like a charm, but when deploying the project to IIS, I am attaching Visual Studio Debugger to "w3wp" process, it attaches but I keep seeing my breakpoints not enabled due to lack of symbols.

I have tried quite a few combinations of attaching the debugger, updated visual studio (I am using VS 2017), but all without any luck.

I have tried both stackoverflow and MS docs, but nothing for debugging ASP.NET core targeting full .NEt framework.

The worst thing is that I had a similar issue a few weeks ago, but did not record how it was resolved.

Any idea on what I am doing wrong?

Update: Issue happens on Windows Server 2012 R2, but on Windows 10 debugging works as expected.

When looking at the processes, there is also one named after my project, but it also does not break on breakpoints, also shows that symbols are not loaded, though I tried specifying symbols via Debug -> Options -> Debugging -> Symbols. — Andre Platov
– Andre Platov, Commented Aug 18, 2017 at 21:00
Tried deploying it on Windows 10 - no problem. The issue is happening on Windows Server R2 — Andre Platov
– Andre Platov, Commented Aug 19, 2017 at 0:04

Andre Platov · Accepted Answer · 2017-08-19 01:34:24Z

7

Okay, I think I understand what happened.

First of all, root causes:

I was not debugging the correct process initially. It was not usual w3wp, instead it was the name of my project (like "MyAspNetCoreApp").
While monkeying with Debug settings, I disabled "Enable Edit and Continue" setting and enabled "Use Managed Compatibility Mode". It apparently made things only worse.

Whew...

Now, troubleshooting that helped resolve the issue:

I ended up trying to debug my app on Windows Server remotely. Using this MS article helped me setup remote debugging for my Visual Studio (2017).
I then successfully attached to the process on Windows Server (My VS was on Windows 10)
That hinted that the issue has most likely something to do with VS, since remote debugging worked.
At that point I went on to check the debugging settings in Both Visual Studios, one on Windows Server and another on on Windows 10.
This is when I noticed the difference, changed it on Windows Server's VS and it worked!!!

What was very confusing, is that Microsoft's documentation was always using w3wp and now dotnet processes as ones to attach to.

Do not get me wrong, the ability to attach to the process by the assembly name is awesome, I only wish it was clearly reflected in the documentation. Hopefully the folks will catch up soon :)

answered Aug 19, 2017 at 1:34

Andre Platov

1882 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jack Zhai Over a year ago

Since this issue has been resolved, if possible, you could mark your solution as the answer, so it could help other community members who get the same issue as yours. Have a nice day:)

Andre Platov Over a year ago

Thanks for reminding me. On some reason I had to wait for 2 days before I could do that.

Collectives™ on Stack Overflow

Cannot debug IIS deployed ASP.NET Core MVC on full .net framework

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related