# .NET 7 support in Dynatrace

**URL:** <https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340>\
**Category:** Open Q&A\
**Tags:** technologies, dotnet\
**Created:** [November 17, 2022, 2:04pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340 "2022-11-17T14:04:44Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sohaib](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@Sohaib](https://community.dynatrace.com/u/Sohaib)\
**Post date:** [November 17, 2022, 2:04pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/1 "2022-11-17T14:04:44Z")

</div>

Hello,

I couldn’t find anything related to Dynatrace and .NET 7.

By any chance, is there someone who tried one agent with this version and can confirm that it is supported?

I couldn’t find anything in the official documentation

Thanks

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [November 17, 2022, 2:51pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/2 "2022-11-17T14:51:30Z")

</div>

.NET 7 introduced some changes in the way, P/Invoke is being done, which requires some deeper changes in our managed\<-\>native interface within OneAgent. That’s why unfortunately this time it will take a bit longer for us to support new newest major version. The team is currently working on it and our current estimate is to have support in OneAgent Version 1.261 (~ March 2023) - no guarantees at this point though.

Here is the Up-to-date [Tech Support Roadmap](https://community.dynatrace.com/topic/183451) Page.

Update: OneAgent Version 1.163 will add full supporting .NET 7, to be released in April 2023.

---

<div class="post-metadata">

**Author:** ![Sohaib](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@Sohaib](https://community.dynatrace.com/u/Sohaib)\
**Post date:** [November 17, 2022, 2:53pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/3 "2022-11-17T14:53:41Z")

</div>

Thank you for the clear answer

---

<div class="post-metadata">

**Author:** ![Roxtar](https://avatars.discourse-cdn.com/v4/letter/r/5daacb/32.png) [@Roxtar](https://community.dynatrace.com/u/Roxtar)\
**Post date:** [November 18, 2022, 9:16am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/4 "2022-11-18T09:16:41Z")

</div>

Are you serious? Like, really serious? 🙃

This can’t be true…

.NET 7 is a major SDK release from a major vendor, I don’t know if you know this little start-up, what’s its name again? Maybe Microsoft :microsoft: ? (They even have a dedicated emoji on this forum).

The first RC of NET 7 (RC1, production ready) has been released the 14th of September. The first preview version was released 17th of February, ok it wasn’t production ready, but previews builds published so that vendors and developers can start updating their tools in anticipation of the migration.

And you’re telling us that we’ll have to wait till March 2023, without guarantees, to be able to monitor our NET 7 apps. That’s 7 months (let that sink in, **7 !!! MONTHS !!!** ) to upgrade your agent to the latest .NET SDK version, unbelievable.

I understand that there are some major changes introduced with .NET 7, but your competitors have done the job…

- DataDog : PR is in progress&nbsp;it’ll be available in the next few days

- NewRelic : it’s already supported

- Application Insights : nah just kidding, it’s MS, so obviously it’s supported.

Just for your information, if you finish the .NET 7 migration in March/April 2023, .NET 8 will probably be already released as a preview build and RCs release will be a few weeks ahead.

I’ll have a chat with our AM, this is a shame, it doesn’t make any sense to postpone a major SDK version migration just because of a monitoring agent that’s not up-to-date.

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [November 21, 2022, 7:44am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/5 "2022-11-21T07:44:02Z")

</div>

We hear you.

We typically aim for 0-day support for new runtime versions. Unfortunately, this time, technical complications and competing priorities have delayed us. The team is working hard to get this fixed. March is the conservative estimation. Chances are it will land sooner, but we can’t promise it at this time.

---

<div class="post-metadata">

**Author:** ![Christophe\_N](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Christophe\_N](https://community.dynatrace.com/u/Christophe_N)\
**Post date:** [January 25, 2023, 5:17pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/6 "2023-01-25T17:17:39Z")

</div>

Hi [@Christoph\_Neum](https://community.dynatrace.com/user/31344) ,

Do you have any news of this integration ?

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [January 27, 2023, 1:43pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/7 "2023-01-27T13:43:32Z")

</div>

Please check the [Tech Support Roadmap](https://community.dynatrace.com/topic/183451) page for up-to-date information.

---

<div class="post-metadata">

**Author:** ![LinusYng](https://avatars.discourse-cdn.com/v4/letter/l/aeb1de/32.png) [@LinusYng](https://community.dynatrace.com/u/LinusYng)\
**Post date:** [February 6, 2023, 1:50pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/8 "2023-02-06T13:50:48Z")

</div>

So what will dotnet7 support include? Just what we have now for dotnet7 or critial improvements like actually working with open telemetry and activities?

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [February 6, 2023, 4:08pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/9 "2023-02-06T16:08:40Z")

</div>

[@LinusYng](https://community.dynatrace.com/user/57751)&nbsp;It will come with all the features of the .NET Code Module, that are available already.

This includes integration of DiagnosticSource Activities and OpenTelemetry Spans.

---

<div class="post-metadata">

**Author:** ![LinusYng](https://avatars.discourse-cdn.com/v4/letter/l/aeb1de/32.png) [@LinusYng](https://community.dynatrace.com/u/LinusYng)\
**Post date:** [February 7, 2023, 5:31pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/10 "2023-02-07T17:31:20Z")

</div>

I will take that as promise that span will work correctly come april then instead of DT creating new spans by its own.

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [February 8, 2023, 6:20am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/11 "2023-02-08T06:20:44Z")

</div>

[@LinusYng](https://community.dynatrace.com/user/57751)&nbsp;Our agent will work the same way in that regard in .NET 7, like also in previous versions.

The DiagnosticSource Activity support instruments the Activity API’s, and re-creates those Activities as Spans in the PurePath model. Including all attributes/tags.

Can you elaborate what you think we could improve within that feature?

---

<div class="post-metadata">

**Author:** ![LinusYng](https://avatars.discourse-cdn.com/v4/letter/l/aeb1de/32.png) [@LinusYng](https://community.dynatrace.com/u/LinusYng)\
**Post date:** [February 8, 2023, 6:31am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/12 "2023-02-08T06:31:40Z")

</div>

_Currently&nbsp;we do not have TraceContext in-process interop._  
_This means that the OneAgent TraceContext does not coordinate with .NET Core TraceContext. So both systems create their own, which is why you see different ids_

We had issues with OneAgent instrumentation so I ask dynatrace support and they replied with the above.&nbsp;So unless that is solved, the no I would not say that trace context works as one might expect because it is then impossible to add instrumentation or other sources using OneAgent and open telemetry. The SDKfeels like dead end and then we had turn to otel ingestion which adds addtional costs.

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [February 8, 2023, 6:38am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/13 "2023-02-08T06:38:54Z")

</div>

It depends what your use-case is.

It is true that OneAgent cannot synchronize the TraceId with DiagnosticSource. Each system uses their own TraceId. If your use-case is log-enrichment with TraceIds, we recommend using the Dynatrace OneAgent SDK, which has an API to access the PurePath TraceId.

If your use-case is enriching PurePath with additional information, or additional Spans, then using the Activity API should work just fine.

If your use-case is Distributed Tracing, this should also work, if you use the built-in .NET Propagators (or OpenTelemetry Propagators for that matter) in order to extract or inject context. OneAgent should properly integrate with these API’s as well.

---

<div class="post-metadata">

**Author:** ![LinusYng](https://avatars.discourse-cdn.com/v4/letter/l/aeb1de/32.png) [@LinusYng](https://community.dynatrace.com/u/LinusYng)\
**Post date:** [March 2, 2023, 8:49am UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/14 "2023-03-02T08:49:33Z")

</div>

I does not seem to work.

But it would be good if this was documented somewhere.

---

<div class="post-metadata">

**Author:** ![yvshett](https://avatars.discourse-cdn.com/v4/letter/y/4da419/32.png) [@yvshett](https://community.dynatrace.com/u/yvshett)\
**Post date:** [November 16, 2023, 4:56pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/15 "2023-11-16T16:56:42Z")

</div>

Is this Released as per April 2023 mentioned date? that means .NET Core 7 App use Dynatrace right?

---

<div class="post-metadata">

**Author:** ![Christoph\_Neum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christoph_neum/32/21662_2.png) [@Christoph\_Neum](https://community.dynatrace.com/u/Christoph_Neum)\
**Post date:** [November 28, 2023, 2:15pm UTC](https://community.dynatrace.com/t/net-7-support-in-dynatrace/37340/16 "2023-11-28T14:15:52Z")

</div>

Yes. .NET 7 Apps are fully supported by Dynatrace, April 2023, as documented here:&nbsp;[New technology support — Dynatrace Docs](https://docs.dynatrace.com/docs/whats-new/new-technology-support#id-1-263-oneagent)

Meanwhile, .NET 8 was just released by Microsoft just last week and we have 0-day support for it (with OneAgent 1.277):&nbsp;[New technology support — Dynatrace Docs](https://docs.dynatrace.com/docs/whats-new/new-technology-support#id-1-277-oneagent)
