Visual Studio 2008 (ORCAS) "Project Creation Failed"
--Alice Kahn
This is due to some assembly redirects that are added to the devenv.exe.config file by installing the GAX (Guidance Automation Extensions).
Here is the fix, and it's an easy one:
1) Navigate to: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE in Windows Explorer
2) Load devenv.exe.config in your favorite text editor.
3) Find this string: "Microsoft.VisualStudio.TemplateWizardInterface"
4) Comment out the element so it looks like this:
<dependentAssembly>
<!--assemblyIdentity name="Microsoft.VisualStudio.TemplateWizardInterface" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /-->
<bindingRedirect oldVersion="0.0.0.0-8.9.9.9" newVersion="9.0.0.0" />
</dependentAssembly>
5) Restart Visual Studio 2008. All fixed!
Labels: ORCAS, VISUAL STUDIO


31 Comments:
Thanks!
Saved me some serious time!
Nuri
super!
thanks!!
Thank you very much
I did not find in that file Microsoft.VisualStudio.TemplateWizardInterface
and I still get this error when creating database project, please somebody help me
I've published a tiny ui-based tool that applys the described patch automatically.
You can downloaded it at http://www.codeplex.com/gaxpatch.
I don't have a devenv.exe.config file the only config file that I have şs VCExpress.exe.config
Thanks guys. Had problems with a Workflow project. I had just installed the Guidance Automation for the web services factory (studio 2005), looks like that was the conflict.
How microsoft release a product that doesnt work from the first step ??? Incredible ! Microsoft retail versions are just beta!
( w/e I dont have that line )
Sorry, but it looks like you don't get it. The product works fine, it's just that installation of the GAT causes a configuration file entry that needs to be corrected, OK?
Hi - I am getting the same sort of error while trying to create "Excel Workbook Project" from VS2008. Once I click the OK button to create it, I am getting "Project Cannot Be Created" error message and nothing else. I tried repairing my Professional Office 2003 installation and that didn't solve the problem. I also tried commenting different parts of the config file that I thought would help and that didn't help either.
Also, when I try opening a project containing an excel workbook that someone created, it gives me an error saying "Excel Designer Could Not Be Activated". I am experiencing this issue only for Excel projects. I can create ms word project without any problem.
Do you have any suggestion as to how I could get over this problem? I am using the professional version of VS2008.
Thanks in advance for your help!
Cool. It solved my problem and saved my times. thanks.
I don't have that file....
I think Web Service Factory (Model Edition) or one of its prerequisite installs broke mine..
Grrr... Thanks for your help!
I don't have that line. Can somebody help?
Saved me time, Thanks!
It worked...thanks
Thanks a LOT !!!!
hope you dont mind me reposting the same...
Thanks for the help. Linked to you on my blog:
http://www.framewreck.net/2008/02/completely-awesome-message-box_24.html
Btw, the new February 2008 GAX/GAT releases don't cause this issue.
Thanks.
Works for Visual Studio 2008 final release as well.
Thank you very much!!!
Great!!!!
-Rino
I don't have the file either. Did anyone come up with another solution?
I don't have that file either...
Thanks! Great. You saved me from reinstalling all developer tools.
Thanks a lot.
Awesome !!!
I have the file, but not that entry.
It really isn't that simple, and yes it is pretty lame to not be able to create projects/solutions when you first install a product.
Let me also point out that this only happened to me on Vista. I had no issues with XP.
I actually could not create a damn thing with VS2008 in Vista. I had to run a subinacl ( in admin mode ) to be able to create a VB project. This fixed all except C++.
More googling to do.
OH, I should have mentioned. I have MSDN versions of both.
Well, after many googles and then going to MSDN forums, I found the solution that worked for me. I thought i might be good to post a link here so that people realize that there is more than just one problem that causes this issue...and more than one solution.
Reference: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2895894&SiteID=1
It worked for me.
Thanks Peter.
Post a Comment
Links to this post:
Create a Link
<< Home