I’m glad to be back, once again, to Integration Monday Events! The first time I presented a session on this user group was almost 3 years ago on April 25,
BizTalk Custom Functoid: Extension function parameters or return values which have Clr type Char ...
Back to Errors and Warnings, Causes and solutions, this time with a surprising error that I got while I was testing a custom Functoid that I had developer:
I finally started and published the first version of the sibling BizTalk project Mapper Extensions UtilityPack for BizTalk Server 2016: BizTalk Pipeline
Visual Studio error: Unable to find transmitPipeline.vstemplate. Please repair the product to fix...
My blog backlog is full of precious things and I stop counting the number of pages I have on my OneNote to be published Today I randomly selected this Unable
In the last post, we try to demystify the reason and cause of the error: Invalid type name The root node type has to be a valid C# identifier when you are
A few days ago, while trying to compile a BizTalk Server solution I got the following error: Invalid type name The root node type has to be a valid C#
There are errors that we are familiar with, but I guess this you may never hear about it I didn't know it until today: Failed to create window handle for pane
I’m back with “Errors and Warnings, Causes and Solutions” and this time targeting developers - BizTalk Deploy operation failed - that work until late and
BizTalk Pipeline does not open with BizTalk Pipeline Editor! Instead it opens with the XML (Text)...
In the sequence of one of my last blog posts, I notice that in the same project also while trying to open a BizTalk pipeline inside Visual Studio, again,
BizTalk Orchestration does not open with BizTalk Orchestration Designer! Instead it opens with th...
While trying to open a BizTalk Orchestration inside Visual Studio, normally a simple and easy double-click operation to open the BizTalk Orchestration