ASP.NET Core 6 Identity - Scaffolding Identity problem

AlexD 6

I am following the tutorial on learn.microsoft.com (Authentication, ASP.NET Core 6.0).

I create ASP.NET Core Web App with individual user accounts and update a database. So far everything works. Then I scaffold the identity.

Then I Scaffold Register, Login, LogOut, and RegisterConfirmation according to the tutorial. Here I select "Login", "Logout" etc., select ApplicationDbContext as Data Context Class and click add.

The problem is that in program.cs it generates additional connection string (so there are two of them), as well as dublicates of builder.Services.AddDbContext... and builder.Services.AddDefaultIdentity...

Everything works fine if I delete (comment out) this newly generated lines but I do not know what am I doing wrong.

SurferOnWww 1,906 Reputation points

2022-06-28T01:02:04.337+00:00
Then I Scaffold Register, Login, LogOut, and RegisterConfirmation according to the tutorial. Here I select "Login", "Logout" etc., select ApplicationDbContext as Data Context Class and click add.

Can you tell how you did it? What are the settings of Data Context Class and User Class?

In my environment the builder.Services.AddDbContext... and builder.Services.AddDefaultIdentity... in the Program.cs generated by the Visual Studio 2022 are as follows:

var connectionString = builder.Configuration.GetConnectionString("DefaultConnection"); builder.Services.AddDbContext<ApplicationDbContext>(options => options.UseSqlServer(connectionString)); builder.Services.AddDefaultIdentity<IdentityUser>(options => options.SignIn.RequireConfirmedAccount = true) .AddEntityFrameworkStores<ApplicationDbContext>();

Are they the same in your environment? The duplications are also the same?
FriQenstein 136 Reputation points

2022-07-22T13:45:39.73+00:00

This is still an issue as of July 22, 2022. In fact, it has gotten worse.
When I attempt to Scaffold the Register page, as OP mentioned, it now creates an additional Data directory in the Areas->Identity directories.

It never did this in the past, especially considering I already have an ApplicationDbContext.cs and an existing Data directory in the standard structure of the solution... as generated by VS2022.

Simply deleting this directory also does not fix the issue, because it branches out to other errors that you must hunt down, which takes more time.

Having to track down these errors wastes time and creates frustration. This completely negates the basic principle of not wasting time while coding.

I am attaching snippets of BEFORE and AFTER the scaffolding to show what it was and what it creates.

Regards.
FriQenstein 136 Reputation points

2022-07-22T15:01:00.577+00:00

An update, because for some reason this forum will not let me EDIT a post....

When I scaffolded the Register page, and got the errors mentioned above, it not only created those duplicates, but it also decided to register everything based on IdentityUser instead of Employee, which is what I have already set everything to use PRIOR to scaffolding the Register page.

Why is it deciding to completely ignore my existing configuration?
i.e. in the Register.cshtml.cs file, everything is registered as IdentityUser instead of what I changed it to at the very beginning of my project creation, Employee.
The ENTIRE file is permeated with IdentityUser references instead of what is actually being used and already setup in the Program.cs file.
FriQenstein 136 Reputation points

2022-08-16T19:02:25.977+00:00

As of 16-Aug-2022, this appears to be fixed.

I am not certain if it was in the patches that were released last week, but I went back and retried all of the above mentioned processes and it is now generating the scaffolded items correctly; no additional entries, no extra directories, and no overwriting referenced classes with IdentityUser as it did before.

Thank you for fixing this.

1 answer

Zhi Lv - MSFT 32,011 Reputation points Microsoft Vendor

2022-06-28T01:59:06.617+00:00

Hi @AlexD ,

The problem is that in program.cs it generates additional connection string (so there are two of them), as well as dublicates of builder.Services.AddDbContext... and builder.Services.AddDefaultIdentity...

Everything works fine if I delete (comment out) this newly generated lines but I do not know what am I doing wrong.

I could reproduce the problem on Asp.net 6 application and use VS 2022. This error appeared recently and only on Asp.net 6, it does not happen on the Asp.Net 5 and the previous version. And I found this issue has been feedback to the Asp.net development team, you can check it and wait the response.

As a temporary solution, as you said you can delete or comment out the duplicate lines. Or you can create an Asp.net 5 or previous version application.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards,
Dillion
Please sign in to rate this answer.
David Thielen 2,256 Reputation points

2023-03-25T00:27:48.41+00:00

@Zhi Lv - MSFT I am trying the same thing and hitting one of the above problems - how can I have the Identity info in one database and my application use a different database?
Sign in to comment