title: Biztalk map error only when building in Azure DevOps
body: <p>I have a bigger visual studio solution containing ~30 edifact xml schemas together with maps to a self made schema. Building the solution inside visual studio or via msbuild on the command line succeeds. Using a devops build pipeline, 5 maps give me an error:</p>
  <blockquote>
  <p><code>##[error]...\EFACT_D18A_IFTSTA_2_0c-InternalFormat.btm(0,0): Error btm1023: Exception Caught: The map contains a reference to a schema node that is not valid.  Perhaps the schema has changed.  Try reloading the map in the BizTalk Mapper.  The XSD XPath of the node is: /*[local-name()='&lt;Schema&gt;']/*[local-name()='EFACT_D18A_IFTSTA_2.0c']/*[local-name()='CNILoop1']/*[local-name()='STSLoop2']/*[local-name()='NADLoop2']/*[local-name()='CTALoop2']/*[local-name()='CTA']/*[local-name()='CTA01']</code></p>
  </blockquote>
  <p>I cannot reproduce the error locally. The same project is in production with this maps on biztalk 2016.</p>
  <h2>Software Versions</h2>
  <ul>
  <li>MSBuild version 16.11.1+3e40a09f8 (identical)</li>
  <li>Microsoft.VisualStudio.BizTalkProject.BuildTasks, Version=3.0.1.0 (identical)</li>
  <li>Visual Studio 2019</li>
  <li>Biztalk 2020</li>
  <li>Pipeline agent details <a href="https://github.com/actions/virtual-environments/blob/win19/20211018.0/images/win/Windows2019-Readme.md" rel="nofollow noreferrer">https://github.com/actions/virtual-environments/blob/win19/20211018.0/images/win/Windows2019-Readme.md</a></li>
  </ul>
  <h2>Tried and failed steps</h2>
  <p>If I remove the 5 offending maps, the build succeeds. There are other working maps of similiar shape and content and I cannot find any relevant difference causing this error.</p>
  <p>If I create an absolutely new map with same source and target schema, it yields the same error.</p>
  <p>The maps contain only lines and fixed values. No functoids, nothing special.</p>
  <p>I can remove the line stated in the error and can recreate it only to get stated another error.</p>
  <p>Increased verbosity of msbuild, but it did not reveal any more insights.</p>