{
  "$type": "site.standard.document",
  "canonicalUrl": "https://johnnyreilly.com/posts/ie-10-install-torches-javascript",
  "description": "Learn how to fix missing Script Documents when debugging JavaScript in Visual Studio 2012, likely caused by auto-updating from IE9 to IE10.",
  "path": "/posts/ie-10-install-torches-javascript",
  "publishedAt": "2013-04-17T00:00:00.000Z",
  "site": "at://did:plc:yy3apqjlms24kso7ahn7lbmb/site.standard.publication/3mova7c4nho2b",
  "tags": [
    "visual studio",
    "javascript"
  ],
  "textContent": "OK the title of this post is a little verbose. I've just wasted a morning of my life trying to discover what happened to my ability to debug JavaScript in Visual Studio 2012. If you don't want to experience the same pain then read on...\n\n\n\nThe Symptoms\n\n1. I'm not hitting my JavaScript breakpoints when I hit F5 in Visual Studio.\n2. Script Documents is missing from the Solution Explorer when I'm debugging in Visual Studio.\n\nThe Cure\n\nIn the end, after a great deal of frustration, I happened upon this answer on Stack Overflow. It set me in the right direction.\n\nI was seeing exactly the same as this list but with TWO instances of Internet Explorer in the list instead of one. Odd, I know.\n\nI fixed this up by selecting Google Chrome as my target instead of IE, running it and then setting it back to IE. And interestingly, when I went to set it back to IE there was only one instance of Internet Explorer in the list again.\n\nThe Probable Cause\n\nMy machine was auto updated from IE 9 to IE 10 just the other day. I \\think\\ my JavaScript debugging issue appeared at the same time. This would explain to me why I had two instances of \"Internet Explorer\" in my list. Not certain but I'd say the evidence is fairly compelling.\n\nPainful Microsoft. Painful",
  "title": "IE 10 Install Torches JavaScript Debugging in Visual Studio 2012 Through Auto Update (Probably)"
}