While working on the current upcoming installment in my BizTalk Server 2013 R2 New Features Series, I realized that I did not yet have a version of Martijn Hoogendoorn’s excellent BizTalk Server Pipeline Component Wizard that would work happily in Visual Studio 2013.
As a result, I filed this issue, and then made the necessary modifications to make it work in Visual Studio 2013 with BizTalk Server 2013 R2. It is now available for download here (updated 27-FEB-2015) if you want to give it a test run.
Unfortunately, that has consumed a significant portion of my evening, and thus the next installment in the blog series will be delayed. But fear not, there is some really cool stuff just around the corner.
Integrate 2014 Registration is Live
In other news, Integrate 2014 registration is now live, and is only 72 days away! It’s going to be an awesome start to a cool Redmond December as 300-400 BizTalk enthusiasts from around the globe converge on the Microsoft campus for a few days of announcements, learning, networking, and community.
I’m not going to lie, I’m pretty excited for this one! Especially seeing these session titles for the first day:
- Understand the New Adapter Framework in BizTalk Services
- Introducing the New Workflow Designer in BizTalk Services
Well, that’s all for now. I hope to see you there!
While the installation works and you can create a custom pipeline component., the installer screws up the biztalk templates for vs 2013. You can no longer open biztalk projects or create new empty ones.
You’re right. I was able to reproduce this, and there is now a fix.
Please uninstall the previous version, ensure your BTSProjects.vsdir file contains only the lines mentioned in my previous comment, and then re-install the Developer Tools component of BizTalk Server to clean everything up.
From there, you can install the new version of the patch attached here:
The only thing that could even potentially lead to that is a modification it makes to register itself in a file that lives at:
C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Developer Tools\BizTalkProjects\BTSProjects.vsdir
If, in the process of registering itself, that file becomes mangled, that would be bad. Though I’ve not seen that in any tests myself.
If you want to try to fix it, you can replace the contents of that file with the following (original content) — but make a backup of the file first:
There should be 2 lines of actual data in the completed file (though this will un-register the pipeline component wizard). If that works, and you want to bring the wizard back, re-add the line in your backed up copy of the file.
Essentially you can see everything it’s doing in the InstallUtil console application source that is part of the patch. And it’s not doing much, so if that doesn’t fix it, then there might be something else off in your environment, and you might consider re-installing the Developer Tools portion of the BizTalk installation.
EDIT – 26-FEB-2015:
I’ve reproduced this 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:
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:
Does it work with BT2016?
After I run the .vsix. what exactly do I do in Visual Studio to start it?
I don’t see anything under Toosl menu.
Okay, I see now it’s File New Project, C#…