http://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspxToday, we explore some undocumented (and therefore not supported) internal parts of BizTalk 2004. When a BizTalk project is compiled, artifacts like Messages, Orchestrations, Pipelines, Maps or Schemas (to mention only a few) are compiled into a .NETen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspx#232330Tue, 21 Sep 2004 11:30:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:232330Carlo PoliOrchestrations and the related types (which are the port types, multi-part message types, correlation types and role link types) are compiled to Internal by default, but they all have a property &quot;Type Modifier&quot; that allows you to change the visibility. It allows you to reuse such a type across BizTalk-assemblies. <br> <br>Thank for the great summary.http://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspx#232333Tue, 21 Sep 2004 14:34:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:232333CaPo's Integration adventureshttp://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspx#232430Tue, 21 Sep 2004 18:57:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:232430Gilles' WebLoghttp://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspx#1612988Tue, 06 Feb 2007 21:20:33 GMT91d46819-8472-40ad-a661-2c78acb4018c:1612988Making Noise » Blog Archive » Format of Biztalk Assemblies<p>PingBack from <a rel="nofollow" target="_new" href="http://noise.youchill.com/?p=7">http://noise.youchill.com/?p=7</a></p> http://blogs.msdn.com/gzunino/archive/2004/09/20/232003.aspx#9364884Thu, 22 Jan 2009 11:34:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:9364884Best practices, xsi:schemaLocation : .NET and XML namespace synchr | keyongtech<p>PingBack from <a rel="nofollow" target="_new" href="http://www.keyongtech.com/323010-best-practices-xsi-schemalocation-net">http://www.keyongtech.com/323010-best-practices-xsi-schemalocation-net</a></p>