Tags: Furynation/aspnetcore
Tags
Update dependencies from https://github.com/dotnet/efcore build 20210… …202.2 (dotnet#29868) [release/6.0-preview1] Update dependencies from dotnet/efcore
[Blazor] Update template to pass in attribute as boolean (dotnet#28285) Description We introduced a public property as part of dotnet#27907 to enable users to opt-in. Turns out that this caused issues since we didn't update the target pack. As a result, the Razor compiler treats this new property as a regular HTML attribute (of type string) instead of as a boolean. In turn this causes the template to error at runtime when the application starts. Customer Impact Customers using 5.0.1 won't be able to create and run new blazor apps out of the box. They can fix the template code by preceding the true value in the attribute with @ to force the compiler to interpret it as C#. (Which is the same fix we are applying). Regression? Yes, 5.0.0. Users were able to create new blazor templates without this issue. Risk Low. We've manually validated the fix against a new project from a 5.0.1 template.
[release/2.1] Update korebuild to fix signcheck errors (dotnet#28005) * Update korebuild to fix signcheck errors
Update dependencies from https://github.com/dotnet/efcore build 20201… …110.2 (dotnet#27689) [release/3.1] Update dependencies from dotnet/efcore
[release/5.0] Update dependencies from dotnet/efcore (dotnet#27189) [release/5.0] Update dependencies from dotnet/efcore - Quarantine flaky test
PreviousNext