18.6 K PV/month
Hey Rick,
Lets try this again.
Please follow the instructions here:
To up-date the documentation here:
The docs should all be referencing ASP.NET Core version 2.2 now.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@hongzewangpa wrote:
I found if I move the services.Addxxx out of IdentityHostingStartupinto startup.cs, it is working.
//code piece moved:
services.AddDbContext<ApplicationDbContext>(options =>
options.UseSqlServer(
context.Configuration.GetConnectionString("DefaultConnection")));
services.AddDefaultIdentity<IdentityUser>()
.AddEntityFrameworkStores<ApplicationDbContext>();
See #12857

options.AllowAreas = true;
this setting doesn't work in ASP.NET Core 3.0
Any work around for this ?
AllowAreas is a compatibility switch. With 3.0 being a breaking change, Areas are "allowed" out of the box, so options.AllowAreas = true; can be dropped.
https://github.com/aspnet/AspNetCore.Docs/issues/14357#issuecomment-532385914
Documentation is not updated for .Net Core 3.0. I tried the section "Create full identity UI source". I had to add below line for services.AddIdentityServer() to work (ApplicationUser is my IdentityUser):
services.AddScoped
Most helpful comment