Testing headless .NET 8 -> .NET 9 update #3196
Replies: 5 comments 24 replies
-
Doing a quick test, the update to .NET 9 seems to be working fine. |
Beta Was this translation helpful? Give feedback.
-
Added a small migration guide to the wiki (even though this one is really easy): https://wiki.resonite.com/Headless_Server_Software/Migration_Net9 Headless-wise, no bugs to be reported, everything runs fine. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
I updated my headless (hosted on an arm64 device, had to recompile Resonite.dll) Everything running good so far! |
Beta Was this translation helpful? Give feedback.
-
UPDATE: We are postponing the switch until next Monday on December 2nd! |
Beta Was this translation helpful? Give feedback.
-
Hello everyone!
I've got another test for you & heads up for upcoming update!
What is being tested
I've updated the headless client from .NET 8 to .NET 9 runtime which has released earlier this month.
This is mostly just a flag change and I don't really expect any breakage to actually happen. However since there's a number of tools in the community, I want to give everyone to give opportunity to prepare for the switch, particularly users hosting events and we might as well use that as opportunity to test this.
#3176
Current build number
2024.11.19.510
IMPORTANT: The build is compatible with current public build as well! You can host sessions with .NET 9 headless already and users will be able to join from the normal non-prelease build.
How to test
prerelease
branch and make sure the build updates before you run itWhat to test
What NOT to test & report
If you find something that got broken
Create a GitHub issue for a pre-release bug: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/new?assignees=shiftyscales&labels=prerelease&projects=&template=prerelease.yml
Make sure to include the log
Please include description of what happened. Be succinct, but exact.
If you find a roadblocker that's not a bug, but something on your end that would disrupt events and you want us to delay this update, please let us know in this discussion with your reasoning
Similarly if you for some reason cannot update the tooling in time and we'd disrupt your events, let us know and we can see if we can postpone the release to main
If you find that stuff works okay
Please report it too and include details on what you generally tested, so we know things are okay. You don't need to make a new issue for this - just a commend in this Discussion is fine.
This lets us know that a bunch of stuff was tested and get better confidence that stuff won't break with release.
Optional testing
This is not really needed, since it won't change the course of our action in any way, but if you'd like to gather some interesting data, I'd be curious to see how does the performance between .NET 8 headless and .NET 9 headless differ! If you gather some cool data, I'd love to see!
How long will testing go for?
We plan to make the switch to .NET 9 next Monday, which is on November 25th to give you some time to prepare.UPDATE: The switch is now postponed to the Thursday next week, which is on November 28th.UPDATE 2: The switch is now postpones to next Monday, which is on December 2nd.
We can re-evaluate if you hit roadblockers, but please give it a test if you can!
Beta Was this translation helpful? Give feedback.
All reactions