Uncategorized

Share this

BizTalk Project Template is missing in Visual Studio 2012

Gautam

I ran couple of times into this issue so thought of documenting it here. So first of all development of BizTalk Server 2013 application is only supported on Visual Studio 2012. In short, to get BizTalk Project Template do the following steps:
  1. Install Visual Studio 2012
  2. Install SQLServer2012 or SQLServer2008R2 SP1
  3. Install BizTalk Server 2013  - Select (mark all check box) all the features while installing BizTalk Server 2013
  4. Configure BizTalk Server 2013
As per the BizTalk product documentation http://msdn.microsoft.com/en-us/library/jj248697(v=bts.80).aspx BizTalk Server Developer Tools and the SDK component need to be installed for development environment for building BizTalk Server applications. If you have missed to install those component during you BizTalk installation there are chances you run into the issue of "BizTalk Project Template is missing in Visual Studio 2012". Selecting the Developer Tools and SDK component installs samples and utilities that enable the rapid creation of Microsoft BizTalk Server solutions. This includes: SDK samples and supporting documentation, BizTalk Explorer, schema and map designers, and Visual Studio 2012 project templates. This component requires Visual Studio 2012. This feature requires the following missing platform components to be installed: WCF HTTP ACTIVATION 4.5,IIS ASPNET 4.5 So its better to Install Visual Studio 2012 firstto get ASPNET 4.5 and WCF HTTP requirements met before installing BizTalk Server.   Related Links: https://social.msdn.microsoft.com/Forums/en-US/4f7f73fe-f22d-4976-ab18-adeec6dfccdf/biztalk-project-templates-installation?forum=biztalkgeneral https://connectedpawns.wordpress.com/2014/10/10/biztalk-2013-solution-template/  
 Previous
Next

Loved this? Spread the word

Gautam

Follow me here

About the Author

My name is Gyanendra Kumar Gautam. I am Solution Consultant, who basically works to hook the stuff together using Microsoft technologies like Azure PaaS, Azure Serverless Services, Microsoft BizTalk Server, and Azure DevOps Services.

 Learn more 

You may also like

The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: Security.

Yesterday this error came for one of the deployment on production. But the same deployment was working fine on staging environment. A message received by adapter “MSMQ” on receive location “RL_XYZ_RES_09” with URI “FORMATNAME:DIRECT=OS:.\PRIVATE$\XYZ_RES_09” is suspended. Error details: There was a failure executing the receive pipeline: “BTSHttpDecoder.DecoderPipeline, BTSHttpDecoder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5793a821957af7d1” Source: “MessageDecoderPipelineComponent_F09” Receive Port:

Read More

BizTalk Project Template is missing in Visual Studio 2012

I ran couple of times into this issue so thought of documenting it here. So first of all development of BizTalk Server 2013 application is only supported on Visual Studio 2012. In short, to get BizTalk Project Template do the following steps: Install Visual Studio 2012 Install SQLServer2012 or SQLServer2008R2 SP1 Install BizTalk Server 2013  – Select (mark

Read More

There is no value associated with the property ‘BTS.MessageID’ in the message.

In the following orchestration (This is the HelloWorld sample application at C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Samples\Orchestrations\HelloWorld\)     Inside the message assignment shape I have added the following code. System.Diagnostics.EventLog.WriteEntry(“HelloWorld”,InvoiceMessage(BTS.MessageID)); Now when I deploy and test the HelloWorld application, I get the following error xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below)

Read More
Leave a Comment

Never miss a good story!

 Subscribe to my blog to keep up with the latest news!