Skip to content
The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles. And is now packaged up into an MVC 3 Portable Area.
JavaScript C# ASP
Find file
Pull request Compare This branch is 9 commits ahead, 61 commits behind troygoode:master.
Latest commit f96ec63 Jun 14, 2011 @fretje Merge pull request #1 from JamesKovacs/master
Added Creation of New Users to UserAdministration
Failed to load latest commit information.
MvcMembership.Tests Added another overload for ChangePassword that takes old password. Sep 1, 2010
SampleWebsite Added ability to create new users from within user administration. May 27, 2011
UserAdministrationArea.Tests Added ability to create new users from within user administration. May 27, 2011
packages Changed it into an MVC 3 Portable Area May 9, 2011
.gitignore Updated .gitignore to ignore *.mdf and *.ldf files. May 27, 2011
Build.Debug.bat Upgaded Build.Debug.bat and Build.Release.bat to use .NET 4.0 version… Sep 1, 2010
LICENSE.txt Upgraded projects to .Net 4.0. Upgrade test suites to xUnit 1.6.1. Ad… Jul 29, 2010
Test.Console.bat Added password change/reset capabilities to MvcMembership facade. Sep 1, 2010
Test.Gui.bat Added password change/reset capabilities to MvcMembership facade (for… Sep 1, 2010
Tests.xunit Changed it into an MVC 3 Portable Area May 8, 2011


What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of three things:

  1. A library that provides testable interfaces for administering users & roles and concrete implementations of those interfaces that wrap the built-in Asp.Net Membership & Roles providers.
  2. An MVC 3 Portable Area which contains the controllers, models and views needed to administer users & roles.
  3. A sample website which consumes the Portable Area.

Out of the box, the starter kit gives you the following features:

  • List of Users
  • List of Roles
  • User Account Info
  • Change Email Address
  • Change a User's Roles

Some screenshots of the UI are available on my blog. While that blog post announced an older version of the project, the screenshots still accurately reflect the current version.

How do I use it?

Note As of now this uses MVC 3 with razor views, so your project needs to be MVC 3. It uses MVCContrib which in turn uses MVC Futures.

Note: If you have an ASP.Net MVC 1.0 project, you can convert it to ASP.NET MVC 2.0 following these instructions:

Add References to MvcMembership.dll

  1. After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
  2. Add a reference from the target site to UserAdministrationArea.dll.


  1. The UserAdministrationArea dll depends on MvcMembership.dll (and MvcContrib).
  2. The MvcMembership.dll depends upon the PagedList.dll assembly, which you can find packaged with the MvcMembership source code, in the bin of the SampleWebsite, or downloaded from GitHub.

Configure Membership & Roles Providers

  1. Make sure you've configured your web.config properly for Membership and Roles. If you aren't sure of how to do this, take a look at the first two articles in this series by Scott Mitchell at 4GuysFromRolla. Hint: Use C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe, and then grant your web site's application pool user access to the database.
  2. Change the "Administrator" value of the Authorize attribute in the UserAdministrationController.cs file (line 11) to whatever role you want to require a user to have in order to view/use the User Administration area. If a user tries to navigate to the User Administration area without this role, they will be redirected to the login page (even if they're already logged in).
  3. Configure the node in your web.config file with the appropriate SMTP settings so that emails can be sent for password change/reset events.
  4. Make sure the user identity of your application pool has sufficient permissions to the aspnet database.
  5. Add the following code to your global.asax to keep the membership system updated with each user's last activity date:
    protected void Application_AuthenticateRequest()
        if(HttpContext.Current.User != null)

Integrate the Views

  1. Add the following to the application_Start method of you Global.asax.cs:
  2. The starter kit relies on your site having a site master page (_Layout.cshtml) and a _ViewStart.chtml. A default ASP.Net MVC razor site is generated with a _layout.cshtml in the \Views\Shared folder and a _ViewStart.chtml in the \Views folder. That master page needs to have a secion "Headsection" rendered in the "head" of the page:
            <!-- links to stylesheets and javascript go here --!>
            @RenderSection("HeadSection", false)
  3. That master page and any contained views will need to specify their Area when generating links, even views not in an area (so the default master page would requires fixes). If the link is not to a page in an area (typical), then an Area of "" (empty string) should be specified. For instance, a call to generate a link to the homepage should look like so: Html.ActionLink("Home", "Index", "Home", new {Area = ""}, new {})
  4. Add a User Administration link to your master page (change "Administrator" to whatever role you want to use):
    <% if (Roles.IsUserInRole("Administrator")){ %>
        <li><%= Html.ActionLink("User Administration", "Index", "UserAdministration", new { Area = "UserAdministration" }, new { })%></li>
    <% } %>
  5. If you don't have an "Areas" folder, create one, and copy the web.config from the "Views" folder into it. Otherwise make sure there is a web.config in there (this is needed for Portable Areas).
Something went wrong with that request. Please try again.