One question I’ve seen asked a few times by people in the NG is “how do I manage ASP.NET Membership, Role Management database in non-ASP.NET application/context”. This blog entry walks you though a few simple steps on how to-do this.
Quick Review: What are the new ASP.NET 2.0 membership & role management Services?
The ASP.NET version 2.0 membership feature provides secure credential storage for application users. It also provides a membership API that simplifies the task of validating user credentials when used with forms authentication. Membership providers abstract the underlying store used to maintain user credentials. ASP.NET 2.0 includes the following providers:
Here I’ll concentrate on the SQL Server provider since it is used mostly for FormsAuthentication based ASP.NET web applications. By default ASP.NET SqlServer membership/role provider use SQL Express database file(aspnetdb.mdf) as the storage, however, you can easily change it to your own SQL Server database in a certain server instance. What you need to do is simply override/customize the membership setting in the application web.config file. E.g.
<add name="MySqlConnection" connectionString="Data Source=MySqlServer;Initial Catalog=aspnetdb;Integrated Security=SSPI;" />
<membership defaultProvider="SqlProvider" userIsOnlineTimeWindow="15">
How do I manage ASP.NET Membership, Role Management database in non-ASP.NET application/context?
Sometimes you may want to manage the SQL Server membership/role database in non-ASP.NET application/context(such as winform or console application) for some certain reasons:
l Need to add some initial data(users/roles) in the setup program of the application
l Want to create a non-ASP.NET application to manage the membershp/role database offline
l Create a non-ASP.NET application that can help create a membership/role database as template(used in other ASP.NET application).
Well, this is certainly supported by the ASP.NET 2.0 membership/role(also some other) providers and you can do this follow these steps:
1. add the connectionstring to your SQL Server membershp & role provider database into the winform/console application’s App.confg file. e.g.
<add name="ProfileAppDB" connectionString="Data Source=localhost;Initial Catalog=ProfileAppDB;Integrated Security=True"
2. copy the membershp & role setting fragment from your ASP.NET application into the winform/console application’s App.config file. e.g.
type="System.Web.Security.SqlMembershipProvider, System.Web, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="ProfileAppDB" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression="" />
<roleManager defaultProvider="NewAspNetSqlRoleProvider" enabled="true">
<add name="NewAspNetSqlRoleProvider" connectionStringName="ProfileAppDB" applicationName="/"
type="System.Web.Security.SqlRoleProvider, System.Web, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
3. Use the built-in façade classes to manage the membership users and roles. E.g.
/// Dump the users and associated roles from membership database
private void Dump_Users()
MembershipUserCollection users = Membership.GetAllUsers();
txtOutput.Text += "\r\n=========Total User Count: " + users.Count + "==========";
txtOutput.Text += "\r\n\r\n";
foreach (MembershipUser user in users)
txtOutput.Text += "\r\n\tUsername: " +user.UserName + "\t, Creation Time: " + user.CreationDate;
string roles = Roles.GetRolesForUser(user.UserName);
txtOutput.Text += "\r\n Roles: " + string.Join(", ",roles);
/// create a new membership user
private void btnCreate_Click(object sender, EventArgs e)
MembershipUser user = Membership.CreateUser(
txtUsername.Text + "@test.org",
"who am i?",
txtUsername.Text, true, null, out ret);
Winform App UI
Additional common questions here:
Q1: What shall I do if I can not add an App.config file for the program at design-time(used in a setup program)? How can I provide the connectionstring and membershp provider configuration info?
A1: You can dynamically create an app.exe.config file for your program in the initialization/startup time. Use built-in API to get the runtime main exe path and create a config file on the fly, then write the configuration info into it(load from resource or any other place).
Q2: How can I programmatically install the membership & role services into an empty SQL Server database(in a certain server instance)?
A2: You have two options here:
ü Call the aspnet_regsql.exe utility the install the services in your database
ü Directly use the System.Web.Management.SqlServices class to install the services into your SQL Server database
Q3: How can I do programmatically create a SQL Express database file which has the membershp & role services installed
A3: Well, you can find that ASP.NET Sqlmembership provider will automatically create a mdf file if you’ve configured to use the default SQL Express connectionstring. Thus, you can inspect it through reflector and find out the SqlConnectionHelper.CreateMdfFile method which include the complete code for creating such as database file on the fly
Hope this helps.