ProtectedBrowserStorage feature moved to ASP.NET Core shared framework

[pranavkm]

ProtectedBrowserStorage feature moved to ASP.NET Core shared framework

As part of the 5.0-rc2 release, the ProtectedBrowserStorage feature has been moved to the ASP.NET Core shared framework.

Version introduced

5.0-rc2

Old behavior

In 5.0-preview8, the feature was available as a part of the Microsoft.AspNetCore.Components.Web.Extensions package but was only usable in Blazor WebAssembly. In 5.0-rc1, the feature was available as part of the Microsoft.AspNetCore.Components.ProtectedBrowserStorage package which references the Microsoft.AspNetCore.App shared framework.

New behavior

As part of 5.0-rc2, a package reference is no longer needed to reference and use the feature.

Reason for change

Better fit for the user experience we expect.

Recommended action

When upgrading from 5.0-rc1

• Remove the Microsoft.AspNetCore.Components.ProtectedBrowserStorage package reference
• Replace the Microsoft.AspNetCore.Components.ProtectedBrowserStorage using with Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
• Remove the call to AddProtectedBrowserStorage from your Startup.

When upgrading from 5.0-preview8

• Remove the Microsoft.AspNetCore.Components.Web.Extensions package reference
• Replace the Microsoft.AspNetCore.Components.Web.Extensions using with Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
• Remove the call to AddProtectedBrowserStorage from your Startup.

Category

ASP.NET

Affected APIs

• Microsoft.AspNetCore.Components.ProtectedBrowserStorage
• Microsoft.Extensions.DependencyInjection.ProtectedBrowserStorageServiceCollectionExtensions.AddProtectedBrowserStorage

---

Issue metadata

• Issue type: breaking-change