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.

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/latest_release

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

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.

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

Monday, December 18, 2017 - 14:00

New Features

  • The request URI for a web transaction will now be included as an attribute of transaction events and error events.
  • The New Relic .NET Status Monitor has been retired and is no longer included in the install. The replacement tool is New Relic Diagnostics. To download the most recent version, select the link in the New Relic Diagnostics documentation.

Fixes

  • Security Bulletin NR17-06: Fixes issue where query parameters were being included in the URL property of transaction trace segments for external calls (uses of System.Net.HttpClient, System.Net.WebRequest, or third-party libraries which are built on top of those). Query parameters will no longer be included in transaction trace segments.
  • Transaction names will be rolled up for web transactions resulting in a 400 or 500 level HTTP status code and a higher priority name has not been set. This helps prevent metric grouping issues.
  • Fixed error that could result in the one time loss of a metric and/or transaction for an instrumentation point at the start of monitoring an application. "...NewRelic ERROR: Tracer invocation error: System.ArgumentException: An item with the same key has already been added. Key: ..."
  • Minor log level adjustments in the profiler logging. Suppresses benign error Failed to tokenize method signature: class System.Reflection.Assembly System.CannotUnloadAppDomainException::LoadAssemblyOrThrow(string)
  • [.NET Core 2.0] For .NET Core agent users on Linux, this release fixes a problem with the run.sh convenience script in combination with a custom installation path.
  • [.NET Framework] Fixes issue resulting in SerializationExceptions when using .Net Remoting.

Upgrading

Thursday, November 30, 2017 - 14:00

New Relic Agent for .NET Core 2.0 GA

Highlights

  • Windows and Linux support, including Azure App Services and Docker
  • Automatic instrumentation for ASP.NET Core applications running on Kestrel
  • External calls via HttpClient
  • Database instrumentation for System.Data.SqlClient, Npgsql, and MySql.Data
  • Custom instrumentation via XML and transaction/trace attributes
  • NewRelic.Agent.Api support

For a more detailed list, see the compatibility documentation.

The .NET Core 2.0 agent is a separate install and can live side-by-side on the same server as the .NET Framework agent. For installation information, follow the procedures for your operating system as applicable:

New Shared Features

  • Database instrumentation performance has been improved.
  • Explain plans are no longer captured by default for supported database systems: Microsoft SQL Server and MySQL. Explain plans can be enabled via configuration.

Updating the Agent

Thursday, November 2, 2017 - 10:00

New Features

  • The agent now supports running in FIPS compliance mode.

Fixes

  • Fixed an issue that caused some transactions to report start time in the server's local timezone instead of UTC.
  • Additional bug fixes to remedy a SerializationException caused by the agent.

Upgrading

Tuesday, October 3, 2017 - 12:00

New Features

  • Adds support for RestSharp library. The Agent can now instrument async and non-async methods from a RestSharp client. For supported methods, please visit here.
  • The application name reported to New Relic APM can now be set by defining the NEW_RELIC_APP_NAME environment variable.

Fixes

  • Fixed some situations where SerializationException occurs in the agent log file.
  • The injection of Browser Monitor JavaScript directly above the body tag on a page should occur less often.
  • Fixes issue where datastore instance information would not be reported for some NpgsqlCommand async calls.
  • Fixed remaining cases where 9-digit SQL trace identifiers were generated, failing Data Loss Prevention monitors which interpret the value as a Social Security Number.

Upgrading

Monday, August 28, 2017 - 13:41

New Features

  • Custom instrumentation can now be declared by applying the agent API's new Transaction and Trace attributes to methods. Using the Transaction attribute, transactions can be marked as Web vs. Non-Web. For more information, see Custom instrumentation via attributes.

Fixes

  • Fixes bug preventing instrumented apps from shutting down due to Profiler failure to detach.

Upgrading

Thursday, August 3, 2017 - 16:00

New Features

  • Adds instrumentation for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 3.* Instrumentation includes async-await support.
  • Adds async-await support for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 2.*.

Fixes

  • Fixed an issue where SQL instrumentation could raise exceptions and cause it to shutdown.
  • Error traces now include the full stack trace, including any inner exceptions.

Upgrading

Wednesday, July 12, 2017 - 10:30

New Features

  • Performance improvements when slowSQL is enabled, particularly for apps with lots of slow SQL queries.

Fixes

  • Fixed an issue that was preventing the proper setting of Key Transaction Apdex scores based on their configured ApdexT values.
  • Fixed an issue preventing the collection of transaction traces for Key Transactions based on their configured ApdexT values.

Upgrading

Thursday, June 15, 2017 - 10:30

New Features

  • Agent overhead is reduced for transactions composed of an unusually large number of small activities.

Fixes

  • Enhanced low-level logging to improve supportability.
  • Fixed a problem with new installs using the Thin Installer where false permission errors could be reported.

Upgrading

Wednesday, May 24, 2017 - 17:00

Fixes

  • In some cases, the trace breakdown table overreported segment times. This happened when these three conditions were met, 1. instrumentation occurred through custom XML files, 2. the segment name was overridden, and 3. the segment contained child segments.

Upgrading

Wednesday, May 17, 2017 - 09:15

Fixes

  • Fixed an issue preventing injection of a mscorlib reference into every module.

Upgrading

Thursday, May 11, 2017 - 15:00

New Features

  • The .NET agent no longer supports Windows Server 2003. Applications running on Windows Server 2003 will be required to use .NET agent version 6.11 or lower. For more information, get support at support.newrelic.com or download the agent at http://download.newrelic.com/
  • Reduced overhead of the agent for transactions that contain many segments.
  • Reduced performance overhead for instrumented methods. Low latency, high-throughput applications may also see a reduction in CPU overhead.
  • Reduced the overhead associated with method JITs. This will reduce the overall startup time and memory footprint of instrumented applications.

Fixes

  • Methods associated with wrappers that have been disabled due to too many exceptions are no longer instrumented by the default wrapper. The previous behavior could result in orphaned metrics and a potential degradation in performance.

Upgrading

Pages