17
Vote

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

description

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

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

comments

Abhi004 wrote Nov 26, 2013 at 6:03 PM

Hi,
Urgently need a update as I am unable to work wizard with VS 2012

Thanks
Abhishek

wrote Dec 23, 2013 at 3:35 PM

wrote Feb 26, 2014 at 7:31 PM

bat2001 wrote Feb 26, 2014 at 7:31 PM

VS 2012 support, please

wrote Mar 19, 2014 at 1:53 PM

wrote Mar 19, 2014 at 6:34 PM

wrote Mar 22, 2014 at 8:16 AM

wrote Apr 4, 2014 at 7:42 PM

wrote May 13, 2014 at 1:49 PM

wrote Jun 24, 2014 at 11:29 AM

wrote Sep 22, 2014 at 7:07 AM

rituraj wrote Sep 22, 2014 at 7:07 AM

VS 2012 support, please

nickh wrote Sep 22, 2014 at 2:39 PM

There's a patch here for VS2012 support. Requires InstallShield for the installer project. Otherwise, just look at the code for the custom action and you can see the install steps (they're pretty straight forward).

wrote Oct 29, 2014 at 2:10 PM

SATISH1986 wrote Dec 8, 2014 at 9:06 PM

I installed the patch and visual studio no longer recognizes BizTalk templates. Let me know if there is a patch for BTS 2013 R2 with VS 2013.

Sreenivasu wrote Feb 7, 2015 at 7:28 PM

After downloading above patch, if you don't have install wizard, then you can do below.
  1. Create a console based application
  2. Add below code
            CustomActions action = new CustomActions();
        IDictionary dictionary = new Hashtable();
        action.Install(dictionary);
    3) Add CustomAction project as reference (Is part of the release)
    4) Open CustomAction source code and do below change to private bool RegisterPipelineComponentWizard(bool unregister)
Replace
//regAsmArguments = string.Format("\"{0}\"", Path.Combine(base.Context.Parameters["ApplicationPath"], "PipelineComponentWizard.dll"));

with
            regAsmArguments = string.Format("\"{0}\"", Path.Combine(@"D:\PipelineWizard\PipelineComponentWizard\bin\Debug", "PipelineComponentWizard.dll"));
Note: Change "D:\PipelineWizard\PipelineComponentWizard\bin\Debug" to your location.

Sreenivasu wrote Feb 7, 2015 at 7:29 PM

Then run the console application. It registers the component to VS.
Open Vs and you can see new Visual studio project "Pipeline component Wizard" under BizTalk projects.

nickh wrote Feb 27, 2015 at 10:27 PM

SATISH1986 - Yes, the registration of the wizard in the .vsdir file used an old Guid for the VSPackage. This has been updated to use the new Guid in the last version of the patch.

To resolve the issue, you can uninstall the Pipeline Component Wizard, remove the line for it in the .vsdir file and then re-install the Developer Tools component of BizTalk Server.

I have posted a new version of the patch which resolves the issue, and cleans up the install/uninstall.

nickh wrote Feb 27, 2015 at 10:28 PM

New (VS 2013 + BizTalk Server 2013 R2) version of the patch is here.