Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASP.NET Core Identity UI now uses "static web assets" feature #14959

Closed
analogrelay opened this issue Oct 4, 2019 · 2 comments · Fixed by #15044 or #15467
Closed

ASP.NET Core Identity UI now uses "static web assets" feature #14959

analogrelay opened this issue Oct 4, 2019 · 2 comments · Fixed by #15044 or #15467
Assignees
Labels
breaking-change Indicates a .NET Core breaking change
Milestone

Comments

@analogrelay
Copy link

ASP.NET Core Identity UI now uses "static web assets" feature

In ASP.NET Core 3.0 we've moved Identity UI to use the new static web assets feature introduced in 3.0. As part of this move there are a few API breaking changes to note.

Bootstrap4 is the default UI framework for Identity UI. (Bootstrap 3 has reached end of life and you should consider migrating to a supported version).

Selecting the framework is done by using the IdentityUIFrameworkVersion property in your project file.

Version introduced

3.0

Old behavior

The default UI framework for Identity UI was Bootstrap 3.0. The UI framework could be configured using a parameter to the .AddIdentityUI() call in Startup.ConfigureServices.

New behavior

The default UI framework for Identity UI is now Bootstrap 4.0. The UI framework must be configured in your csproj file, instead of the .AddIdentityUI() call, by adding the following MSBuild property to your csproj file:

<IdentityUIFrameworkVersion>Bootstrap3</IdentityUIFrameworkVersion>

Reason for change

We updated the default UI framework to reflect a new version of Bootstrap. Because we use the new static web assets feature, the UI framework configuration moved to MSBuild since the decision on which framework to embed is a build-time decision not a run-time decision.

Recommended action

Review your site UI to ensure the new Bootstrap 4.0 components are compatible. If necessary, use the IdentityUIFrameworkVersion MSBuild property to revert to 3.0.

Category

  • ASP.NET Core

Affected APIs

IdentityBuilderUIExtensions.AddDefaultUI()


Issue metadata

  • Issue type: breaking-change
@serpent5
Copy link
Contributor

FYI, the explanation for this announcement discusses AddIdentityUI, but the affected API is AddDefaultUI.

@scottaddie
Copy link
Member

@serpent5 Thank you for letting me know. Looking at this right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
5 participants