Skip to main content

Add/Create ASP.NET Membership tables/view/sp with aspnet_regsql


To install the membership database, log on to your server with an account that has authority to administrate SQL Server (such as the Administrator account). If you want to add membership tables to existing DB then use that DB in example else create new DB, here I’m creating new DB with Name Test_Membership as below(and will use this DB throughout this example):

 
Fig.1 Create New DB wizard

 Fig.2 Give DB name and click OK to create DB

Now DB is created, next step is create Membership tables to your DB, here we goes:

If you love to work with command prompt then follow these two simple steps:
1. Start a Visual Studio command prompt by going to Start -> All Programs -> Visual Studio 2010 -> Visual Studio Tools -> Visual Studio Command Prompt.
2.  Run the following command, using the your Test_Membership database settings to fill in the values in brackets: aspnet_regsql.exe -S [Host] -d [Name] -U [Username] -P [Password] -A all

And your Membership tables/view/sp are added to your DB.

Else if you love to work with designer and want to add membership details to your DB through designer, then follow these simple steps.

1.  Run C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regsql.exe.

2.  Click on Next

 
3. Select “Configure SQL Server for application services” and click on Next.


 4. Select “Windows Authentication” and then select Database and hit Next.

While accessing DB through Windows Authentication some may face error : failed to query a list of database names,
if there is no error then go to next step, but if you face such error then simply select SQL server Authentication and enter username and password and then select your DB as:

5. Setting summary screen appear and your settings are then presented...then click on Next

 
6. Finally you should be presented with a finish screen,click on Finish and you are done with process.


Now you can check in your DB to verify whether membership tables/views/stored procedures are created or not.

Cheers!!!

Comments

Post a Comment

Popular posts from this blog

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...