You’ve heard New Relic assure you that we’ll provide support for .NET Core but we’ve been light on details resulting in our community of customers feeling frustrated about both the lack of support for .NET Core and lack of updates.
First of all, we get why .NET Core is important to you. .NET Core is an exciting change in the Microsoft ecosystem that benefits Microsoft developers in ways that developers in other language ecosystems have enjoyed for years. We know you’re excited to run applications on Linux and take advantage of both the ease of use and the incredible performance improvements available when using .NET Core.
We’ve been working with .NET Core for a while now and have seen how it’s matured over the last several months: .NET Standard 2.0 is coming out, project structures are solidifying, API availability is hardening, developer toolset is growing and, most importantly, we’re seeing the Microsoft developer community embrace .NET Core as it’s reached maturity.
New Relic is committed to supporting .NET Core and I’d like to share the high level plan we’re executing behind the scenes to bring .NET Core support to you.
Phase 1 (already in progress)
First up, we’re working to prepare the New Relic .NET agent, which includes changing the build infrastructure, implementing new performance and functional test coverage, and removing pre-async code and legacy dependencies, among other projects to ensure .NET Core and .NET Framework are both adequately supported. With this phase, we’re setting up the .NET agent for faster innovation.
Phase 2 - Full ASP.NET Core Support for the Agent running in Windows
During this phase, we will build support for profiling an ASP.NET Core application using the .NET agent on a Windows server. This will be our first generally available release of the New Relic .NET agent that supports .NET Core applications.
Phase 3 - Basic ASP.NET Core Support for the Agent running in Linux
With this phase, we will build support for running the .NET agent on an ASP.NET Core application on Linux.
Not included in this phase is profiler integration since the CLR profiler APIs for the Linux platform remain unverified. However, we believe in providing as much functionality as we can, when we can, so we plan to release the Linux support we do have if we end up getting blocked by this.
Phase 4 - Implement Profiler Support for .NET Core on Linux
New Relic plans to publish our findings from our Linux CLR profiler API tests to the community. For all the CLR profiler API functionality that we validate, we intend to add profiling support for Linux into the .NET agent. This will give users the ability to profile an ASP.NET Core application using the .NET agent on a Linux server.
How to get involved
We hope to learn a lot from our customer community as we progress through each of these phases. Tell us what your environment looks like and let us know if you’re interested in participating in an early access program by completing this survey.
Your input will help shape the direction we move in!
Here’s something Legal makes me say every time I talk about things that we’re in the process of building but haven’t yet shipped:
This post contains “forward-looking” statements, as that term is defined under the federal securities laws, including but not limited to statements regarding the .NET Core Agent as well as potential benefits derived therefrom. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause New Relic’s actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect New Relic’s financial and other results and the forward-looking statements in this press post is included in the filings New Relic makes with the SEC from time to time, including in New Relic’s most recent Form 10-Q, particularly under the captions “Risk Factors” and “Management’s Discussion and Analysis of Financial Condition and Results of Operations.” Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at http://ir.newrelic.com or the SEC’s website at www.sec.gov. New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law.