MvcMembership Wiki & Documentation Rss Feed

Updated Wiki: Home

TroyGoode — Tue, 05 Oct 2010 14:08:07 GMT

Source Code Has Moved!

For installation instructions and other information about how to use the starter kit, please visit our GitHub page:

Source Code & Instructions on GitHub:
http://github.com/TroyGoode/MembershipStarterKit

Updated Wiki: Home

TroyGoode — Thu, 29 Jul 2010 15:13:33 GMT

Source Code Has Moved!

ASP.Net MVC Membership Starter Kit

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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.

Screenshots:
http://www.squaredroot.com/2009/08/07/mvcmembership-release-1-0/

Updated Wiki: Home

TroyGoode — Thu, 24 Jun 2010 23:31:36 GMT

ASP.Net MVC Membership Starter Kit

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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

Source Code Has Moved!

Updated Wiki: Home

TroyGoode — Thu, 24 Jun 2010 23:31:03 GMT

ASP.Net MVC Membership Starter Kit

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Source Code Has Moved!

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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

Updated Wiki: Home

TroyGoode — Thu, 24 Jun 2010 22:26:19 GMT

What happened to the ASP.Net MVC Membership Starter Kit?

It is still alive, but has found a new home on GitHub:

http://github.com/TroyGoode/MembershipStarterKit

Updated Wiki: Home

TroyGoode — Thu, 24 Jun 2010 22:26:08 GMT

What happened to the ASP.Net MVC Membership Starter Kit?

It is still alive, but has found a new home on GitHub:

http://github.com/TroyGoode/MembershipStarterKit

Updated Wiki: Home

TroyGoode — Sun, 09 Aug 2009 15:28:33 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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
Screenshots available on my blog

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
Copy the MvcMembership folder from the SampleWebsite's Content folder to your app's Content folder.
Run through the various .cs files and the views and change the namespaces from SampleWebsite.* to whatever is appropriate for your application.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

Well, the last release was for Preview 5, so at the very least the project has been updated for Beta and finally Release. Moreover, the project has been completely rewritten from scratch – a major undertaking that was the primary cause of the long delay between releases. Why the rewrite? Two reasons:

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

Alright, so that was basically the long-winded spiel to prepare you for the bad news: the project regressed from a functionality perspective. During the course of the rewrite things some things didn’t make it in – chief among them is the OpenID integration. I encourage everyone to take a look at the Maarten Balliauw (an MvcMembership contributor) blog post on authenticating via RPX in MVC.

What comes next?

The primary motivator for me getting off my but after nearly a year and finishing up this release is my desire to convert it to an “area” for use in MVC 2. Packaging reusable components like this has been a sore spot for the current MVC framework and I’m glad to see the blue badges are going to provide a common solution. Along with that I’ll likely try to add RPX authentication ala Maarten’s post.

Updated Wiki: Home

TroyGoode — Fri, 07 Aug 2009 04:01:50 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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
Screenshots available on my blog

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

What comes next?

Updated Wiki: Home

TroyGoode — Fri, 07 Aug 2009 04:01:17 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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
Screenshots available on my blog

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

What comes next?

Updated Wiki: Home

TroyGoode — Fri, 07 Aug 2009 04:00:34 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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
Screenshots available on my blog

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

What comes next?

Updated Wiki: Home

TroyGoode — Fri, 07 Aug 2009 04:00:07 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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
Screenshots available on my blog

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

What comes next?

Updated Wiki: Home

TroyGoode — Fri, 07 Aug 2009 03:57:58 GMT

Project Description

The starter kit provides the Asp.Net MVC controllers, models, and views needed to administer users & roles.

Download

What is the Asp.Net MVC Membership Starter Kit?

The starter kit currently consists of two things:

A sample website containing the controllers, models, and views needed to administer users & roles.
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.

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

How do I use it?

In Asp.Net MVC 1 there isn’t a great story for packaging & sharing controllers, views, and other resources so we’ll need to follow a few manual steps:

After getting the source code build it using your preferred IDE or using the included Build.Debug.bat or Build.Release.bat batch files.
Grab the MvcMembership.dll assembly and place it wherever you’re including external libraries in your project. Add a reference to the assembly to your Asp.Net MVC application.
Copy the UserAdministrationController.cs file from the SampleWebsite’s Controllers directory to your app’s Controllers directory.
Copy the ISmtpClient.cs file, SmtpClientProxy.cs file, and UserAdministration folder from the SampleWebsite’s Models folder to your app’s Models folder.
Copy the UserAdministration folder from the SampleWebsite’s Views folder to your app’s Views folder.
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.
Finally, 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(User != null)
        Membership.GetUser(true);
}

What is new since the last release?

The first release of the Starter Kit was for Preview 2 of the MVC framework. A lot changed between Preview 2 and Release – A LOT. A lot of the features of the first starter kit were rolled into the OTOB experience (such as login and registration), so I shifted the scope of the project more squarely into the realm of user & role administration. Unfortunately all of these major changes took a toll on the source – I was no longer happy working in the source as it was written for many reasons and thus wanted a rewrite. One of those reasons was…
Previous releases had no (as in zero, less than one, nada) unit tests. This became increasingly unacceptable to me and trying to add unit tests after-the-fact was a nightmare. Instead I rewrote the project using TDD.

What comes next?

Updated Wiki: Home

TroyGoode — Wed, 02 Jul 2008 04:01:05 GMT

Project Description

This project aims to provide you with a basic MVC website from which you can build up your own MVC application without having to implement Login/Logout, Registration, and User Administration manually.

Introduction

