ASP. NET membership management without Visual Studio [translation]

See: http://joeon.net/archive/2007/05/25/ASP.NET-Membership-Admin-without-Visual-Studio.aspx

When using the default ASP. NET 2.0 membership (aspnetsqlmembershipprovider), you can use the Visual Studio tool or Frontpage Server Extension to modify configurations and add/delete users.
(Notes: ASP. NET configuration options are available when you use Visual Studio to develop a web site)

So how do I configure membership without using Visual Studio? The main steps are listed below:

For reference: The following operations expose some management capabilities, so you must be careful when performing the operations and perform the operations with a clear and correct purpose.

1. Create a virtual directory in IIS:
Virtual directory: Asp. netwebadminfiles
Physical path: C: \ WINDOWS \ Microsoft. NET \ framework \ v2.0.50727 \ ASP. netwebadminfiles

2. Modify the properties of the virtual directory and change ASP. NET to 2.0.
Note: If you run applications 1.1 and 2.0 on the same machine, you need to install a separate application pool for the site 2.0. Otherwise, the following error message will appear: "Application unavailable"

3. Remove anonymous access to the virtual directory

4. Then, you can use the following URL to connect to the console:
Http: // localhost/asp. netwebadminfiles/default. aspx? Applicationphysicalpath = xxx & applicationurl =/yyy

My example:
Http: // localhost/asp. netwebadminfiles/default. aspx? Applicationphysicalpath = c: \ Inetpub \ wwwroot \ MyApp \ & applicationurl =/MyApp

Note: The following is not recommended.
If you need to remotely connect to this console, Open c: \ windows \ Microsoft. net \ framework \ v2.0.50727 \ ASP. webadminpage under the netwebadminfiles \ app_code directory. CS file, comment out the following code:

If (! Application. Context. Request. islocal)
{
Securityexception = new securityexception (string) httpcontext. getglobalresourceobject (
"Globalresources", "webadmin_configurationislocalonly "));

Webadminpage. setcurrentexception (application. Context, securityexception );
Application. server. Transfer ("~ /Error. aspx ");
}

This console is still protected by Windows Integration authentication.

If the following error is reported when updating user information:
Failed to update database "C: \ Inetpub \ wwwroot \ MyApp \ app_data \ aspnetdb. MDF" because the database is read-only.
This is because the network_service account does not have the read and write permissions on this MDF file.