The current PR seems to run with local CSFML 3.0 binaries (i.e. all example programs seem to run without any immediate issues), so I think it's now possible for people to test it out if they want to (although I'd expect it to crash in a lot of other places).

Since CSFML and SFML.Net 3.0 nuget packages are not available yet, here's instructions on how to build local CSFML and SFML.Net nuget packages for Windows / Visual Studio 2022:

Before all:

• run dotnet nuget locals all --clear to clear previous cached packages if needed (i.e. if you update the package code but use the same version)

For CSFML 3.0:

• Clone CSFML master branch (or https://github.com/Marioalexsan/CSFML/tree/render-states if the latest CSFML PR is not merged yet)
• Open a Powershell terminal in tools/nuget and run ./build.win.ps1
• in tools/nuget, run dotnet pack -c Release
• in Visual Studio 2022, in Tools -> NuGet Package Manager -> Package Sources, add a path to CSFML/tools/nuget/CSFML/bin/Release

For SFML.Net 3.0:

• run dotnet build -c Debug
• in Visual Studio 2022, in Tools -> NuGet Package Manager -> Package Sources, add the following paths:
  • SFML.Net\src\SFML.Net\bin\Debug
  • SFML.Net\src\SFML.Graphics\bin\Debug
  • SFML.Net\src\SFML.Audio\bin\Debug
  • SFML.Net\src\SFML.Window\bin\Debug
  • SFML.Net\src\SFML.System\bin\Debug
• create a new project, and add the following to your .csproj:

<ItemGroup>
    <PackageReference Include="SFML.Net" Version="3.0.0-alpha1" />
</ItemGroup>

I've tested this flow with a new console project that uses one of the examples as source code, but let me know if it breaks in some other cases.

I've taken the liberty to update your branch by splitting the one commit into two, extracting the test stuff into a dedicated commit.
Also you can't really (in an easy way) multi-target tests while mixing it in the same solution. So I just limited it to .NET 6