Project Conversion Woes: A project with that name is already opened in the solution

Tonight I decided to play with the project conversion (C# to VB.NET) capabilities of the wonderful #develop. For the uninitiated, #develop is an open source .NET IDE which is surprisingly robust, feature rich and lightweight. It has many cool features, one of which is the ability to convert entire projects (not solutions though) between languages. I really can’t recommend this app enough – it can be found at the following link.

I set my project up to convert and it ran smoothly. There were a few error messages (could not convert C# yield statement to VB.NET, anonymous method issues etc.) but pretty straightforward stuff and  the conversion ran extremely quickly. I attempted to add the newly created/converted vb.net project to a newly created VB.NET solution in Visual Studio, only to run into the following message:

A project with that name is already opened in the solution

It took some research but everything I read pointed to the ProjectTypeGuids in the vbproj file. Mine looked as follows:

<ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>

Googling the possible ProjectTypeGuids I came across the following comprehensive list:

http://www.mztools.com/Articles/2008/MZ2008017.aspx

The first GUID (there are two – delimited by a semi-colon) was correct. {60dc8134-eba5-43b8-bcc9-bb4bc16c2548} corresponds to Windows Presentation Foundation (WPF) and the project I converted was a WPF C# application. However, the second GUID was incorrect – apparently a failure of the conversion process.

{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} corresponds to Windows (C#) and my app was no longer a C# app. Replacing this with its VB.NET equivalent - {F184B08F-C81C-45F6-A57F-5ABD9991F28F} – the line in the project file became:

<ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>

I reloaded the project in Visual Studio and lo-and-behold it worked! Another fine lesson learned!

Comments

Jason said…
Thank you very much! I appreciate the feedback.
April 11, 2009 at 9:42 AM
Anonymous said…
This comment has been removed by a blog administrator.
July 10, 2009 at 4:40 AM
Anonymous said…
This comment has been removed by a blog administrator.
November 2, 2009 at 8:52 AM
Anonymous said…
Interesting story you got here. It would be great to read a bit more about this matter. Thanx for posting this information.
February 11, 2010 at 10:26 AM
Post a Comment

Popular posts from this blog

Excel - Adding an existing Pivot table to the data model

Image
  I've been working more with, and continue to be amazed by, Power Pivot. I recently ran into an issue where I needed to add the data for an existing Power Pivot report to the Data Model. There is a checkbox that makes this easy when creating a PivotTable: As so often happens, the analysis grew in scope/importance and I found myself needing to add the data to the data model. While it's not obvious how, there is a way to add an existing Pivot table to the data model. There's a More Tables... link in the PivotTable Fields pane.  Clicking on the  More Tables... results in a dialog confirming that you want to Create a New PivotTable .  Doing so will result in the creation of the new PivotTable in a new sheet. By default the data is added to the data model. You'll likely lose some formatting but for anything other than a trivial PivotTable, this should save effort, as it did for me.
Read more

Mirth

Image
Introduction Let's talk about Mirth. At it's simplest, Mirth  link is an Open Source HL7 interface engine. HL7 (Health Level 7) is an NPO involved in the development of healthcare standards and the HL7 v2.x and HL7 v3 standards are commonly used in Medical Information for data interchange - including but not limited to clinical, financial, logistical and administrative messaging. I first ran across Mirth over a year ago on a personal quest to find an alternative to our client's legacy HL7 application. Academically, I wrote a number of lexical analysis tools using lexx, yacc, bison and JavaCC and knew the challenges of writing and maintaining complex parsers. I was simply looking for something that could parse HL7 for us, and perhaps log messages and provide a little more transparency than our application currently allowed.  A year later and our legacy application is still going strong (read: my proposal was declined), but Mirth is being used in production, far away from th
Read more

Getting Started with Mirth (Part 1)

Image
This is the first post in a 2 part series. The second post is here Recently I posted about my positive experience when using Mirth by Webreach as an open source communication layer between one of our in-house applications and a third party and proprietary web service interface. That post received a large amount of attention (relative to my other posts :o) ) so now I will post a quickstart guide to creating a similar setup. In this post I will go over the very basics of using Mirth (please dig in and play around with some more advanced options/configurations), specifically I will demonstrate how to use Mirth to read data from a database, package the data up in a SOAP envelope, send the data to a web service and process the SOAP response. I'll also show you how easy it is to monitor channels once deployed. Once you've installed and opened Mirth for the first time you'll be presented with an empty dashboard - but it wont stay empty for long. This is where you'll s
Read more