One of my very first blog posts (and most definitely my most popular so far) revolved around how to integrate the MVC Framework with ASP.Net membership and forms authentication. It has remained popular to this day, but unfortunately the Preview 2 release of the MVC framework has caused much of the code I released in that article to no longer function correctly.

Even before the release of Preview 2, I had been planning to extend the samples I was providing to offer more useful features. I don't know about you, but nearly every website I ever create with ASP.Net requires some kind of security/membership system. My preference is to use the built-in system when possible (except for the horrible Profiles sub-system). This means creating login, logout, & registration functionality every time, as well as creating administrative screens for managing the users that enter your system.

WebForms provides some controls to help with the login and registration process, but user administration has always been delegated to either (a) the built-in tool that runs separately and doesn't work remotely or (b) rolling your own solution. The development of the MVC framework seems to me like a good time to resolve this scenario and provide the community with an array of pre-built tools to help boot-strap projects so that we can stop working on infrastructure and start working on the heart of the individual application.

With that in mind I have created this CodePlex project: the ASP.Net MVC Membership Starter Kit. It currently provides controllers and views for all of the common authentication and user administration needs, including:

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

A big thanks goes out to Rob Conery, as I borrowed his recent Authentication Filters and included those, along with my recently released Error Handling Filters.

To see some screenshots of the starter kit, visit my original announcement of the project.

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with or have any relation to MvcContrib?
A: No. MvcContrib is a great project that aims to feature extras like alternate routing, view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Originally the goal was none, other than the ASP.Net Membership system. In an effort to provide more login options out-of-the-box we are now utilizing Andrew Arnott & company's DotNetOpenId library. In a later release we hope to break OpenID and WindowsLive integration out into separate modules that you can choose to use or discard.

Q: Who is responsible for this?
A: The contributers are:

Myself (Troy Goode) - I started the project shortly after Preview 2 came out in response to the popularity of my earlier MVC Authentication articles.
Maarten Balliauw - Maarten joined me quickly after the first release and has contributed much to the project including all of the component controllers, Windows Live integration, and the basic password recovery features.
Greg Beamer - Greg joined us in late June to help improve the password recovery experience.

Please contact me if you'd like to help!

UPDATED WIKI: Home

TroyGoode — Sat, 26 Apr 2008 17:42:03 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only myself (Troy Goode) and Maarten Balliauw, but I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!

UPDATED WIKI: Home

TroyGoode — Fri, 11 Apr 2008 05:17:20 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

What's Next?

There are a few features missing that I would like to include in the very short term. Primarily these are features for end-users, like Change Password and Forgot My Password (both of which are currently available on the administration side). Beyond that, visual cleanup of the forms (and separation of the style sheets) as well as a bit of AJAX-ification of the forms would be nice. If you use the starter kit and have suggestions or criticisms, please post to the Discussions forum!

UPDATED WIKI: Home

TroyGoode — Fri, 11 Apr 2008 05:16:49 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only myself and Maarten Balliauw, but I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!

What's Next?

UPDATED WIKI: Home

TroyGoode — Wed, 02 Apr 2008 22:44:34 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only me, but I'd like that to change! I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!

What's Next?

UPDATED WIKI: Home

TroyGoode — Wed, 02 Apr 2008 22:36:01 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only me, but I'd like that to change! I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!

What's Next?

UPDATED WIKI: Home

TroyGoode — Wed, 02 Apr 2008 22:34:28 GMT

Project Description

Introduction

One of my very first blog posts (and most definitely my most popular so far) revolved around how to integrate ASP.Net membership and forms authentication into the ASP.Net MVC framework which had just been released in it's December CTP flavor. It has remained popular to this day, but unfortunately the Preview 2 release of the MVC framework has caused much of the code I released in that article to no longer function correctly.

Even before the release of Preview 2, I had been planning to extend the samples I was providing to offer more useful features. I don't know about you, but nearly every website I ever create with ASP.Net requires some kind of security/membership system. My preference is to use the built-in system when possible (except for the horrible Profiles sub-system). This means creating login, logout, & registration functionality every time, as well as creating administrative screens for managing the users that enter your system.

WebForms provides some controls to help with the login and registration process, but user administration has always been delegated to either (a) the built-in tool that runs separately and doesn't work remotely or (b) rolling your own solution. The development of the MVC framework seems to me like a good time to resolve this scenario and provide the community with an array of pre-built tools to help boot-strap projects so that we can stop working on infrastructure and start working on the heart of the individual application.

With that in mind I have created this CodePlex project: the ASP.Net MVC Membership Starter Kit. It currently provides controllers and views for all of the common authentication and user administration needs, including:

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only me, but I'd like that to change! I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!

What's Next?

UPDATED WIKI: Home

TroyGoode — Wed, 02 Apr 2008 22:30:33 GMT

Project Description

Introduction

Login/Logout
Registration
List of Registered Users
User Details / Administration
Role Management

NSFAQ (Not-So Frequently Asked Questions)

Q: Does this compete with MvcContrib?
A: No. MvcContrib is a great project that aims to features like alternate routing and view engines, and IoC integration. This project is simply a starter kit to help get membership-based applications off the ground a little quicker. There is no reason you could not use both projects together.

Q: What dependencies does using this starter kit saddle me with?
A: Ideally, none, other than the ASP.Net Membership API. Every measure will be taken to avoid using third party libraries, be it JavaScript or .Net. We will strive to separate the code and rely on default settings as much as possible to make it easy for you to customize your installation without anything in the starter kit getting in the way.

Q: Who is responsible for this?
A: Currently, only me, but I'd like that to change! I'm keenly interested in finding a few other developers that would like to contribute to enhancing the starter kit. Please contact me if you'd like to help!