"project type is not supported by this setting"

I installed VS 2008 SP1 on W2k3 OS. After I installed the beta version of ASP.NET MVC and tried to create a project like ASP.NET MVC, I get the following error.

"project type is not supported by this setting"

Let me know if you fixed this problem.

+70
visual-studio-2008 asp.net-mvc
Dec 03 '08 at 4:44
source share
23 answers

I tried some of the solutions posted here, but still not happy. Finally, I replaced ProjectTypeGuids with this one below in the project file and loaded a thin

<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>

+65
Oct. 15 '09 at 16:16
source share
β€” -

I ran into something and had problems with my own .

In short, try:

  • Run the Visual Studio command prompt as an administrator.
  • Execute:

     devenv /setup 

Then he leaves a little (VS2008 does not open), as soon as the invitation returns VS fire, and everything (can) return to normal operation.

I came across this when my MVC projects messed up when trying to run Entity Framework :)

+16
Mar 30 '09 at 5:58
source share

The problem is that MVC 2 is not fully backward compatible. Visual Studio cannot open MVC 1 applications without MVC 1 installed. Therefore, if you just install MVC 1, which can install along with MVC 2, you should be fine. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=53289097-73ce-43bf-b6a6-35e00103cb4b

+10
Mar 31 '10 at 18:32
source share

I had the same problem with MVC v1. Turns out I didn't install the "Visual Web Developer" feature.

This SO user had the same problem .

+8
Feb 04 '10 at 10:10
source share

My situation was somewhat different: I tried to open an existing MVC 3 project. It turns out I did not have MVC 3, installing it from here , fixed the problem for me.

+5
Oct 06 '11 at 17:31
source share

I installed the visual web developer from the Visual Studio 2008 DVD Studio installation and fixed the problem

+4
Feb 24 '09 at 15:33
source share

Tried to install ASP.NET MVC 1.0. This works for me.

+3
Apr 18 '09 at 16:18
source share

ewalshe - the same thing worked for me. I know this is an old post, just wanted to put it there for someone else. I had an existing version control solution (Vault), and I wanted to set up my home computer for development. I installed Visual Studio 2008 at home without the following options:

C ++
Visual basic
Visual web developer

When I pulled the solution out of the source control, all projects loaded EXCEPT into my web project - VS just didn't recognize it. A fresh install using the default options and restarting fixed my problem. I don’t have the time and desire to really find out which of the above requirements is necessary for web applications to work ... maybe someone will ring.

~ Ryan

+2
Jul 11 '09 at 0:33
source share

I was getting the same error and found this question in a google search for an answer. Most of the answers found in the search suggested that older types of projects are being moved to a machine with a version of Visual Studio installed. None of them applied to me.

I have VS2008 installed on a computer (running on 64-bit Vista) at work and the recently installed beta version of ASP.NET MVC without problems.

I wanted to replicate my work environment on my Mac, so I installed VS2008 with ASP.NET MVC beta in a WinXp installation running on Parallels VM. When I started creating a project with an ASP.NET MVC web application template, I got the error "project type not supported by this installation."

Finally, I got everything that works, another reinstall of VS2008 (clean installation, not repair). This time I choose the default installation options, and not configure things as usual. I usually cancel VB, mobile device, office and other development components other than C #. I have little free space on my Mac.

After a clean install of VS2008, I did a Windows update, installed VS2008 SP1, and finally installed a beta version of ASP.NET MVC.

It appears that when I set up the VS2008 installation, I unselected the necessary settings for the MVC beta to work properly. I don’t know what it is, I’m just happy that in three days I can play MVC material at home.

It has been a month since you posted the question. Have you made progress since then?

+1
Jan 07 '09 at 21:38
source share

This is sometimes caused by the launch of a version of Visual Studio that does not support MSTest.

+1
Jul 25 '09 at 20:51
source share

