I love the conversation and questions.
The reference Roon Ready code shared with partners to include in their products is written in c and the scripts delivered at run-time run are executed through that c code. It all uses standard networking to communicate with the Roon Server. There are no .net dependencies with it.
The Auralic device will continue to work with future Roon versions regardless of how we build Roon. The Roon Ready devices don’t use Roon Bridge so the .net dependencies don’t apply.
@Alan_Bateman , to answer your questions …
-
moving Roon to .net 10 doesn’t require any changes to Roon Ready devices.
-
The Roon Ready code will remain optimized for audio gear that spans from specialized devices to ones with high end processors. Dotnet isn’t supported across all these devices so isn’t part of it.
-
No changes needed to push to Roon Ready devices. However, generally, if there are improvements to be made, it can be done at runtime on the device.