As you may know the official release of .NET 8 is around the corner! It is expected to ship tomorrow (November 14th 2024). We plan to release a new update of Radzen Blazor Studio with official support for .NET 8 shortly after - we just need to update the references and conduct internal tests.
Here is what's new:
New .NET 8 specific application type - Blazor Web Application. It allows to pick interactivity mode - server, web assembly or auto (both).
Radzen Blazor Studio would require .NET 8 SDK to be installed on your machine. This is important: Radzen Blazor Studio won't start if you get the new version via auto update and don't have .NET 8 installed. The solution is simple - just download and install the .NET 8 SDK for your OS. It is backwards compatible with .NET 7 so your existing applications will continue to work as expected. If you are not ready to install .NET 8 yet just skip the autoupdate by clicking the Not now button.
Best,
Atanas Korchev,
on behalf of the Radzen Team
I found errors in both my non RBS app and my main RBS app this morning after attending the conference online and upgrading VS2022 to 17.7.7. I also installed new Net 8.
They had run fine before the 2 upgrades.
SOLUTION:
I found in my case; current code runs fine in the VS 2022 Preview.17.9
We are currently running latest .NET 8 SDK with current (pre .NET 8) Radzen Blazor Studio without any issues. We have been doing this for months. Maybe Visual Studio is the culprit and removes the .NET 7 SDK.
As I said we are have been using current official RBS with .NET 8 for a couple of months now. It will work as long as you also have .NET 7 SDK installed.
If you are asking for the ability to create .NET 8 Blazor Web applications - you will have to wait for the next release then. Until then I suggest checking how the new Blazor rendering modes work as it catches a lot of developers by surprise: ASP.NET Core Blazor render modes | Microsoft Learn
You can just download an earlier version. However the .NET 8 requirement does not mean that your apps must use .NET 8 too. You can still develop .NET 7 apps with the latest version.
Learned of a correction if RBS code doesn't run in VS 2022 17.8.
I found that in the Installer, the checkmarks for .net6 , net7 webassembly buildtools were left off, which checked and updated. 17.8 works fine again on RBS ciode,
I mostly understand the concepts behind the different rendering modes.
I'm in the middle of development of a Blazor server app.
It uses API calls that I copied into the app from a sample/baseline WASM app.
I'll need to build a mobile app that interacts with my database and uses native phone functions (so can't use PWA)
I don't have a great answer for why I chose Server App vs. WASM in the first place. It's an internal business application so that is probably why I chose Server (plus that is most of my experience).
Would you recommend starting over with an Interactive Auto rendering mode (would just use it globally vs. component by component)?
I have to think about how long it would take to redo my customization on my current app, I don't think it would be too bad...
I don't even know if I would notice the difference to be honest.
I think it is a matter of wanting to build the app to the latest and greatest available at the time. I'm already targeting .NET 8 so would just be utilizing the latest Blazor rendering model.
I think it will help me with mobile app dev down the line?
I think another option would be to modify my existing app to use Interactive Auto? Don't think I want to tackle that. I'd rather start with a fresh app.
Would appreciate any comments/recommendations, thank you!
