Files
Vladimir Enchev 1fac64e573 .NET 11 support added and .NET 8 support removed. Radzen.Blazor now targets net9.0, net10.0 and net11.0 with 11.*-* Components references, and the Sass, MoveCss and MinifyJs targets key on net11.0; the test, demo, API, tools and trimming projects, the Dockerfile images, the CI, deploy and NuGet workflows and the e2e docs moved to net11.0. The always-true NET6_0_OR_GREATER and NET8_0_OR_GREATER conditionals were collapsed. EditContext.Validate is obsolete in .NET 11, so RadzenTemplateForm, RadzenSteps and RadzenDataGrid.UpdateRow await ValidateAsync on net11.0, and the demo host dropped the obsolete UseWebAssemblyDebugging call with its inspectUri launch entries. The new .NET 11 analyzers are fixed rather than suppressed: CA1307 call sites pass StringComparison.Ordinal with the net11-only char overloads polyfilled for net9 and net10 in StringComparisonExtensions, CA1860 Any() calls compare Count or Length, CA2263 uses a GetJsonTypeInfo<T> helper that takes the generic GetTypeInfo overload on net11, and BL0012 removed seventeen StateHasChanged calls from private event handlers that ComponentBase already renders after. BL0016 (unguarded JS interop) stays in NoWarn because it accepts only a try/catch around each of 272 interop calls. The tests moved to bUnit 2.13.3, which drives the .NET 11 Virtualize component natively, behind a compatibility layer so the test sources stay as they are on master: Radzen.Blazor.Tests.TestContext derives from BunitContext and keeps RenderComponent, the ComponentParameter.CreateParameter overload and a synchronous DisposeComponents, extension methods keep SetParametersAndRender and ToMarkup, and global using aliases map TestContext, ComponentParameter and IRenderedFragment for every test namespace, so tests written against either bUnit version compile unchanged and merges from master carry no test churn. The real .NET 11 changes in the tests are a handful: EditContext.Validate is obsolete so the DataAnnotationValidator tests await ValidateAsync, AIChatService.TryQueueMessageAsync became virtual so the fake overrides it, xunit moved to 2.4.2 and its NotNull annotations make two Assert.Equal(float, float, int) calls name the precision argument and two Markdown update asserts check for null first, and CS8632 is silenced in the project because the annotations in test files without a nullable context are harmless. The chart tick label expectation follows the exact double-to-decimal conversion in .NET 11. Verified with the full suite on net11.0, the trimmed runtime gate and Playwright against the demo app for the components whose StateHasChanged calls were removed.
2026-11-09 14:16:17 +02:00
..
.NET 11 support added and .NET 8 support removed. Radzen.Blazor now targets net9.0, net10.0 and net11.0 with 11.*-* Components references, and the Sass, MoveCss and MinifyJs targets key on net11.0; the test, demo, API, tools and trimming projects, the Dockerfile images, the CI, deploy and NuGet workflows and the e2e docs moved to net11.0. The always-true NET6_0_OR_GREATER and NET8_0_OR_GREATER conditionals were collapsed. EditContext.Validate is obsolete in .NET 11, so RadzenTemplateForm, RadzenSteps and RadzenDataGrid.UpdateRow await ValidateAsync on net11.0, and the demo host dropped the obsolete UseWebAssemblyDebugging call with its inspectUri launch entries. The new .NET 11 analyzers are fixed rather than suppressed: CA1307 call sites pass StringComparison.Ordinal with the net11-only char overloads polyfilled for net9 and net10 in StringComparisonExtensions, CA1860 Any() calls compare Count or Length, CA2263 uses a GetJsonTypeInfo<T> helper that takes the generic GetTypeInfo overload on net11, and BL0012 removed seventeen StateHasChanged calls from private event handlers that ComponentBase already renders after. BL0016 (unguarded JS interop) stays in NoWarn because it accepts only a try/catch around each of 272 interop calls. The tests moved to bUnit 2.13.3, which drives the .NET 11 Virtualize component natively, behind a compatibility layer so the test sources stay as they are on master: Radzen.Blazor.Tests.TestContext derives from BunitContext and keeps RenderComponent, the ComponentParameter.CreateParameter overload and a synchronous DisposeComponents, extension methods keep SetParametersAndRender and ToMarkup, and global using aliases map TestContext, ComponentParameter and IRenderedFragment for every test namespace, so tests written against either bUnit version compile unchanged and merges from master carry no test churn. The real .NET 11 changes in the tests are a handful: EditContext.Validate is obsolete so the DataAnnotationValidator tests await ValidateAsync, AIChatService.TryQueueMessageAsync became virtual so the fake overrides it, xunit moved to 2.4.2 and its NotNull annotations make two Assert.Equal(float, float, int) calls name the precision argument and two Markdown update asserts check for null first, and CS8632 is silenced in the project because the annotations in test files without a nullable context are harmless. The chart tick label expectation follows the exact double-to-decimal conversion in .NET 11. Verified with the full suite on net11.0, the trimmed runtime gate and Playwright against the demo app for the components whose StateHasChanged calls were removed.
2026-11-09 14:16:17 +02:00
.NET 11 support added and .NET 8 support removed. Radzen.Blazor now targets net9.0, net10.0 and net11.0 with 11.*-* Components references, and the Sass, MoveCss and MinifyJs targets key on net11.0; the test, demo, API, tools and trimming projects, the Dockerfile images, the CI, deploy and NuGet workflows and the e2e docs moved to net11.0. The always-true NET6_0_OR_GREATER and NET8_0_OR_GREATER conditionals were collapsed. EditContext.Validate is obsolete in .NET 11, so RadzenTemplateForm, RadzenSteps and RadzenDataGrid.UpdateRow await ValidateAsync on net11.0, and the demo host dropped the obsolete UseWebAssemblyDebugging call with its inspectUri launch entries. The new .NET 11 analyzers are fixed rather than suppressed: CA1307 call sites pass StringComparison.Ordinal with the net11-only char overloads polyfilled for net9 and net10 in StringComparisonExtensions, CA1860 Any() calls compare Count or Length, CA2263 uses a GetJsonTypeInfo<T> helper that takes the generic GetTypeInfo overload on net11, and BL0012 removed seventeen StateHasChanged calls from private event handlers that ComponentBase already renders after. BL0016 (unguarded JS interop) stays in NoWarn because it accepts only a try/catch around each of 272 interop calls. The tests moved to bUnit 2.13.3, which drives the .NET 11 Virtualize component natively, behind a compatibility layer so the test sources stay as they are on master: Radzen.Blazor.Tests.TestContext derives from BunitContext and keeps RenderComponent, the ComponentParameter.CreateParameter overload and a synchronous DisposeComponents, extension methods keep SetParametersAndRender and ToMarkup, and global using aliases map TestContext, ComponentParameter and IRenderedFragment for every test namespace, so tests written against either bUnit version compile unchanged and merges from master carry no test churn. The real .NET 11 changes in the tests are a handful: EditContext.Validate is obsolete so the DataAnnotationValidator tests await ValidateAsync, AIChatService.TryQueueMessageAsync became virtual so the fake overrides it, xunit moved to 2.4.2 and its NotNull annotations make two Assert.Equal(float, float, int) calls name the precision argument and two Markdown update asserts check for null first, and CS8632 is silenced in the project because the annotations in test files without a nullable context are harmless. The chart tick label expectation follows the exact double-to-decimal conversion in .NET 11. Verified with the full suite on net11.0, the trimmed runtime gate and Playwright against the demo app for the components whose StateHasChanged calls were removed.
2026-11-09 14:16:17 +02:00

