Last post Mar 13, 2019 01:04 PM by AddWeb Solution
Dec 15, 2016 04:41 PM|kdn102|LINK
I have googled this and found lots of suggestions on what to do, but none of them work.
This was working just fine last week. The only thing I've installed in the last week was SSMS 2016.
If anyone who has ideas on how to get passed this, I would appreciate it!
Dec 16, 2016 02:45 AM|Chris Zhao|LINK
What is exact error? Could you share screen shot?
Dec 18, 2017 08:52 PMfirstname.lastname@example.org|LINK
Was this ever resolved?
I am still getting this with VS2017 building ASP.Net Web
Mar 08, 2019 10:08 PM|10ktoday|LINK
I have just started getting the same issue with Visual Studio 2017 after installing SSMS v17.9.1
Did you ever solve this?
Mar 13, 2019 01:04 PM|AddWeb Solution|LINK
Forcing you to stop debugging, edit, start debugging again. Then here’s a solution:
1. Stop running your app.
2. Go to Tools > Options > Debugging > Edit and Continue
3. Disable “Enable Edit and Continue”.
If you find that Visual Studio doesn’t alert you that files have changed and that confuses you when debugging do this:
1. Go to Tools > Options > Debugging
2. Enable “Require source files to exactly match the original version”.
Now run your application again and feel free to edit while you run the application, you will have to rebuild it in case you want to check the code though.
Hope its work fine for you.