Oct 6
BizTalk Server Schema Editor getting blocked by Internet Explorer Enhanced Security Configuration
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
Jul 27
Demystify Invalid type name error on BizTalk Schemas (Part II)
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
Jul 26
Demystify Invalid type name error on BizTalk Schemas (Part I)
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#
Jul 3
BizTalk Schema Problems: The type or namespace name ‘SerializableAttributeAttribute’ ...
An error never comes alone When an error appears, it always appears two or three, and I still have thousands to published, but this one made me crazy for a
Sep 10
Schema item missing from Visual Studio BizTalk Project items
This week I encountered a curious situation while I was developing a new BizTalk solution After creating my new project, I tried to add a new schema to the
Jul 10
Error when trying to validate EDI message against the schema: [29] Invalid count specified at the...
As I mentioned in my last post, when we are in the development phase of a BizTalk project is normal to validate test instances of messages that are provided
Jul 9
Error when trying to validate EDI message against the schema: [71] Transaction Set or Group Contr...
When we are in the development phase of a BizTalk project is normal to validate test instances of messages that are provided with respective schemas before we
Jul 20
BizTalk Schema validation – Default and Deep Validation
By default, BizTalk Server will examine only the namespace and the root node name of a message to identify and validate the schema, and will not detect extra
