Home/ Questions/Q 6329177
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T17:36:17+00:00

I’m learning ASP.NET MVC 3 to build a web application. I’ve followed a couple

  • 0

I’m learning ASP.NET MVC 3 to build a web application. I’ve followed a couple tutorials teaching the Entity framework, Razor, MVC, etc. One thing I can’t find much about though is how to do authentication and authorization. In the tutorials I can find, it basically goes

Create an “Internet Application” project. The authorization system is already there so you don’t need any code. Now use an ASP.NET settings panel to set up user roles and slap [Authorize] everywhere.

I understand the system it starts you off with is called ASP.NET Membership. Is it common to just stick with that for your authorization?

I’ve been using Code First to do models and databases — is there a way I can create my own user models, have ASP.NET create the database, and use that for membership? How tough is it to customize user models (for example, if I want some user roles to have some information stored with their membership, but not others)?

Are there any tutorials that go through ASP.NET Membership in detail rather than just starting with whatever the project template spits out? For example, implementing it in an empty project?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It depends on the needs of your application. You will find the provided model has some limitations, but if you only need basic user/role management then it might suffice. Personally, I’ve always found it a bit too inflexible for my liking, but if it does what you need for the application your building, don’t waste your time reinventing it.

    Hope this helps.

    • 0