.NET agent release notesRSS

Fixes

• Fixes a bug where the .NET Agent was not handling exceptions coming from HttpRequest.Path and HttpRequest.Url properties. Because the exception was unhandled users would see a System.Web.HttprequestValidationException in their log files and in some cases could miss transactions being reported.
• Fixes a bug where the .NET Agent was throwing null reference exceptions when tracing some SQL commands where there was no transaction available.
• Fixes a bug where the .NET Agent was reporting StackExchange.Redis call times incorrectly. Now, the agent reports the correct call times for apps that use StackExchange.Redis synchronously.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

Fixes

• Fixed a bug that caused certain frameworks (such as EpiServer CMS) to throw exceptions when trying to resolve a reference to JetBrains.
• Fixed a bug that caused ASMX web service exceptions to not be noticed. This would result in missing some error details, such as stack traces.
• Fixed a bug where sometimes transactions will not be reported if the HttpClient class is used during that transaction.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

Fixes

• Fixed a bug that prevented self-hosted WCF applications from automatically creating Traced Errors.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

New Features

• Added StackExchange.Redis framework support. The .Net agent now records time spent making StackExchange.Redis API calls, which will appear as Datastore metrics and Transaction Trace segments in New Relic APM.

Fixes

• Fixed a bug that cause Automatic Browser Monitoring to cause problems on web pages that have no HEAD tag and also contain the text "<BODY" inside of an inline script.
• Improved agent error reporting for applications using WebAPI v1 in unsupported configurations. A warning will be displayed in the agent log (during agent startup) if an application is using an unsupported configuration.
• Azure KUDU (scm) sites were being instrumented by the .NET Agent due to a change in the way Azure is naming application pools. We have updated our logic to match the new application pool naming so these sites will be ignored by the agent.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

New Features

• Added ServiceStack.Redis v3.x and v4.x framework support. The .Net agent now wraps time spent making ServiceStack.Redis API calls, which will appear as Datastore metrics and Transaction Trace segments in New Relic APM.

Fixes

• Fixed a bug that caused web transaction data to be lost if the request contained an invalid "Referer" HTTP header.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

Fixes

• Fixes a bug which caused the .NET Agent to stop reporting intermittently due to an exception raised within the .NET Framework and caught by the Agent.
• Fixes an unhandled System.ObjectDisposedException in the agent.

Fixes

• Web requests for static resources which are handled by System.Web.Optimization will be named with the requested URL instead of the unmapped route parameters (some previously were named {controller}/{action}/{id}).

Fixes

• Transactions using MVC attribute routing will show the correct action name instead of "Unknown Action".

New Features

• Adds an API method for setting the name of the application reported to in New Relic at runtime.
• Adds a configuration option for stopping the agent from reporting automatically when the agent starts up.
• Adds an API method for telling the agent to start reporting at runtime.

Fixes

• Fixes a bug where self-hosted WCF applications would not correctly report on the overview page.
• Fixes a bug where database calls and external calls in a background/async thread would result in a transaction named * showing up in the Other bucket.
• Fixes a bug where apdex was not reported for self-hosted WCF applications.
• Fixes a bug where API calls from an application that didn't have any instrumentation would not report any data.
• SQL object names are more accurately parsed. In particular, table names will be recognized with an expanded set of characters. The agent is able to parse table names with a variety of separator characters and formatting whitespace. For example, {Table1}, [ Table2 ], "Table3" and Table4.

Known Issues