This may be obvious, but it is fixed for me. I installed ASP.NET MVC before installing Visual Studio 2008. As soon as I uninstall MVC and reinstall, I no longer had a problem.

+1
Oct 15 '09 at 21:15
source share

install ASP.NET MVC 1.0. This works for me.

+1
Jan 23 '10 at 6:44
source share

On Windows 7, if you do not work as a local "Administrator" and enable UAC, the installation will automatically fail. The solution is to disable UAC, reboot, and the installation should succeed.

+1
Mar 12 '10 at 21:10
source share

If you are trying to start an MVC application, try starting AspNetMVC1.msi . This worked for me, so hopefully it will solve your problem.

+1
Jan 10 '11 at 11:59
source share

I continued to face this problem. Running devenv / setup and devenv / resetsippkgs did not work for me. There was also no removal of design guidelines. I installed MVC 1.0 and it still didn't work. Then I installed MVC 2.0 and it seems to have done this.

+1
Jan 12 2018-11-12T00:
source share

I had MVC 2 installed on my machine and I was still getting this error message. I installed MVC 1, no GO. I installed web Developer No GO. I finally uninstalled MVC1 and MVC2 and then reinstalled MVC2: http://www.microsoft.com/Downloads/en/details.aspx?familyid=C9BA1FE1-3BA8-439A-9E21-DEF90A8615A9&displaylang=en

Reinstalling MVC 2 solved the problem for me. Hope this helps someone else.

thank

+1
May 3 '11 at 17:58
source share

VS2008; ASP.NET MVC 2 on a 64-bit machine that received this problem:
"project type is not supported by this setting"

Solution: Thanks to Bert Hageben from above. In the "Installing VS" section of the "Start" menu in the "VS Tool" folder, VS2008 x64 Cmd Prompt is running. The executed commands:

 devenv /setup 

... still a project error and did not open, then launched

 devenv.exe /resetskippkgs 

... and then success!

+1
Jul 20 2018-11-21T00:
source share

I had to rebuild the VM for development in order to solve this problem. Clean FTW installation.

0
Jul 25 '09 at 20:48
source share

Tried @ryan and @Rob Cooper answers without joy. Running this in VHD on Win7.

It is zoned on Mvc and that where there is a problem. Not 100%, but I think the problem is that I tried to open a project that did not have the latest version of Mvc in a new assembly.

The workaround is to roll back to the previous version of Mvc. Then, when this one is happy, upgrade the project to the latest Mvc, and then start the machine.

0
Sep 11 '09 at 16:17
source share

There was a problem with this problem when I started VS2008 by accident while starting the ASP.NET MVC installation. Closed VS, uninstalled ASP.NET MVC, then reinstalled it and everything worked fine.

0
Jan 19 '10 at 13:51
source share

The Vivek Ayer solution also worked for MbUnit projects. In addition, the first GUID was simply deleted (instead of replacing it with "{349c5851-65df-11da-9384-00065b846f21}").

0
Dec 02 '10 at
source share

If you are using Visual Studio 2010 and want to open / create MVC 3, you must have the Visual Web Developer Visual Studio component installed.

If you performed the default installation without configuration, then this component is installed.

If you perform an individual installation and assume that you want to use only C #, you can disable the Visual Web Developer component, assuming that you do not need it. This is a must have for any MVC development. Just run VS setup and make sure this component is selected.

Downloading and installing MVC 3 will work correctly even without a component installed. However, you cannot open or create an MVC 3 solution.

0
Feb 21 '12 at 19:24
source share

The trick to solve this problem is ProjectTypeGUID, but the GUIDs listed elsewhere in this and other posts do not work for me.

At the end (and this is my suggestion) I created a new MVC project, then open the * .vbProj file and copy the ProjectTypeGUID objects found there. When I transferred them to the vbproj file of the project that I was having problems with, everything started working.

In my case (for an existing VS10 VB project) the correct GUIDs were:

 <ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids> 
0
Mar 27 '13 at 9:32
source share



All Articles