NET Release Notes

Recent .NET agent release notes are listed below. If you would like a release that has been used extensively with a list of known issues, see Established releases (.NET) for download and version information.

Monday, March 18, 2019 - 16:30

Download URLs

Download the appropriate release for your New Relic .NET agent:

https://download.newrelic.com/dot_net_agent/latest_release

Fixes

  • Fixed issue where transactions may not get reported when custom instrumentation is applied to async methods with a void return type. Instrumenting async void methods is generally not recommended and may result in unexpected segment timing as well as the disruption of downstream instrumentation. Please review async limitations online help for alternative approaches.

New Features

  • [.NET Core] Adds support for .NET Core 3.0 preview 2
  • [.NET Core] Adds support for ASP.NET Core 3.0 preview 2
  • [.NET Framework] Adds support for .NET Framework 4.8 Early Access build 3694
  • Adds official support for Postgres/Npgsql versions 4.0.
    • Supports Sync and Async methods, on .Net Framework and .Net Core running in Windows and Linux.
    • Eliminates duplicate and extraneous datastore metrics and trace segments associated with opening connections to databases (as seen in prior agent versions).
    • Npgsql versions older than 4.0 may also be instrumented, but duplicate and/or missing metrics are possible.
  • Adds improved WCF support
    • WCF client calls are tracked as external calls
    • WCF client synchronous and asynchronous programming model (following the begin/end asynchronous pattern) calls are tracked.

Upgrading

Tuesday, February 12, 2019 - 14:00

Fixes

  • [Framework] Improved support for async workloads in self-hosted OWIN applications.
  • [Framework] Status code only errors are now noticed in self-hosted OWIN applications.

New Features

  • [Framework] Adds support for the following in .Net Framework self-hosted OWIN apps:
    • Microsoft OWIN version 4
    • Distributed tracing
    • Cross application tracing
    • Request parameters capture
    • Request URI capture
    • Introduces single metric creation for HTTP status codes 400 and greater
    • Exception capture from OWIN middleware components

Upgrading

Wednesday, January 9, 2019 - 14:00

Fixes

  • Fixed an issue where the response time of a web transaction could be misreported when making asynchronous external calls whose duration extended beyond the time the web transaction response ended.
  • Fixed an issue when using OpenRasta instrumentation where the full URL could be captured on instrumented requests. This may have resulted in query strings being collected which can contain sensitive information. See security bulletin NR19-01.
  • Fixes an issue with auto-instrumenting RestSharp and Couchbase driver calls involving non-public collection types.

Upgrading

Monday, December 17, 2018 - 14:30

Fixes

  • Fixes an issue where stack traces for custom errors outside a transaction were not visible in the Error Analytics UI page.
  • Fixes an issue with auto-instrumenting MongoDB driver calls involving non-public collection types.
  • Fixes an issue with reporting the same transaction multiple times.

New Features

  • Improved performance when serializing metrics prior to sending to New Relic.
  • Improved SQL-related database instrumentation performance.

Upgrading

Thursday, November 29, 2018 - 16:00

Fixes

  • Fixes a bug in SQL-related database instrumentation that potentially causes a CPU spike. This bug appeared in the agent version 8.9.130.

New Features

  • [.NET Core] Adds support for .NET Core 2.2.
  • Adds support for ASP.NET Core 2.2.
  • Improves the performance of cross application tracing.

Upgrading

Thursday, November 15, 2018 - 10:00

Fixes

Added auto instrumentation to prevent associating Serilog PeriodicBatchingSink activity with an application’s transactions.

New Features

Added API support for manually creating and accepting distributed tracing payloads.

Upgrading

Thursday, October 18, 2018 - 13:30

Fixes

  • Fixes potential memory leak when Distributed Tracing is enabled.
  • Fixes an issue where a NullReferenceException is logged for certain data stores (MongoDB and Couchbase) when distributed tracing is enabled.
  • Fixes an issue where a transaction start time is incorrect when an error has been reported.

Other Information

  • After November 7th, 2018 the Core_20 directory will be removed from the download site. This folder currently contains an outdated version of the .Net Core agent. The most up-to-date version of the .NET Core agent can be found in inlatest_release directory.

Upgrading

Wednesday, October 3, 2018 - 13:30

New Features

Fixes

  • The profiler now honors the log level configuration setting that is set in the app-local newrelic.config file.

Other Information

  • After November 7th, 2018 the Core_20 directory will be removed from the download site. This folder currently contains an outdated version of the .Net Core agent. The most up-to-date version of the .NET Core agent can be found in inlatest_release directory.

Upgrading

Tuesday, August 28, 2018 - 10:00

New Features

  • Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.
  • To enable distributed tracing, see .NET Agent configuration.

Upgrading

Thursday, August 16, 2018 - 15:00

New Features

  • Adds support for capturing request.uri attribute for WCF services when available.
  • [.NET Core] SQL query parameter values can now be captured on Slow SQL Traces on Linux.

Fixes

  • Fixes an issue where errors set to be ignored through configuration were not being ignored.
  • Fixes an issue where running the thread profiler can cause an application to terminate.
  • Fixes an issue where transaction events could be dropped.
  • [.NET Core] Fixes an issue for .NET Core applications running on Linux when serializing slow SQL trace and explain plan data for transmission to New Relic. Previously, the following exception would be seen in the agent logs: NewRelic ERROR: System.PlatformNotSupportedException: Operation is not supported on this platform.

Notes

  • We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly.
    • All downloads for the current version of the agent can be found in the latest_release directory on the download site.
    • Historical versions can be found in the previous_releases directory.

Upgrading

Monday, July 30, 2018 - 11:30

Download URLs

Download the appropriate release for your New Relic .NET agent:

https://download.newrelic.com/dot_net_agent/previous_releases