Trimming runtime gates

Two runtime gates back the static contract tests in Radzen.Blazor.Tests/TrimmingContractTests.cs. Both reference Radzen.Blazor.TrimTest.Models, a separate <IsTrimmable> assembly, so the trimmer strips model members that Radzen reads by reflection - the real reflection-over-T scenario.

1. Console gate (required, deterministic, browser-free)

Radzen.Blazor.TrimRuntimeTest instantiates the item-typed generic components with the trimmable model, then checks via reflection whether the trimmer preserved the model getters.

dotnet publish Radzen.Blazor.TrimRuntimeTest/Radzen.Blazor.TrimRuntimeTest.csproj \
    -c Release -r <rid> --self-contained -p:PublishTrimmed=true
./Radzen.Blazor.TrimRuntimeTest/bin/Release/net11.0/<rid>/publish/Radzen.Blazor.TrimRuntimeTest

Exit 1 today (getters trimmed). Exit 0 once the library annotates the item-typed component generics with [DynamicallyAccessedMembers(PublicProperties | PublicFields)].

2. WASM gate (faithful browser repro, optional)

Radzen.Blazor.TrimTest renders the components by string Property over the trimmable model and drives sort/filter/group in OnAfterRenderAsync, reporting done / error:<msg> in #trim-status.

dotnet publish Radzen.Blazor.TrimTest/Radzen.Blazor.TrimTest.csproj -c Release
dotnet tool install -g dotnet-serve
dotnet serve -d Radzen.Blazor.TrimTest/bin/Release/net11.0/publish/wwwroot -p 5050 &
cd e2e && npm install && npx playwright install chromium
TRIM_URL=http://localhost:5050 node trim-smoke.mjs

Exit 1 today (the drive throws over the trimmed model). Exit 0 once the DAM fix lands (rooting RadzenDataGrid<Order> preserves Order's members app-wide).