6 min read
BizTalk Server 2013: Step-by-Step to implement Unit Testing in Schemas and Maps
Sandro Pereira
Aug 28, 2014
If you want to automatically validate BizTalk schemas and verify map transformations during development or build processes, you can use the built-in
2 min read
Quick Tip: BizTalk Schema Identity
Sandro Pereira
Aug 17, 2011
In BizTalk Server development, understanding how the engine identifies a message is crucial Many developers mistakenly believe that the physical filename (eg,
2 min read
BizTalk WCF Service Wizard – Consume WCF Service to download metadata from a running servic...
Sandro Pereira
Oct 11, 2010
Windows Communication Foundation (WCF) provides a new TCP-based network protocol (nettcp://) for high-performance communication To import schemas that
2 min read
BizTalk Schemas – Unexpected XML declaration. The XML declaration must be the first node in...
Sandro Pereira
Oct 10, 2010
Today, I found an error on the MSDN forum that I encountered and suffered from in the past If you are working with BizTalk schemas or processing incoming XML
2 min read
Microsoft Hotfix BizTalk Server 2009 – Schema References broken
Sandro Pereira
May 11, 2010
Maintaining legacy BizTalk environments requires knowing exactly where the "landmines" are buried One of the most notorious issues in BizTalk Server 2009 is
3 min read
Introduction BizTalk Document Schemas – Part II
Sandro Pereira
Jul 4, 2009
If the Root Node is the "Name" of your message, the Namespace is its "Surname" In a global enterprise environment, you might have ten different "Invoice"
2 min read
How To import Add Reference from WSDL file
Sandro Pereira
Jun 16, 2009
In BizTalk Server, communicating with external systems via SOAP requires a clear "contract" This contract is the WSDL (Web Services Description Language) file
3 min read
Introduction BizTalk Document Schemas
Sandro Pereira
Jun 13, 2009
In BizTalk Server, everything revolves around the message Whether you are dealing with XML, Flat Files, or JSON (in newer versions), the Document Schema is
2 min read
There was a failure executing the receive pipeline: Microsoft.BizTalk.DefaultPipelines… failed to...
Sandro Pereira
Apr 24, 2009
Sometimes, when we try to test our Visual Studio BizTalk Server solution that we deploy in the BizTalk Server environment, we get the following error
