Visual Studio Development Bookmark and Share   
 index > Visual Studio WPF Designer > The project type is not supported by this installation.
 

The project type is not supported by this installation.

After having installed all the RC1 parts, including "Orcas" and try to create a new project in VisualStudio 2005 (Windows Application, XAML Browser Application or Custom Control Library) I get an error message:

"The project file '.....' cannot be opened.

The project type is not supported by this installation."

I've tried reinstalling everything but it's still giving the same error message.

Could it be because I'm running a swedish version of Windows XP? Although I haven't had this problem with other releases.

Ted  Friday, September 08, 2006 7:10 AM

You could also try to run the following command:

devenv /ResetSkipPkgs

This will try to load any Visual Studio packages that failed previously at some point, such as the WPF project flavor package, which would cause the error message you're seeing.

Marco Goertz - MSFT  Monday, September 11, 2006 4:19 PM

Well, I answered my own question...but hopefully I can help someone else.

I reinstalled VS.NET 2005 C# Express again and this time it works. I guess the problem was that I installed Orcas after I had reinstalled the IDE. It would appear that it has to be installed after everything else.

Schwegs  Thursday, September 21, 2006 12:14 AM
Resolution for my case can be found here
Dmitry Pavlov  Saturday, October 14, 2006 8:59 AM
Nothing to do with the Swedish version -I have the same error on my US-English version. Really hoping to get an answer on this one.
SpartyGuy  Friday, September 08, 2006 5:53 PM

Got the same problem.. Updated to RC1 and now I can't work.. Pleeeaaase resolve this for usMicrosoft!

"The project type is not supported by this installation"

When opening the old WinFX projects or trying to create a new project, all the same.

Fangorn123  Monday, September 11, 2006 1:04 PM

I found something that solved the problem for me anyway, in the Web page opened at the end of the installation of "Orcas". Under "Setup issues":

Open the run-dialog (start-->Run) type "devenv /setup" and press ok.

Opening an old project or creating a new project, works for me now. Hope it does it for you guys too.

Good luck!

/Jens

Fangorn123  Monday, September 11, 2006 2:29 PM

You could also try to run the following command:

devenv /ResetSkipPkgs

This will try to load any Visual Studio packages that failed previously at some point, such as the WPF project flavor package, which would cause the error message you're seeing.

Marco Goertz - MSFT  Monday, September 11, 2006 4:19 PM

Hello we would like to investigate this issue to understand what might cause you to see this error message. Can you please help elaborate more on your installation steps.

Did you install Development Tools and its prerequisites from the from the following locations?
.NET Framework 3.0 RC1
http://www.microsoft.com/downloads/details.aspx?FamilyId=19E21845-F5E3-4387-95FF-66788825C1AF&displaylang=en
Windows SDK (Optional if you want integrated help)
http://www.microsoft.com/downloads/details.aspx?FamilyId=117ECFD3-98AD-4D67-87D2-E95A8407FA86&displaylang=en
Development Tools for .NET Framework 3.0 RC1
http://www.microsoft.com/downloads/details.aspx?FamilyId=935AABF9-D1D0-4FC9-B443-877D8EA6EAB8&displaylang=en

Can you reproduce this issue on a clean machine (one that has had no prior installs of the development tools or .NET framework 3.0) or has this machine had previous versions of either the .NET Framework 3.0 or development tools installed?

If this is not a clean machine what prior working versions of the .NET Framework 3.0 & Development Tools did you have before uninstalling them and then installing the RC1?

Did you ever use this command to install the Development Tools on your machine, "msiexec /i vsextwfx.msi WRC_INSTALLED_OVERRIDE=1"?

What operating system version and os language are you using?

Thank you

Anthony

ACangialosi  Monday, September 11, 2006 5:51 PM

Thanks Marco. This seemed to do the trick. I'm now able to both create new projects and also open other WPF projects. Thanks again.

Ted  Tuesday, September 12, 2006 5:39 AM

Anthony,

Trying to answer your questions...

Yes, it was downloaded from the locations you listed.

Unfortunatly I don't have a clean machine to try on, both my development machines have had several CTPs installed. And I only had this problem on one of the machines, the only difference between the machines are that on the corrupted one, the operating system is swedish and I also forced an install of the June CTP of Orcas ontop of the July CTP of .Net Framework 3.0 using the WRC_INSTALLED_OVERRIDE trick.

Ted  Tuesday, September 12, 2006 5:44 AM

Hmmm...this didn't do the trick for me.

I was previously running June CTP (with sdk, orcas, etc). I followed all uninstall instructions beforehand, and installed (in this order)

  1. RC1 framework
  2. SDK
  3. uninstalled/reinstalled VS.NET 2005 C# Express
  4. Orcas

at the same locations listed in the post above.

I did have the flavor error after step #3 (in addition this error), but installing Orcas took care of that one. I also tried both commands listed in this thread, neither of which seemed to help.

