Yesterday I spoke about how you can apply custom pattern restrictions to properly validate DateTime, Date, and Time formats inside elements or attributes You
Today I was involved in a BizTalk Schema importation that includes not-so-used restrictions on Date and Time elements formats And that gave me the idea and
I have been working on a new BizTalk Server project on a new client for a few weeks Now that we are beginning the development phase, I was getting annoying
I'm just playing with BizTalk Server doing a small proof-of-concept using BizTalk Server and Azure Service Bus, and I was surprised with a few bunches of
Sometimes we want to bypass the adapters and perform the communication thru NET code Sometimes we want to access multiple values, or recursive values, of a
Visual Studio BizTalk Schema Generator Wizard error: Error occurred while creating the BizTalk po...
After several days migrating BizTalk open-source contributions like BizTalk Mapper Extensions UtilityPack, BizTalk Pipeline Components Extensions Utility
BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON th...
This week while trying to use the BizTalk Server 2016 JSON Schema Wizard to generate an XML schema from a specific JSON file to be sent to a Logic App I got
In the last months, I have been working with ORACLE adapter, mainly doing direct insert operations on ORACLE tables and as you might imagine, I found some
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#