Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • $\begingroup$ Well, it seems that this was a hit and run question. The OP has disappeared. If anyone can test if this solution is working, please comment so we can finalize or delete the answer. $\endgroup$ Commented Feb 5, 2014 at 18:15
  • $\begingroup$ I can confirm that this does not fix the issue. Think I will have to reinstall VS2012 now, crap! $\endgroup$ Commented Feb 8, 2014 at 19:39
  • $\begingroup$ @RunnyKine Before you do that, let's experiment a bit ... does the VS120COMNTOOLS environment variable exist on your system? What is its value? $\endgroup$ Commented Feb 8, 2014 at 19:43
  • $\begingroup$ It exists, I can't see the full value but it's C:\Program Files (x86)\Microsoft Visual Studio 12.0 ... $\endgroup$ Commented Feb 8, 2014 at 19:50
  • $\begingroup$ @RunnyKine OK, did you actually edit the file I referenced in the post, the way I described? (Make a backup of the original and put the backup in some other directory.) If not, please try actually editing, and make one more change: look up the line starting with $VisualStudioVersions and add "2013" at the beginning of that list. Let's see if it works when both changes are done. $\endgroup$ Commented Feb 8, 2014 at 19:54