Can no longer debug typescript files in Visual Studio 2013 Update 3

Not even sure how this has happened, but I was able to use Visual Studio and debug with Internet Explorer 11 for the longest time without any issues. Then, one day the breakpoints started not to load. After emptying the cache in Internet Explorer, they loaded again. Now, they are consistently not loading. The Script Document shows the javascript files that are compiled and I can debug in Firefox (even the typescript files) so I assume the map files are correct. I have reinstalled Visual Studio and IIS just to eliminate any of those being an issue, so I am now turning here and hopefully this is just some simple issue.

I have gone through at least 20 possible solutions for this issue and the fact that I can hit a breakpoints in the Script Documents tells me something is up.

[basarat]

Can you debug a simple pure JavaScript files from VS2013?

Yes, I can hit breakpoints that are javascript files even in that same project (IE. Knockout.js). It is only the typescript files I seem to not be able to trigger a break point claiming the symbols have not been loaded.

[basarat]

@zenoware what does this button say for you in IE11 debug tools:

It does say the same thing as what you are displaying:

[RyanCavanaugh]

If you can debug the source maps correctly in FireFox but not in IE, you'll probably have to take this to the IE F12 tools team. I'll point them in this direction and see if they can follow up for more details.

[paulvanbrenk]

@zenoware

Just to clarify you are not able to hit breakpoints in either VS or IE, but this works as expected in Firefox?

Are you able to hit breakpoints in Chrome? Which version of VS are you using, are any updates installed? Which version of IE are you using (can you paste the complete version number from the about box)?

Can you post the full last line from the generated js file you're having trouble with? The one which shows where to find the sourcemap.

@paulvanbrenk to answer your questions:

this works as expected in Firefox?

• Yes, I can debug the ts files from Firefox
  Are you able to hit breakpoints in Chrome?
• Yes, just tested it and I can hit breakpoints in ts files.
  Which version of VS are you using, are any updates installed?
  

Which version of IE are you using (can you paste the complete version number from the about box)?

Can you post the full last line from the generated js file you're having trouble with?
First off, it is every single ts file i have. Even on different projects. Here is one example:
//# sourceMappingURL=Forest.js.map

@RyanCavanaugh Thanks for showing them this as well. If I cannot resolve this, I will attempt a few more things before reverting to re-installing windows (very last effort)

[ahbn]

I met the same problem. Update2 do not have this problem, you can uninstall the Update3.
In the installation Update2。

@ahbn That is a shame because isn't TypeScript 1.0 on Update 3? If it works, that is what I will do.

@ahbn Reverting back to Update 2 did fix my problem! Thanks for the information. I am curious why this is an issue with Update 3? So there is a work around but still an issue that needs to be investigated. But is it an IE issue or a Visual Studio issue is something I am not sure about.

[ahbn]

I try to reinstall the system, directly install Update3 cannot breakpoint problems arose, and then I switched back to Update2, is normal, then I install Update3 again on this basis, the problem appeared again, so I feel that the problem may be Update3. Currently I use normal under the Update2.

[sheetalkamat]

@zenoware, can you please provide simple repro project for us to investigate? I would like to see your project settings, js file, map file contents and paths for sources etc.
Do you see any message in output window of VS? VS normally shows the error why the source map cannot be read.