You blew my mind with how good you explain things, I get c# in school and Im always lacking behind because the teacher goes over everything so quickly!
I'm new to this, but was able to get it to work...thank you so much! I look forward to watching more of the videos in your series (and watching all of the adds...to help support a good content creator)
Thanks a lot for the course, its amazing. Please tell me why in the CreateRole view is not necessary specify that the asp-controller is Administration but is enough specify asp-action="CreateRole"
Hi , I'm encountering the following error when following your solution: An unhandled exception occurred while processing the request. InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Identity.RoleManager`1[Microsoft.AspNetCore.Identity.IdentityRole]' while attempting to activate 'Hybrid2.Controllers.AdministrationController'. Please assist
services.AddDefaultIdentity(options => options.SignIn.RequireConfirmedAccount = true) .AddRoles() // just add this line into your startup and i think your problem is solved .AddEntityFrameworkStores();
I too have the problem Dieter Munnik is experiencing. I have added custom fields to AspNetUsers using an ApplicationUser class inheriting from IdentityUser as in your other videos. In Startup.cs I have added .AddRoles() but I then get errors referring to ViewData["Title"] and RoleName usage in the Razor View. After commenting these out the View opens but is of no use to add records of course. But my other controller actions using standard models to open CRUD Razor Views all have errors referring to the CreateRoleViewModel requiring a primary key. Any advice?
Extra info - it appears IdentityRole is missing a using directive or an assembly reference. Any help on where to add these would be appreciated especially as I find your examples the best on the web.