.NET6 testing/support

[gregkalapos]

No description provided.

[gregkalapos]

Framework detection doesn't work:

      {AbstractConfigurationReader (EnvironmentConfigurationReader)} The agent was started without a service version. The automatically discovered service version is 1.0.0
fail: Elastic.Apm[0]
      {Service} Failed to detect whether the current .NET runtime is .NET Full Framework, Mono or .NET Core - `N/A' will be used as the current .NET runtime name
fail: Elastic.Apm[0]
      {Service} Failed to detect whether the current .NET runtime is .NET Full Framework or .NET Core - `N/A' will be used as the current .NET runtime version

[gregkalapos]

First tested on macOS with ASP.NET Core minimal API - no transactions were detected. Installed Visual Studio on Windows to debug - it did work on Windows as expected. Then installed Visual Studio for mac on macOS - I did not manage to get it work, then installed Rider preview with .NET 6 support, with that I was able to debug, but then the issue went away again - all transactions were captured as expected.

I give up on this part - this works as intended - if we manage to reproduce it again I'll dig deeper, but this may be related to a not fully functional RC build.

[ffMathy]

@gregkalapos now that dotnet 6 is out, is it possible for this to be released faster, at least as a beta or something?

It's the only package preventing us from upgrading. And that's a bit of a shame, considering that the fix is right here 😂

[gregkalapos]

@ffMathy we are working on a release - should be out very soon.

[anshivank]

@ffMathy we are working on a release - should be out very soon.

Hi @gregkalapos, Is there any update on this? We recently upgraded our application from .Net5 to .Net 6. We were using the package Elastic.Apm.NetCoreAll and and the app.UseAllElasticApm(config) method. It was working fine and we were able to see the APM logs in Elastic Observability. But after upgrading to .NET 6, it's not working. We found the issue is the incompatibility of Elastic.Apm.NetCoreAll package with .Net 6. Could you please suggest if there's a work around to make this work in .Net 6?

Thanks

[gregkalapos]

Hi @anshivank - in this issue the only thing I identified was the service detection issue above, but that's fixed and released.

I'm not sure what exactly your issue is. Could you maybe file a new one with a more detailed description on what does not work for you on .NET 6? Fyi we already run all our tests on .NET 6 as well, so it should be ok - unless you found something which we don't cover yet. In any case... please let's open a new issue and let's discuss what you ran into.