The ASPNETDB.MDF file is added to your project and is in the App_Data folder.<\/p>\n\n\n\n
*Note \u2013 You may need to run \u201cASP.NET Configuration\u201d and refresh before the file will show up. You may also need to create a role and\/or username. Roles are created when \u201cASP.NET Configuration\u201d is run. You can register \/ creates a user account by running Register.ASPX in Visual Studio. It\u2019s under the \u201cAccount\u201d folder. <\/strong><\/p>\n\n\n\n Some people have problems when trying to upload ASPNETDB.MDF file to their server and getting it to work properly, especially with shared hosting. Since the schema and data are so useful in the ASPNETDB.MDF file we\u2019ll move it over to our SQL Server database.<\/p>\n\n\n\n Start by choosing the ASP.NET Web Site template in Visual Studio.<\/p>\n\n\n\n <\/p>\n\n\n\n *To see the ASPNETDB.MDF file in your solution explorer, database explorer, or server explorer you may have to first run, \u201cASP.NET Configuration.\u201d<\/strong>\u00a0To do this, click ASP.NET Configuration in your Visual Studio menu under Websites > ASP.NET Configuration.\u00a0 Then refresh.<\/p>\n\n\n\n After running ASP.NET Configuration in Visual Studio in this screen will show in the browser. This is the ASP.net Web Site Administration Tool and is where Roles and Access Rules are managed.<\/p>\n\n\n\n <\/p>\n\n\n\n Next right click the ASPNETDB.MDF file in your database explorer, server explorer, Solution Explorer. Select the option \u201cPublish to Provider.\u201d This creates a SQL script we can use in our SQL Server Management studio to recreate our database.<\/p>\n\n\n\n *Note – This is done differently depending on the version of Visual Studio used. Below I will show a couple of ways.<\/p>\n\n\n\n Below is via \u201cDatabase Explorer\u201d in an\u00a0express version<\/em>\u00a0of Visual Studio.<\/p>\n\n\n\n <\/p>\n\n\n\n In a full version of Visual Studio, \u00a0go under the \u201cApp_Data\u201d folder, right click on the ASPNETDB.MDF file and click \u201cInclude In Project.\u201d<\/p>\n\n\n\n <\/p>\n\n\n\n The icon for the\u00a0ASPNETDB.MDF should turn a yellow\/golden color. Double click the file. \u00a0That should open the \u201cServer Explorer,\u201d where you can then right click the ASPNET.MDF file that is in the \u201cServer Explorer,\u201d select the option \u201cPublish to Provider.\u201d<\/p>\n\n\n\n <\/p>\n\n\n\n After you click \u201cPublish to Provider,\u201d a new window will open, \u201cWelcome to the Database Publishing Wizard.\u201d<\/p>\n\n\n\n Select the ASPNET.MDF file and click next. Make sure, \u201cScript all objects in the selected database\u201d is checked.<\/p>\n\n\n\n <\/p>\n\n\n\n Now select the destination of the output for the script that will be created, and click next. Make note of where you are saving your file.<\/p>\n\n\n\n Select publishing options\u2026 Click next.<\/p>\n\n\n\n <\/p>\n\n\n\n Now review and click, Finish.<\/p>\n\n\n\n <\/p>\n\n\n\n You should see a screen like below. Be patient, it may take a few minutes to complete. Once finished, click close.<\/p>\n\n\n\n Now open SQL Server management Studio. Create a new blank database\u2026..<\/p>\n\n\n\n New Database:<\/p>\n\n\n\n <\/p>\n\n\n\n Double click on the\u00a0sql (ASPNET.MDF.sql)\u00a0<\/strong>\u00a0file you just created to open it in SQL Server Management Studio.\u00a0*It may look like\u00a0ASPNET.MDF.\u00a0<\/strong><\/strong>The .sql is \u00a0a\u00a0hidden<\/strong>\u00a0file extension.Make sure the new database you just created is selected.\u00a0<\/strong>Execute the aspnetdb.mdf sql file you just loaded (the tab will need to be selected in SQL Server Management Studio). You are executing this script so that it will create the necessary tables, relationships, etc., into your new SQL Server database.\u00a0 You can now use this for your asp.net login.<\/p>\n\n\n\n After \u00a0execution it will look like below. You should be able to double click on the database you just created on the left and expand.\u00a0Refresh<\/strong>. Expand the tables folder to see all of the tables the script just created.<\/p>\n\n\n\n Almost There! Now that you have your DB setup, all that is left is to configure your web.config file to use the SQL Server Database you just created.<\/p>\n\n\n\n The asp.net login is still setup to use the default connection string of our original aspnet.mdf file. We need to change the connection string to the SQL Server Database we just made. We have 3 separate areas to update, <connectionStrings>, <membership>, and <roleManager>. The connection string needs to be updated to connect to the new database that was just made. Then there are <providers> tags. One is under<membership> and the other under <roleManager>. Update \u201cconnectionStringName\u201d here to the same name as entered in <connectionStrings>.<\/p>\n\n\n\n For the connectionString, the \u201cData Source\u201d should be the same as what is listed in the \u201cObject Explorer\u201d in SQL Server Management Studio. ID, and Password should be what was used to connect to the Database in SQL Server Management Studio.<\/p>\n\n\n\n See image below. \u00a0The old connection information is commented out with the new information put in.<\/p>\n\n\n\n Here is sample code for the Web.config:<\/p>\n\n\n\n Use Visual Studio to run the Login.aspx file located in the \u201cAccount\u201d folder. You should see a login screen in your browser.<\/p>\n","protected":false},"excerpt":{"rendered":" This tutorial will show you how to make the ASP.NET forms authentication work with SQL Server using the provided ASPNETDB.MDF file. Then it will show you how to properly configure your web.config file to use it. *Note \u2013 This tutorial will help if you are having trouble getting your forms based authentication to work in […]<\/p>\n","protected":false},"author":1,"featured_media":192,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-209","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-uncategorized"},"_links":{"self":[{"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/posts\/209","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/comments?post=209"}],"version-history":[{"count":2,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/posts\/209\/revisions"}],"predecessor-version":[{"id":232,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/posts\/209\/revisions\/232"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/media\/192"}],"wp:attachment":[{"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/media?parent=209"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/categories?post=209"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wshop.fi\/eng\/wp-json\/wp\/v2\/tags?post=209"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/asp-net-login-template.png\")
The ASPNET.MDF File<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/visual-studio-login-aspnetdb-mdf.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/asp-net-web-site-administration-tool1.png\")
ASPNET.MDF in Visual Studio Express<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/visual-studio-login-aspnetdb-mdf-publish-provider-1.png\")
ASPNET.MDF is Visual Studio<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/asp-net-login-include-aspnetmdf-in-project.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/asp-net-login-publish-to-provider-visual-studio-1.png\")
<\/figure><\/div>\n\n\n\nDatabase Publishing Wizard<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/asp-net-visual-studio-database-publishing-wizard1.png\")
ASPNET.MDF in Database Publishing Wizard<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/database-publishing-aspnetdb-mdf1.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/database-publishing-aspnetdb-mdf-sql-output-location1.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/aspnetdb-mdf-options-settings1.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/aspnetdb-mdf-database-sql-script-review1.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/database-publishing-aspnetdb-mdf-progress-finished1.png\")
Using SQL Server Management Studio to run the ASPNET.sql Script<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/sql-server-management-studio-create-new-database.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/New-Database.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/sql-server-management-studio-script-execute.png\")
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/sql-server-management-studio-script-post-execution.png\")
Web.config Connection String<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wshop.fi\/eng\/wp-content\/uploads\/2021\/03\/webconfig-connection-string-aspnet-login-sql-server1-1.png\")
<configuration>\n <connectionStrings>\n <!--<add name=\"ApplicationServices\"\n connectionString=\"data source=.\\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\\aspnetdb.mdf;User Instance=true\"\n providerName=\"System.Data.SqlClient\" \/>-->\n <add name=\"Reports\" connectionString=\"Data Source=YOUR-SQL-DB;Initial Catalog=Reports;Persist Security Info=True;User ID=YOURID;Password=YOURPASSWORD\"\n providerName=\"System.Data.SqlClient\" \/>\n <\/connectionStrings>\n \n <system.web>\n <compilation debug=\"true\" targetFramework=\"4.0\" \/>\n \n <authentication mode=\"Forms\">\n <forms loginUrl=\"~\/Account\/Login.aspx\" timeout=\"2880\" \/>\n <\/authentication>\n \n <membership>\n <providers>\n <clear\/>\n <!--<add name=\"AspNetSqlMembershipProvider\" type=\"System.Web.Security.SqlMembershipProvider\" connectionStringName=\"ApplicationServices\"\n enablePasswordRetrieval=\"false\" enablePasswordReset=\"true\" requiresQuestionAndAnswer=\"false\" requiresUniqueEmail=\"false\"\n maxInvalidPasswordAttempts=\"5\" minRequiredPasswordLength=\"6\" minRequiredNonalphanumericCharacters=\"0\" passwordAttemptWindow=\"10\"\n applicationName=\"\/\" \/>-->\n <add name=\"AspNetSqlMembershipProvider\" type=\"System.Web.Security.SqlMembershipProvider\" connectionStringName=\"Reports\" \n enablePasswordRetrieval=\"false\" enablePasswordReset=\"true\" requiresQuestionAndAnswer=\"false\" requiresUniqueEmail=\"false\" \n maxInvalidPasswordAttempts=\"25\" minRequiredPasswordLength=\"6\" minRequiredNonalphanumericCharacters=\"0\" passwordAttemptWindow=\"10\" \n applicationName=\"\/\"\/>\n <\/providers>\n <\/membership>\n \n <profile>\n <providers>\n <clear\/>\n <add name=\"AspNetSqlProfileProvider\" type=\"System.Web.Profile.SqlProfileProvider\" connectionStringName=\"ApplicationServices\" applicationName=\"\/\"\/>\n <\/providers>\n <\/profile>\n \n <roleManager enabled=\"true\">\n <providers>\n <clear \/>\n <!--<add connectionStringName=\"ApplicationServices\" applicationName=\"\/\"\n name=\"AspNetSqlRoleProvider\" type=\"System.Web.Security.SqlRoleProvider\" \/>-->\n <add connectionStringName=\"Reports\" applicationName=\"\/\" name=\"AspNetSqlRoleProvider\" type=\"System.Web.Security.SqlRoleProvider\"\/>\n <add applicationName=\"\/\" name=\"AspNetWindowsTokenRoleProvider\"\n type=\"System.Web.Security.WindowsTokenRoleProvider\" \/>\n <\/providers>\n <\/roleManager>\n \n <\/system.web>\n \n <system.webServer>\n <modules runAllManagedModulesForAllRequests=\"true\"\/>\n <\/system.webServer>\n<\/configuration><\/code><\/pre>\n\n\n\n