Reputation: 17806
I can create new MVC projects and they work and run however trying to open an existing project is not working at all.
I tried the following changing the project type to:
<ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
(this worked on migrating a project from Asp.Net MVC preview 1 to preview 2 BTW)
Changed the Reference to:
<Reference Include="System.Web.Mvc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
</Reference>
I tool this from a new project I created so i know that should be OK (I even hardcoded the path to the same result).
Still I get the dreaded:
The project file '.....csproj' cannot be opened. The project type is not supported by this installation.
I also tried devenv /setup
and installing the SP1 for Visual Studio.
The project I'm trying to open is this one (a DevExpress sample of a grid working on ASP.NET MVC).
Upvotes: 28
Views: 23129
Reputation: 17806
ok the problem was too many changes, I unzipped the solution again and just changed
the first parameter in the ProjectTypeGuids
to {F85E285D-A4E0-4152-9332-AB1D724D3325}
so it looks like
<ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
and I can see the project hurray!
Upvotes: 18
Reputation: 1634
There is a really easy way to solve this.
Probably some of the dependencies are missing, and it is really hard to find out which one.
Go to
Download ASP.NET and WebTools for your version of Visual Studio
A web platform installer will come up, which will install all the required tools
This solved my problem
There is no need to go through the ProjectTypeGuids
Upvotes: 0
Reputation: 1029
Just had a similar problem when taking an older MVC / Azure WebRole project into VS 2012 with MVC4. The trick was to edit the .CSPROJ like this:
10c11
< <ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11
da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
---
> <ProjectTypeGuids>{E3E379DF-F4C6-4180-9B81-6769533ABE47};{349c5851-65df-11
da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
i.e. change the first one from {F8... to {E3E3... (which is apparently MVC4). This has to be done outside of Visual Studio, in a text editor, and then open the solution and "Reload" the project that gave an error - this will trigger VS to migrate it to VS 2012.
Upvotes: 25