I have moved from VS Express for Web 2012 to Visual Studio 2017 Community Edition.
I am developing an MVC application.
One of the most shocking changes I've seen is that when I use Ctrl + F5 for testing, I sometimes get the previous build, so none of my new code changes go through.
I have to use F5 for the changes to go through. On my 2012 software, the changes just took every time.
I use Ctrl F5 a heck of a lot more and save F5 for the more confusing problems if I actually need to debug something. So much that maybe I should just change the hotkeys for this. I wonder if I'm the minority in this habit.
Anyway, is there a way to have Ctrl F5 return to the state where it accepts my new code changes?
I am developing an MVC application.
One of the most shocking changes I've seen is that when I use Ctrl + F5 for testing, I sometimes get the previous build, so none of my new code changes go through.
I have to use F5 for the changes to go through. On my 2012 software, the changes just took every time.
I use Ctrl F5 a heck of a lot more and save F5 for the more confusing problems if I actually need to debug something. So much that maybe I should just change the hotkeys for this. I wonder if I'm the minority in this habit.
Anyway, is there a way to have Ctrl F5 return to the state where it accepts my new code changes?