Ok I have just updated to Visual Studio 2013 Update 2. They are very excited about their updates to the debugger. However I am having nothing but headaches with it.
Before Update 2 I could set breakpoints in my .js files and run in IE and I would be able to break and debug within the IDE.
Now when I try and add a breakpoint to any .js file it immediately opens up the [dynamic] file and places the breakpoints. If I restart or refresh the breakpoints are lost and I have to reset them only for them to be erased again when I refresh.
This seems to be effecting only the .js files that are being called within the app. I have an SPA built on Durandaljs and Knockoutjs. In this instance it is a Modal that I am trying to break inside its viewmodel.
If I place breakpoints in one of the root page files, the breakpoint will persist but it still switches over to the [dynamic] file.
In our team we experienced those problems that you mention plus other ones. In addition to this there was a general slow down in the IDE. Update 2 RC was not stable enough and we went back to Update 1. We will be waiting for the official release to be out to try again.
So that was our takeaway: never try a non official update of VS again.
But maybe here people would suggest another solution.