This project has moved and is read-only. For the latest updates, please go here.

Questions about section name=xlangs type=Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurationSectionHandler

Topics: General Questions
Feb 18, 2011 at 10:42 AM


When I use BTDF for deploying my biztalk application, the following is added in BTSNTSvc.exe.config.

<section name="xlangs" type="Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurationSectionHandler, Microsoft.XLANGs.BizTalk.CrossProcess" />


    <Configuration xmlns:xsi="" xmlns:xsd="">
      <Debugging StartupInDebugger="false" ValidateAssemblies="false" ValidateSchemas="false" ValidateCorrelations="false" DumpStreamOnError="false" EagerGC="false" ExtendedLogging="false" DumpParts="false" DumpStates="false" RetailAsserts="false" SupressKeepAlive="false" TestExtensions="false" />
      <Dehydration AlwaysDehydrate="false" NeverDehydrate="false" MinThreshold="1" MaxThreshold="1800" ConstantThreshold="-1">
        <PhysicalMemoryThrottlingCriteria OptimalUsage="90" MaximalUsage="95" IsActive="false" />
        <VirtualMemoryThrottlingCriteria OptimalUsage="900" MaximalUsage="1300" IsActive="true" />
        <PrivateMemoryThrottlingCriteria OptimalUsage="50" MaximalUsage="350" IsActive="true" />
      <AppDomains AssembliesPerDomain="10" WeakXsdPartValidation="false" SuspendUponIncompleteResponse="Off">
        <DefaultSpec SecondsIdleBeforeShutdown="1800" SecondsEmptyBeforeShutdown="1200">
        <AppDomainSpecs />
        <ExactAssignmentRules />
        <PatternAssignmentRules />
      <Throttling PauseAt="0" ResumeAt="0" />

A few questions:

  • Why is this section added to the config?
  • Are these settings the default settings that biztalk uses for all applications?
  • Is there a way to prevent adding this section to the config?

Thanks in advance,


Feb 18, 2011 at 6:17 PM

This is where 1) the Debugging settings are housed (ExtendedLogging, ValidateSchemas, etc.) and 2) assignments of assemblies into specific AppDomains are specified.  The XML block is written out by BizTalk's own configuration API, so those settings and values are all assigned by BizTalk code.

There is currently no way to prevent this from being written out.  There are a number of MSBuild properties that override some of the XML values, like EnableBizTalkAssemblyValidation, EnableBizTalkExtendedLogging and UseIsolatedAppDomain.

We could change the XML update to directly write to the XML files instead of using the BizTalk API, which would result in the <Debugging> element and possibly <AppDomains> being written out depending on the properties set in your .btdfproj.