VS 2015 Update 1 - Claiming I am debugging a release build

Question

After updating to VS 2015 update 1, if I run a web project (MVC), stop the application, then try to run it again, VS stops and pops up a dialog claiming

Answer 1

I've been having the same issue since updating to VS2015 Update 1.

Found a similar report on Microsoft's Visual Studio Forums which points to a bug report that's been raised with them here

There are various workarounds but I think the underlying issue is that IIS Express is not shutting down when debugging is ended - and its not because of the edit and continue option being unchecked. Quickest workaround I can find until the bug is fixed:

• Right click on IIS Express icon in tray and exit it after debugging (Credit to David Totzke who supplied workaround on bug report)

Not great, but I don't think a proper solution is available at the moment.

Answer 2

As mentioned by @romanoza, Microsoft updated the (now missing) Microsoft Connect bug report, (previously located here, in case you are able to find an archive somewhere) with the following information:

Uncheck the setting Debug -> Options -> Suppress JIT optimization on module load (Managed only)

This is the workaround. They go on to say later:

We recommend folks leaving it unchecked as having it unchecked will improve both performance and the behavior of just my code in specific scenarios.

Lastly, the acknowledgement:

It is a bug that it doesn't work with that setting enabled and we're working on a fix for that situation in case some customers still want to debug with that setting turned on.

Update: Based on the comments, it appears that the box is now unchecked by default for some developers, and that checking it can fix the exact same problem in some cases. Very strange.

Answer 3

For me, I found 3 \Release\ folder refs in this FileListAbsolute.txt file:

C:\Projects\MyWebApp.Web\obj\Release\MyChildWebApp.Web.csproj.FileListAbsolute.txt

They were like this:

C:\Projects\MyWebApp.Web\obj\Release\MyChildWebApp.Web.csprojResolveAssemblyReference.cache

C:\Projects\MyWebApp.Web\obj\Release\MyChildWebApp.Web.dll

C:\Projects\MyWebApp.Web\obj\Release\MyChildWebApp.Web.pdb

And simply removing those 3 lines outside of VS then re-opening the solution solved the problem. Hope that helps.

Answer 4

The word from Microsoft is that this is a known issue (it originally went to the Debugger team, but was determined it was a build issue, and is now in the Project system team's hands. There are other bugs open on this issue, and it's rated Priority 1, so should be on track for the next update. Though as would be expected, no promises can be made as to when it will be released (or what is actually in the update).

So. It's known and is being worked on. At least turning off the “Enable Just My Code” in the Debugging General Options seems to be a work around for now.

Answer 5

Pretty sure this has been fixed in Visual Studio 2015 Update 2.

I used to see this all the time (multiple times per day), and have not seen it once since updating to Update 2.

Answer 6

I noticed the answers here are incomplete, I was having the same issue and it was solved by opening the project properties and under the build tab and debug configuration unchecking "optimize code". You also should check the configuration manager as mentioned above to make sure that is also sound. The answer came from this post and they should get the credit: VS2015 Project no longer runs in debug mode

Thanks,