Visual Studio 2012 failed to create project

Question

I just upgraded to windows 8 from windows 7. Visual studio 2010 broke down completely. Oh well. I removed vs2012 and installed visual studio 2012, where the pain starts. I h

Answer 1

The trace of this issue leads to Windows Imaging Component (one solution proposed was to remove FastPictureViewer, which codec affects WIC, but it was not my case). I used procmon to log all file and registry calls and found that VS2012 stumbles at the following key:

HKLM\SOFTWARE\Classes\.png - REG_SZ Content Type

I was suprized to see that Content Type for .png was set application (for .jpg it was application as well). After correcting it to image/png, not only VS2012 started successfully, but VS2010 as well, that was showing "Provide value on System.Windows.Baml2006.TypeConverterMarkupExtension threw an exception" on Win8 and caused me to try VS2012.

Answer 2

To resolve that problem, I've change the permission of "modify" for "everybody" on the files

c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config

and

c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config

Don't know if it's the best way to do it, but at least it works.

Answer 3

Just happened to me. As Eric Aubry said check the machine.config file. In my case it wasn't permission error but the fact that the file was destroyed internally. By renaming the machine.config.default everything was fixed.

Answer 4

Do you have any codec packs installed on your system? I had a WIC codec pack for viewing RAW files in Explorer, and it resulted in the same issue you are describing. Uninstalling the codecs fixed Visual Studio for me.

Answer 5

I was having various issues, including the above.

To resolve the problem on Windows 8 for VS 2012, setting it to run as administrator fixed the problem for me.

Launch icon properties->Advanced Properties->Run as administrator

I hope this helps.

Cheers, Sean

Answer 6

For me, this happened when I installed mysql on my machine, and it added an extra connection string to my machine config. However, since I was using a separate file for configSource, it resulted my machine config to become corrupted.

Moving the new config key to my config source from the 32bit machine config solved the issue.