Is there a difference in the working between the Membership Provider of Webforms and Membership Provider of MVC 3?
相关问题
- Request.PathInfo issues and XSS attacks
- How to dynamically load partial view Via jquery aj
- Entity Framework throws exception - Network Relate
- Slow loading first page - ASP.NET MVC
- How does ASP.NET know which event to fire during a
相关文章
- “Dynamic operations can only be performed in homog
- Change color of bars depending on value in Highcha
- Forward request from servlet to jsp
- How to get server path of physical path ?
- superclass mismatch for class CommentsController (
- How to find the exceptions / errors when TryUpdate
- ASP.Net MVC 3: optgroup support in Html.DropDownLi
- A circular reference was detected while serializin
No, MVC is just a design pattern that Microsoft has utilized. So, you can use membership in all ASP.Net projects.
This is evident even in the namespace: System.Web.Security
No.
System.Web.Security
namespaceSystem.Web.UI
namespaceSystem.Web.Mvc
namespaceTherefore, there are no dependencies. In other words, you'll be making the same membership calls with the same membership objects in an MVC application as you would in a WebForms application.