BizTalk Server Pipeline Component Wizard doesn't work in VS2013 with BizTalk Server 2013 R2


The wizard only works up through BizTalk Server 2010 in Visual Studio 2010. Updates are required with the release of BizTalk Server 2013 R2.

I have once again uploaded a patch here that implements these updates and gets it all working if you want a shortcut to getting it released.

NOTE: Patch was updated 27-FEB-2015, and fixes the following issues
  • Project creation of empty BizTalk projects result in errors due to mismatched VSPackage Guid
  • Removal of designer properties not implemented
  • Alignment of wizard elements causes some strings to be trimmed in the UI
  • Old image used for Wizard summary page
I've also attached the same patch to this issue.

file attachments


SATISH1986 wrote Nov 13, 2014 at 2:55 PM

Do I install the base wizard and the install the patch ?

I installed patch only and my BizTalk projects were corrupted.

kevinfoust wrote Feb 5, 2015 at 8:02 AM

I have successfully installed with this patch in late 2014, but when I did a new install yesterday I had the same issue as Satish1986. Something in BizTalk components was corrupted, and BT2013R2 had to be repaired.

nickh wrote Feb 26, 2015 at 11:02 PM

I reproduced this finally on a fresh install of everything, and I can see what the root cause is. I'll get that fixed and put up a new patch.

In the meantime, you can resolve the issue (and un-register the pipeline component wizard) by doing the following:
(1) Remove the entry for the Pipeline Component wizard from the file at: C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Developer Tools\BizTalkProjects\BTSProjects.vsdir

This file will be marked as read-only, so you will have to clear the flag before modifying. It should contain only the following lines:
 BTSMig.vsz|{7a51b143-7eea-450d-baef-827253c52e43}|#151|201|#152|{7a51b143-7eea-450d-baef-827253c52e43}|226| |#153
 BTSBpelImport.vsz|{7a51b143-7eea-450d-baef-827253c52e43}|#181|250|#182|{7a51b143-7eea-450d-baef-827253c52e43}|226| |#183
(2) Remove the .vsz file for the pipeline component wizard (in the same directory)

(3) Do a repair install of BizTalk Server (specifically the "Developer Tools" component)

wrote Feb 27, 2015 at 10:20 PM

wrote Feb 27, 2015 at 10:20 PM

nickh wrote Feb 27, 2015 at 10:44 PM

All fixed, please uninstall previous version, manually verify the BTSProjects.vsdir file to ensure it looks like above, repair install BizTalk Server, and then install new patch attached to this work item.

Sorry about that. I reached pretty far back for the original installer code and didn't account for the fact that the Guid changed for the VSPackage that is the BizTalk Developer tools (the Pipeline Component Wizard was using its resource assembly for the icon). As a result, when VS tried to load up the vsdir file listing the project templates, it couldn't properly load resources which in 2013 resulted in a nasty error message when creating any type of BizTalk project.

It worked on the machine on which I originally built the patch, not sure how or why, but I can confirm it didn't work for me this week on a fresh/new/clean machine (the BizTalk Server 2013 R2 Azure VM to be precise).

wrote Oct 9, 2015 at 6:44 PM

BizTalkers wrote Jun 10, 2016 at 3:25 PM

Great work Nick, thanks.

One minor problem I noticed, the wizard won't accept a numeric value in the namespace i.e. Unit4.PipelineComponents. As a work-around I entered UnitFour.PipelineComponents in the wizard then did a search and replace after code has been generated.

nickh wrote Feb 2 at 7:41 AM

I just saw the last comment here earlier this week. I went ahead and fixed that issue in a patch for BizTalk Server 2016. The problem was the regex being used for validation.