Aaron Stannard

Ok, marking it as resolved via #7624

@dependabot rebase

Akka.NET is still 100% compatible with .NET Framework (we still target .NET Standard 2.0.) All of our unit tests are dual targeted for .NET Framework 4.8 and .NET 8. https://github.com/akkadotnet/akka.net/blob/55827b71316eff96311679b2cfa588bc4cce60aa/src/core/Akka.Cluster.Tests/Akka.Cluster.Tests.csproj#L5...

> Thanks for your detailed answer. > > I created a .NET Framework 4.8 project and tried to install the NuGet package Akka.Analyzers 0.2.5, but I keep getting the error...

So I just tried opening a new .NET 4.7.1 solution in Rider and got the same problem 

I think this is a more subtle build tooling issue than I originally suspected - apparently it works in our test suite because we're referencing it through a .NET Standard...

lol the worst part is - Akka.Analyzers is, itself, a .NET Standard 2.0 package 🤯

Working on a reproduction here: https://github.com/akkadotnet/akka.analyzers/pull/103 Apparently it's a bug with how we're delivering the NuGet package. A local reference to the Akka.Analyzer's `.csproj` works fine.

> That reminds me of DLL hell :-) Thanks for watching anyway ! No problem - it's one of those cases where we literally run .NET Framework builds of this...

Ok, well I found a better explanation for this problem - it's your MSBuild tooling, using the old-style project types that pre-date MSBUILD15 https://github.com/xunit/xunit/issues/2943#issuecomment-2145579215 https://github.com/dotnet/sdk/issues/41352 I'll take a look at...