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

By Sandro Pereira

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#

By Sandro Pereira

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

By Sandro Pereira

Jul 25

The file ‘…’ cannot be copied to the run directory. The process cannot access the fil...

I've been working on a BizTalk Server 2004 project that had (not anymore) between 6 or 8 visual studio solutions each one with a BizTalk Project inside After

By Sandro Pereira

Jul 15

Cannot generate serialization assembly {AssemblyName}.XmlSerializers.dll because it already exist...

For some reason after having migrated a BizTalk 2006/Visual Studio 2005 solution to BizTalk 2010/VS 2010 using Visual Studio Conversion Wizard, I got the

By Sandro Pereira

Apr 29

Multi-Part message – “use of unconstructed message ” – Error message when...

Sometimes when we try to build or deploy BizTalk solution, you may get the following error message: “Use of Unconstructed Message 'MessageName'” I

By Sandro Pereira
BizTalk360
BizTalk Server

Over 500+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Manage and monitor serverless
components effortlessly

Learn More
Atomicscope
Business Users

Monitor your Business Activity in iPaaS
or Hybrid integration solutions

Learn More

Back to Top