New Features

  • SQL query parameter values can now be captured on Slow SQL Traces. This feature can be enabled with the new configuration option datastoreTracer.queryParameters. The transactionTracer.record_sql configuration option must also be set to raw. See documentation here. This feature should be used with caution as it can lead to the capture of sensitive data. High Security Mode prevents the use of this feature. Windows support only. Linux support coming soon.
  • [.NET Framework] Adds support for tracking async transactions when .ConfigureAwait(false) is used from async controller actions in ASP.NET MVC applications.
  • [.NET Core] Adds support for .NET Core 2.1. Support for .NET Core 2.1 requires at least CLR version 2.1.3 and tiered compilation must not be enabled.

Fixes

  • [.NET Core] Fixes issue where status code based errors would be reported instead of the actual noticed Exception. This most commonly occurred with errors noticed in the ExceptionHandlerMiddleware (app.UseExceptionHandler(...)).
  • Fixes an issue where only the first request parameter is captured when request.parameters.* attributes are added to an include list.

Notes

  • We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly.
    • All downloads for the current version of the agent can be found in the latest_release directory on the download site.
    • Historical versions can be found in the previous_releases directory.

Upgrading

Tuesday, June 19, 2018 - 13:50

Download URLs

Download the appropriate release for your New Relic .NET agent:

https://download.newrelic.com/dot_net_agent/previous_releases

New Features

  • Adds automatic capture of datastore information for MongoDB driver versions 2.6.x, 2.5.x, 2.4.x, and 2.3.x.
  • [.NET Core 2.0] Adds thread profiler support for .NET Core applications running on Windows.

Fixes

  • Improved the agent's ability to recover from certain connection related issues without requiring an agent or application restart.

Upgrading

Wednesday, May 16, 2018 - 15:00

Download URLs

Download the appropriate release for your New Relic .NET agent:

https://download.newrelic.com/dot_net_agent/previous_releases

New Features

Fixes

  • [.NET Framework] Fixes issue of recursive directory creation when recovering from a failed upgrade install in the scriptable installer.
  • [.NET Framework] Fixes issue where Thread Profiler fails to resolve types and method names. These would appear as UnknownClass.UnknownMethod(<#>) in a profile.

Upgrading

Tuesday, May 1, 2018 - 15:00

New Features

  • [.NET Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

  • Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
  • Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
  • [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.
  • [.NET Framework] Fixed issue introduced in agent version 8.1.709.0 that caused some .NET Framework applications to throw the following exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.

Upgrading

Thursday, April 19, 2018 - 16:00

This release has been unpublished. Use version 8.1.712.0 or higher.

This version introduced a bug that could cause crashes for .NET Framework applications manually loading types from assemblies in the application domain. This includes enumerating custom attributes. The encountered error will appear like the following:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified

New Features

  • [.NET Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

  • Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
  • Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
  • [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.

Upgrading

Wednesday, March 7, 2018 - 14:00

New Features

  • Adds stripExceptionMessages configuration option to the newrelic.config file. When enabled, this will remove error messages from errors that are reported to New Relic. This is the same behavior as having High Security Mode enabled but can be used without High Security Mode. The default value for this setting is false.

Fixes

  • Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries that have multiple statements.

Other Changes

  • In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer allowed.
  • WCF service parameters are now captured as request.parameters.* attributes and are no longer sent as service.request.* attributes.
  • Minimum version required for use in EU Datacenter.

Upgrading

Wednesday, March 7, 2018 - 13:00

Download URLs

Download the appropriate release for your New Relic .NET agent:

This is a security-only release for the 6.x agents that support legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 and higher or .NET Core, the 7.x or later versions of the agent should be used.

Fixes

  • Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries which have multiple statements.

Upgrading

Tuesday, February 20, 2018 - 15:00

New Features

  • Improved metadata collection for cloud providers. The agent now collects additional metadata when running in AWS, GCP, and Azure. This information is used to provide an enhanced experience when the agent is deployed on those platforms.

Fixes

  • Fixed an issue where transactions could be dropped when they included datastore segments and the following exception was logged: NewRelic ERROR: An exception occurred while doing some background work: System.NullReferenceException: Object reference not set to an instance of an object.
  • Fixed an issue where SOAP instrumentation would report System.Reflection.TargetInvocationException errors when a more specific error existed. Inner exceptions will now be reported when they exist.

Deprecation Warnings

The follow items are considered deprecated and will be removed with the upcoming 8.x major release:

  • Disabling agent HTTPS communication via the service SSL configuration will no longer be allowed starting in 8.x versions of the agent.
  • WCF service parameters will no longer be sent as service.request.* attributes starting in 8.x versions of the agent. These parameters will be sent in the form request.parameters.*.

Upgrading

Thursday, February 8, 2018 - 11:14

Fixes

  • Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High Security Mode was enabled.

Upgrading

Monday, January 22, 2018 - 15:00

New Features

  • Modifying custom instrumentation XML files can now be performed without having to restart the monitored application. Instrumentation updates will be applied ‘dynamically’ at runtime. This feature required functionality provided by new APIs introduced in .NET Framework 4.5 and newer, which this release also addresses (see ‘Framework Support’ section below).

Fixes

  • Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High Security Mode was enabled.
  • Fixed an issue with automatic browser monitoring which could cause a stack overflow exception.
  • For custom instrumentation, the metricName parameter will be honored without needing to set transactionNamingPriority.
  • The scriptable installer will now successfully install and uninstall in scenarios where there is a space in the path to the installation files.

Framework Support

  • This release of the agent removes support for .NET Framework versions earlier than 4.5. See our community post about this from November of last year, for more details.
  • This is not an end of life for the 6.x agents (that support older .NET Frameworks), which will continue to work and report into New Relic.

Upgrading

Pages