Agent v10.11+ fails to report data or create a log file

[tippmar-nr]

Description

When running a .NET Framework application that has a binding redirect for System.ValueTuple, referencing an old version of that assembly, the .NET agent v10.11 and later produces a profiler log file but does not create an agent log file and does not report data to New Relic.

Example:

      <dependentAssembly>
        <assemblyIdentity name="System.ValueTuple" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>

If the binding redirect for System.ValueTuple is removed from the .NET Framework application, the .NET agent starts and reports data as expected.

Expected Behavior

The .NET agent should start and report data without regard to any binding redirects in a customer application.

Steps to Reproduce

Create a .NET Framework console application targeting Framework v4.8 and add a binding redirect to the app.config file similar to the following:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.ValueTuple" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

Run the application and note that a NewRelic.Profiler.99999.log file is created in the New Relic home folder, but an Agent logfile is not created. Also note that the application fails to report data to New Relic.

Remove the binding redirect and run the application. Note that Profiler and Agent log files are created and the application reports data to New Relic

For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
P1
Suggested T-Shirt size (S, M, L, XL, Unknown):
M

[workato-integration]

https://new-relic.atlassian.net/browse/NR-181163