Assembly warnings on compile

Using a clean D365F&SCM development environment. Creating a single model for future development work and compiling the system for the new model. There is no customisation in the system; it is clean. The following warnings are presented when the compilation for the new model was completed.

Warning 1

Assembly ‘Microsoft.Xbox.Experimentation.Contracts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d91bba2b903dc20f’ failed to load because it was not found. 

C:\AOSService\PackagesLocalDirectory\ApplicationCommon\ApplicationCommon\AxReference\Microsoft.Commerce.Flighting.Common.xml

Warning 2

Assembly ‘System.Memory.Data, Version=1.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ failed to load because it was not found. 

C:\AOSService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxReference\Azure.Core.xml

Warning 3

Assembly ‘Microsoft.Dynamics.Commerce.Runtime.Entities.AttributeBasedPricing, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ failed to load because it was not found. 

C:\AOSService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxReference\Microsoft.Dynamics___vices.PricingEngine.xml

Result

Warning messages on a clean system can be ignored. We should receive no warnings or errors. Can we remove these warnings?

We must add an entry to the best practice suppressions file to remove the warnings. The file is in the following location: C:\AOSService\PackagesLocalDirectory\<model>\<model>\AxIgnoreDiagnosticList. Depending on where your AOSService directory is, you might need to change the drive. It might be on the K drive, depending on the configuration.

The file name is <model>_BPSuppresions.xml. For a new model this file will not exist, and will need to be created. Once created, you can create the suppression entries to prevent the warnings from occurring. For the examples provided, the xml would look like:

<?xml version="1.0" encoding="utf-8"?>
<IgnoreDiagnostics>
  <Name>YourModel_BPSuppressions</Name>
  <Items>
    <Diagnostic>
      <DiagnosticType>ExternalReference</DiagnosticType>
      <Severity>Warning</Severity>
      <Path>dynamics://Reference/Microsoft.Commerce.Flighting.Common</Path>
      <Moniker>AssemblyFileNotFound</Moniker>
      <Justification>Legacy issue</Justification>
    </Diagnostic>
    <Diagnostic>
      <DiagnosticType>ExternalReference</DiagnosticType>
      <Severity>Warning</Severity>
      <Path>dynamics://Reference/Azure.Core</Path>
      <Moniker>AssemblyFileNotFound</Moniker>
      <Justification>Legacy issue</Justification>
    </Diagnostic>
    <Diagnostic>
      <DiagnosticType>ExternalReference</DiagnosticType>
      <Severity>Warning</Severity>
      <Path>dynamics://Reference/Microsoft.Dynamics___vices.PricingEngine</Path>
      <Moniker>AssemblyFileNotFound</Moniker>
      <Justification>Legacy issue</Justification>
    </Diagnostic>
  </Items>
</IgnoreDiagnostics>

You will see three diagnostics blocks, one for each of the suppressions required to clear each warning.

Note: you will need to create the file for each model you create