BizTalk Custom Configuration

IN BTSNTSvc.exe.config requires TWO changes to the standard file to make custom configuration files accessible:

<?xml version=1.0>
<configuration>
 <configSections>
  <section
  name=xlangs
  type=Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurationSectionHandler, Microsoft.XLANGs.BizTalk.CrossProcess />
 </configSections>

    <runtime>
        <assemblyBinding xmlns=urn:schemas-microsoft-com:asm.v1>
            <probing privatePath=BizTalk Assemblies;Developer Tools;Tracking;Tracking\interop />
        </assemblyBinding>
    </runtime>
   
    <system.runtime.remoting>
   
        <channelSinkProviders>
            <serverProviders>
                <provider id=sspi type=Microsoft.BizTalk.XLANGs.BTXEngine.SecurityServerChannelSinkProvider,Microsoft.XLANGs.BizTalk.Engine securityPackage=ntlm authenticationLevel=packetPrivacy />
            </serverProviders>
        </channelSinkProviders>
   
        <application>
            <channels>
                <channel ref=tcp port=0 name=>
                 <serverProviders>
                     <provider ref=sspi />
                        <formatter ref=binary typeFilterLevel=Full/>
                    </serverProviders>
                </channel>
            </channels>
        </application>
    </system.runtime.remoting>
    <xlangs>
  <Configuration>
   <AppDomains AssembliesPerDomain=10>
    <DefaultSpec SecondsIdleBeforeShutdown=5 SecondsEmptyBeforeShutdown=5>
    </DefaultSpec>
    <AppDomainSpecs>
        <AppDomainSpec Name=MyAppDomain>
            <BaseSetup>
                <ConfigurationFile>C:\Projects\Projects\AppDomainConfig\MyAppDomainConfiguration.config</ConfigurationFile>
            </BaseSetup>
        </AppDomainSpec>
    </AppDomainSpecs>
    <PatternAssignmentRules>
     <PatternAssignmentRule AssemblyNamePattern=AppDomainConfig.* AppDomainName=MyAppDomain />
    </PatternAssignmentRules>
   </AppDomains>
  </Configuration>
     </xlangs>

Thanks to BizTalk 2004 Guerilla Training course - App Domains [MSDN]

NOTE: Custom pipelines, probably due to the fact they are not in orchestration, do not comply with this configuration pattern