When Microsoft will remove Razor Page Identity from MVC project template?

[TanvirArjel]

I am going to be hard on Microsoft and ASP.NET Core team regarding this issue.

When Microsoft released ASP.NET Core 2.1 with Razor Page Identity in MVC template, we are complaining about this because it does not make sense I am selecting a MVC template but getting Identity as Razor Page. Every time I had to do insane amount of work to convert those Razor Page Identity into MVC controller based Identity.

Surely this is one of the critical bugs or mis-designs Microsoft ASP.NET Core team have ever made. And more dangerous thing is that ASP.NET Core team is not giving any heed to this issue. They are just ignoring.

Actually it should have been:

1. For ASP.NET Core MVC Project, Identity will be generated in MVC
2. For ASP.NET Core Razor Page, Identity will be generated in Razor Page

This grave mistake has been done on ASP.NET Core 2.1 and now its ASP.NET Core 3.0 Preview 3 but not fixed yet!

Today I have generated an Angular app with Authentication, I have found that its Razor Page identity in Angular app too. Oh my God! In Angular app you are redirecting to Razor Page route for registration. How comical this thing is.

Till ASP.NET Core 2.0, Identity for MVC project was in MVC and it was working fantastic. Then why did you do this illogical changes which does not make any sense. Any explanation?

You already have MVC based Identity code in ASP.NET Core 2.0, then why are you not bringing those code into other versions as people are complaining about this.

You are saying you are making open source project but you not giving heed to the people's opinion then its not open source any way.

Regards
An angry Microsoft and ASP.NET Core Fan

[Ponant]

@TanvirArjel , It is hard to maintain an MVC and RP based template simultaneously so they had to make a choice.

[mikesheen]

@TanvirArjel Being open source doesn't mean accepting every pull request or making changes based on an issue.
The project maintainers reserve the right to do as they please - and business and technical reasons would weigh in heavily on decisions regarding changes.
I think it's unfair to challenge ASP.NET Core's open source "status" based on your opinions relating to an issue you have.
You're free to provide a pull request which addresses your issue - and if it meets the contribution guidelines and the ASP.NET Core teams vision for the product then I'm sure they will consider your pull request.
Being open source does not mean you have to accept every proposed change.

[blowdart]

As @Ponant has stated we have limited time and limited resources. Adding MVC identity scaffolding would more than double the time we take to make any chance to identity and that's not something we are willing to do.

We've ran surveys on this, taken feedback, attempted to contact customers to discuss it in greater detail, but when it's all compiled the majority of users don't have a problem with how it is right now, and thus we concentrate on features that have more customer demand.

Of course, as with everything else you are free to publish your own template, with a scaffolded MVC version of identity, but it is not something we are considering doing.

[TanvirArjel]

@blowdart, You are completely wrong that people are not complaining about this or not facing any problem. Please go to stack overflow see that how many questions has been asked related to this. Even new comer does not know what Razor Page Identity is! as they are already used to MVC. They become mad of searching the hidden Identity related code in the project. So your logic is pretty superfluous!

[TanvirArjel]

@blowdart Please take a look on it: https://stackoverflow.com/questions/56060589/where-are-are-identityusers-uploaded-to-the-database and see how Razor Page Identity is confusing people!