Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by .... ..... , an ibibo Master, at 5:33 AM on July 12, 2008

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by Raksha , an ibibo Master, at 9:53 AM on July 10, 2008

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.

Answered by Yash , an ibibo Master, at 9:52 AM on July 02, 2008

well, This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed.

Answered by Romi , an ibibo Master, at 8:26 PM on June 21, 2008

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by Madhurima , an ibibo Master, at 3:05 PM on June 18, 2008

hi there

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by Reeta K , an ibibo Master, at 7:49 PM on June 15, 2008

well Harshil, Creating permanent user accounts

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:

1.

Run aspnet_regsql from a DOS command prompt window.

This starts the ASP.NET SQL Server Setup wizard.

You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.

Use the ASP.NET SQL Server Setup wizard to create the user database.

In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed.

Answered by satyaiitk , an ibibo Master, at 6:11 PM on June 14, 2008

Permanent user accounts are disabled by default. After a Web Forms application is successfully deployed, the IIS server administrator can use the following procedure to set up permanent user accounts. This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by Anju Singh , an ibibo Master, at 8:07 PM on June 13, 2008

well, This procedure uses the default ASP.NET membership provider and data source assignment, although a note in the procedure describes a required change to the web.config file when you use a nondefault connection string.

StepsTo create permanent user accounts:
1.Run aspnet_regsql from a DOS command prompt window.
This starts the ASP.NET SQL Server Setup wizard.
You can enter Aspnet_regsql /? at the command line to obtain a list of optional parameters for SQL Server or SQL Server Express that you can use to bypass the wizard. If you are using a local SQL Server database, for example, you can enter aspnet_regsql -S (local) -E -A m, where -S (local) indicates that the server is local, -E indicates that the connection uses Windows Authentication, and -A m adds the membership feature.
2.Use the ASP.NET SQL Server Setup wizard to create the user database.
In the wizard, you can enter .\SQLEXPRESS as the server name. This is the default name for the local server as defined in the machine.config file. The wizard should give you a success message.
3.In a text editor, modify the web.config file in the virtual root directory for your deployed

Answered by Uttam , an ibibo Master, at 8:00 PM on June 13, 2008

Remember that you cannot open aspx page using file's system path such as file:///C:/... This is because .aspx pages needs to be processed by the asp.net runtime in order to generate the final HTML that is going to be served to the browser. The file system option means that Visual Studio will not create IIS virtual folder for you automatically and will use a small development web server to run your application. After you are done developing your web application you need to deploy it on IIS. I believe there are deployment tools in VS that helps you with this, but what I suggested you to do is to create a virtual folder in IIS, set up a web application for that folder and copy your files manually. After that you can view any *.aspx file through web browser.

Answered by A.R.Karthick , an ibibo Master, at 7:28 PM on June 13, 2008