Does Radzen components support .net 8

John_Lee · June 9, 2023, 4:35am

Does Radzen components support .net 8?
How about .net 7?

enchev · June 9, 2023, 4:55am

.NET 8 is not yet officially released - it will be supported when it’s official. All previous versions of .NET including .NET 6 which is LTS and .NET 7 are supported:

github.com

radzenhq/radzen-blazor/blob/master/Radzen.Blazor/Radzen.Blazor.csproj#L4


      
          <Project Sdk="Microsoft.NET.Sdk.Razor">
            <PropertyGroup>
              <NoWarn>BL9993;BL0007;BL0005</NoWarn>
              <TargetFrameworks>netstandard2.1;net5.0;net6.0;net7.0</TargetFrameworks>
              <RazorLangVersion>3.0</RazorLangVersion>
              <LangVersion>7.3</LangVersion>
              <OutputType>Library</OutputType>
              <IsPackable>true</IsPackable>
              <PackageId>Radzen.Blazor</PackageId>
              <Product>Radzen.Blazor</Product>
              <Version>4.13.0</Version>
              <Copyright>Radzen Ltd.</Copyright>
              <Authors>Radzen Ltd.</Authors>
              <Description>Radzen Blazor is a set of 70+ free native Blazor UI controls packed with DataGrid, Scheduler, Charts and robust theming including Material design and Fluent UI.</Description>

evant · June 18, 2024, 11:41pm

.NET 8 is now officially released and <RadzenTemplateForm> does not support it (because it does not support AntiforgeryToken or @formname. )

Now I have to take all RadzenTemplateForms out of my site and replace with EditForms or just plain forms.

enchev · June 19, 2024, 3:40am

Not sure what you are referring. Can you clarify?

korchev · June 19, 2024, 4:28am

Hi @evant,

I do know what @evant is referring to @enchev. However an issue I have opened in the ASP.NET github repository stays unresolved and I don't know how we can support form name properly. There is another related one. @evant you can monitor the github discussion for the progress. Long story short we don't know how to support that as part of the Blazor API is internal and can't be used by library authors.

evant · June 19, 2024, 3:47pm

To be more specific, Radzen forms don't work with the new "Blazor Web App" format in .NET 8. Because .NET 8 is backwards compatible with .NET 7 style Blazor Server apps, it continues to work fine- for now. I'm sure that sooner or later the Blazor Server app format is going to be deprecated, which is why I wanted to upgrade everything now and get it out of the way. <RadzenTemplateForm> is the only thing standing in the way of that, and since the site has about 50 of them, I am going to target .NET 8 but keep it a Blazor Server App and hope Radzen can work out a fix before I'm forced by Microsoft to do the rest of the upgrade.

korchev · June 19, 2024, 3:50pm

I don't think this would happen as a lot of apps will stop working. Also Blazor server isn't going anywhere - it is supported in Blazor 8 just fine by enabling server interactivity. You don't need to update anything IMHO unless you want to use static server rendering without interactivity. Even if you migrate to EditForm be warned that no interactive feature works in SSR (opening a dropdown, sorting a data grid etc.)

korchev · June 19, 2024, 3:52pm

They will work flawlessly if you enable interactivity for the component that hosts them. Our online demos use .NET 8 as well as thousands of applications created with Radzen Blazor Studio.

jnsn · December 3, 2024, 6:59pm

As I was recently migrating a website with ASP.NET Core Identity to .NET 8 I bumped into this issue as the Radzen forms were not working out of the box on those pages.

I've ultimately reverted to using the default Microsoft form, and added the Radzen CSS classes for now, but as a quick test I simply copied the FormMappingValidator and one additional extension method to my project, copied the RadzenTemplateForm to a new custom component, include the necessary code and everything seemed to work as I'd expected.

I'm not sure if this is a) an approach you could do?, or b) something you have any objections or remarks against me doing this?

As part of my project I'm also exposing some functionality to plugin authors, and I'm not sure whether I really want to expect them to use my custom RadzenTemplateForm override.

korchev · December 4, 2024, 7:46am

RadzenTemplateForm won't work until the linked issues are resolved by Microsoft. Adding a new form component would lead to confusion - when to use RadzenTemplateForm and when to use the other one.

You are free to do whatever you want as long as it does not violate the MIT license.

jnsn · December 25, 2024, 7:05am

Hello,
Sorry for the late reply but it's been busy.

My point for a) was, since the missing implementation is just a few lines of code, can't you, as Radzen, create your own version of this for the time being? Until Microsoft, hopefully in .NET 10, exposes this and it can be replaced by their implementation.

korchev · December 25, 2024, 10:16am

What is the missing implementation that is a few lines of code?