Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Visual Studio 2008 SP1 and upgrading a BizTalk 2006 R2 project – Failing
- This topic has 1 reply, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
July 8, 2009 at 8:47 AM #22816
Greetings all,
I posted this on the on the MSDN Vs.Net general managed group, but think I will probably get more traction with it here.
Here is the message I posted there:
I am in the process of upgrading our BizTalk projects from BizTalk 2006 R2
to BizTalk 2009.I start VS 2008, load up the solution with all our VS 2005 artifacts in it
project, and the Visual Studio Conversion Wizard starts. All good to here.The wizard properly reports that the projects which will be updated. These
look good.I press Finish and the conversion tool goes and does its conversion thing.
The wizard reports that all projects have been converted successfully,
However when I view the conversion log, it says that none of the BizTalk
projects were converted. If I expand the node on of the non-converted
projects, there is no error information as to why it didn’t convert.The two biztalk projects in the solution (the others are c# projects) are
both grey and VS.Net 2008 says they are unavailable.If I then right click on the project and select “Reload” the conversion
wizard comes up again, this time it asks to create a backup before
converting. I select yes to the default location and hit Next. It tells me
it’s ready to convert, when I hit Finish I get the nice little dialog window:The operation could not be completed. Unspecified error.
If I look at the conversion log this time, I see the error:
Conversion Issues – your.project\your.project.btproj:
Error converting project file. Child element <BIZTALK> of element
<VisualStudioProject> is not valid.There are a couple of posts on the net about this issue but no concrete
resolutions:http://msdn.microsoft.com/en-us/library/dd257156.aspx
The msdn article mentions not having a solution which makes no sense as the
thing is listed in the solution explorer (abite not being loaded).Anyone have some ideas/thoughts on this?
Thanks.
-
July 16, 2009 at 6:35 AM #22865
Hi,
I experienced the same problem. When upgrading a solution of almost 60 BizTalk 2004 projects to BizTalk 2009, one single project failed with the Child element <BIZTALK> of element <VisualStudioProject> is not valid error. Comparing the problem project with the others did not show any difference of interest.
However, when I retried the conversion progress on a fresh copy of the 2004 solution, it finished without errors.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.