I should note that I do have VS.NET 2003 installed too, and when I run devenv /ResetSkipPkgs it opens 2003, not 2005 express.

Any suggestions?

[EDIT: I can run XAMLPad and open & run projects in VS.NET 2005 C# Express that I didn't create (such as from the SDK samples).]

Schwegs  Wednesday, September 20, 2006 11:18 PM

Well, I answered my own question...but hopefully I can help someone else.

I reinstalled VS.NET 2005 C# Express again and this time it works. I guess the problem was that I installed Orcas after I had reinstalled the IDE. It would appear that it has to be installed after everything else.

Schwegs  Thursday, September 21, 2006 12:14 AM

That's correct you have to install it after everything else

mark

Mark Boulter  Thursday, September 21, 2006 4:48 PM

I have created my own package with custom project type for custom language. I have also created the installer for my package and when I try to install it on "clear" virtual PCI have got the same error message:

"The project file 'THAT STRANGE BUT THERE IS A PATH TO THE PROJECT IN THE TEMP FOLDER OF MY USER PROFILE' cannot be opened. The project type is not supported by this installation."

There are two weird things:

1. The fact the error occurs :)

2. Path to the project in errror message. I set the path 'C:\Projects' in New Project dialog.

The testing machineworksunder Virtual PC. Environment is very "clear". It is a WinXP Pro SP2 withVisual Studio 2005 Team Suite installed. And the second application I installed was my package.

Well, as you can see neither Orcas nor anything else can influence this error.

Please help me. Any ideas are welcome!

Thanks!

Dmitry Pavlov  Sunday, September 24, 2006 10:56 AM
Resolution for my case can be found here
Dmitry Pavlov  Saturday, October 14, 2006 8:59 AM

Hiya

To help with the investigation - I am running VS 2005 Team System for SD on XP Pro SP2 English with all latest updates. I downloaded and installed all the RC1 files as this is the only version with a GoLive licence. The rest of WinFX works fine its just WPF that doesn't work for me with the project type not supported error.

The wierd thing though is that if another user logged onto my machine the WPF stuff works fine. We even ghosted another working machine and it still doesn't work for me. This problem therefore must be caused by a setting siomewhere and isn't actually an installation problem.

For me the problem was solved by running devenv /setup

BabyGBear  Wednesday, October 18, 2006 11:15 AM
I am having the same problem with a solution I downloaded where the entire solution is in C#, and only one of the component projects doesn't work. I tried both dos prompt commands to no avail, and trying to reinstall the microsoftSDK from the location provided requires I uninstall later versions of the SDK (V6.0.6000.0) to install the one linked (V6.0.5536.0). Are there any other ideas?
SACCETTANYC  Monday, January 08, 2007 9:44 PM

Thanks - this solved my problem when upgrading my older version of 'orcas' to the December 'January' CTP.

Cheers, Jonathan

Jonathan F  Monday, January 22, 2007 9:07 PM

Install Microsoft® Visual Studio® 2005 Team Suite Service Pack 1

I got my problem fixed with it...

http://www.microsoft.com/downloads/details.aspx?familyid=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en

Rajesh2516859  Friday, March 30, 2007 6:50 AM

Same Here.....

My project was previously built in VS 2003...Now I am trying to open it in VS 2005...

Do I need to do any special settings.....

Anand Thakare  Thursday, May 24, 2007 4:40 AM

Top Banana!

Thanks V. Much.
Its alive.................!

FlemGrem  Thursday, October 11, 2007 9:35 AM

Jens workaround did the trick for me. Thanks Jens.

-Alok

alokverma  Friday, February 15, 2008 11:20 AM

Thank's it works very good...

ioPaul  Tuesday, February 26, 2008 5:29 PM

I am having the same issue. I am going to unstall and then install Visual Studio 2008.

Manoj Kholia  Tuesday, April 29, 2008 8:57 PM
Thanks Fangorn it worked for me
Sarvesh Sharma  Sunday, March 22, 2009 11:27 AM
thanks Fangorn123
I have the same issue, run devenv /setup from vs command promt works.
that's a solution.
qhuflf  Thursday, March 26, 2009 6:54 AM
Fangorn123 said:

I found something that solved the problem for me anyway, in the Web page opened at the end of the installation of "Orcas". Under "Setup issues":

Open the run-dialog (start-->Run) type "devenv /setup" and press ok.

Opening an old project or creating a new project, works for me now. Hope it does it for you guys too.

Good luck!

/Jens



That works!~
qhuflf  Thursday, March 26, 2009 6:55 AM

You can use google to search for other answers

Custom Search

More Threads

• Custom Control Designer
• Working under designers
• Reflecting in Design.dll
• Compile-time conundrum
• WPF Bug removing source from web browser
• Design-Time View
• Bug - Syntax Highlighting in XAML Editor
• DataTemplate Converter problem
• WPF- UIElement
• Intercept XAML Designer Selection Events