Home/ Questions/Q 6229043
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T09:29:41+00:00

I asked this question over on the asp.net forums, and nobody seems to know

  • 0

I asked this question over on the asp.net forums, and nobody seems to know what i’m talking about. I’m not sure why that is, but I figured I’ll ask here to see if there is anyone with some insight.

Back when MVC2 was released, it included a sample AccountController that wrapped the built-in Membership and FormsAuthentication classes with testable interfaces and services. I read a lot about this, and it was considered a good thing because the Membership and FormsAuthentication classes were not easily testable.

Recently, I generated a new sample project with my up to date (SP1, MVC3, Tools Update, etc..) environment and I find that the AccountController is now much simpler. Gone are the Interfaces and MembershipService and FormsAuthenticationServices. The sample now calls the Membership and FormsAuthentication classes directly.

I’m wondering if anyone knows when this happened and why? Are the testable interfaces no longer considered correct? Was there a technical reason to change this?

The best I can figure is that this happened as a part of the change to remove a possible vulnerability when passing return url’s on the open url.

Any insight?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The Account Controller was changed with the MVC3 tools update (When they also included the use of jQuery via Nuget)

    • 0