9

After installing Debugger Canvas and restarting Visual Studio, I get this error for each project when opening a solution:

Project <Name> could not be opened because the Microsoft Visual C# 2010 compiler could not be created. Please re-install Visual Studio.

I tried all of the answers from this question with no luck: Microsoft visual C# 2008 compiler could not be created. Please re-install Visual Studio

So far I have:

  • Tried the /resetsettings argument
  • Tried the /ResetSkipPkgs argument
  • Tried removing the whole key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio

Any other ideas other than reinstalling VS and/or SP1?

VS Version: 10.0.40219.1 SP1Rel

Thanks!

Community
  • 1
  • 1
alf
  • 18,372
  • 10
  • 61
  • 92

4 Answers4

25
  1. Open VS command prompt
  2. Run the following command

    devenv /resetsettings

  3. Open your Project

H A
  • 1,251
  • 2
  • 24
  • 39
  • 2
    I got "Project 'X' could not be opened because the Visual C# 2015 compiler could not be created" in Visual Studio 2015. devenv /resetsettings fixed that issue for VS 2015 too. – Sergey Oct 16 '15 at 04:14
  • 2
    @Sergey it didn't solve mine, I am still getting "Visual C# 2015 compiler could not be created" while creating a new project. Note: I tried all the mentioned answers!!! – Soumyaansh Jan 12 '16 at 08:40
  • @Sergey I am facing the same problem with same VS 2015. But it message me to reinstall VS. While I have run to repair it – Ajay Sharma Jan 29 '16 at 10:33
11

After trying everything, I fixed this by reapplying the SP1, without needing to reinstall the whole VS. Hope it helps someone else!

alf
  • 18,372
  • 10
  • 61
  • 92
0

I had a similar problem, but the error message also included "Query Service for { } failed." I tried opening VS with both the /ResetSkipPkgs and /ResetSettings switches, which didn't work. I finally fixed it by deleting the following registry key.

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio

Visual studio will lose all user preferences the next time you start it.

John Gilmer
  • 831
  • 1
  • 11
  • 18
0

VS2015 - My issue was in the sln file. Reverting to previous revision resolved the issue.