(Web)Service Installations, in Visual Studio, Under Windows 10

Recently, came across a strange quirk, when trying to install a WCF service, from within Visual Studio, in Windows 10:

Quite bizarre since the IIS version of Windows 10 seems to be higher than 5.1.

Not in this world though.  It seems that the condition to check the IIS version uses a string compare, where “#10” is lower than “#5”.

To solve this, change the IIS Condition property.

Update the Condition property to:

(IISMAJORVERSION >= “#5” AND IISMINORVERSION >= “#1”)  OR IISMAJORVERSION >= “#6” OR IISMAJORVERSION >= “#10”

Solved, you can now successfully install your project.

Reblog: Save BizTalk suspended messages body/payload to file, using Powershell and BizTalk API

http://www.integrationadmin.com/2016/10/biztalk-suspended-messages-bodypayload.html

Problem: BizTalk Pipeline shows up as XML in Visual Studio by default.

Sometimes, when opening a .btp file (a pipeline), in Visual Studio, the designer doesn’t show up, but instead, it’s the XML representation.

You can open it, explicitly, using Open With, and selecting the BizTalk Pipeline Editor, but since it only happens with some pipeline, and not with others, there should be an easier solution.  And there is.

Reblog: Final Version of BizTalk Terminator Tool Released

The Microsoft BizTalk Team blog announces a new, and the final version for the BizTalk Terminator Tool.

This doesn’t mean the functionality is going away, however.  It is already integrated in their existing BizTalk Health Monitor (BHM) tool, in the maintenance node.

Microsoft BizTalk Developer blog

How to identify the PID of a business process

When debugging a custom BizTalk component such as a Custom Pipeline Component, sometimes, you want to attach your Visual Studio to the BizTalk Host Instance service.

However, when running multiple Host Instances, you will have multiple instances of BTSNTSvc.exe and BTSNTSvc64.exe, without being able to identify them (from Visual Studio).
These serivces have an individual Process Identification Number (PID) that is unique for each Host Instance, and will change when restarting a host.

There is a way from the command prompt to identify using these.

Custom Extension XML in a BizTalk Map Caches Assemblies in Visual Studio

This is a “gotcha”, that I wasted a few hours on, so I thought to mention this on the internet.  When adding a method to a helper class, that was called in custom XSLT, I kept on getting the message that the method wasn’t available.  Even when removing the assembly from the GAC…

This case happens when using a BizTalk map with a Custom Extension XML.  I used the extension XML, to be able to call a method in a helper class, in a custom XSLT.