This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 57.00000000000001%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Sir, It has been more than a month since finding a help article explaining how to publish an asp.net core application having a database to IIS. I have extensively worked with ASP.NET MVC and am quite familiar with VS publishing features. But, when it comes to the core, I am unable to understand in which directory database files get saved or whether VS altogether saves the database or not after publishing. The file structure of the published application is well organised in asp.net MVC but the core published folder gets dumped with dlls making it difficult to manage. For example, in ASP.NET MVC replacing the .cshtml file in a view folder was possible which makes it easy to manage the site but the same is not possible with the ore. Therefore, please help me understand how to publish asp.net core application that has a database to iis.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Arun Khatri ,
When you publish the database, you can set the database connection:
After deploy the application to IIS, by default the web site will use the ApplicationPoolIdentity (select the application pool, then click on 'Advanced Settings..." on the right-side. then check the Identity option), So, when you running the application and access the database, you will receive the a network related or instance specific error while establishing connection to sql server. The issue relates the ApplicationPoolIdentity, you can change it to LocalSystem, then, IIS will try and login to the database using a built-in account named 'NT AUTHORITY\SYSTEM'. We need to give this account access to the database in LocalDB. You can do it via the SQL Server Management Studio (SSMS). After that you can access the local database from the deployed web site.
More detail information, you can search "Deploying an ASP.NET Core application that uses LocalDB to iis" via google.
Besides, you can also try to use Azure SQL Database. Refer to Tutorial: Build an ASP.NET Core and Azure SQL Database app in Azure App Service.
Best regards,
Dillion
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
asp.net core is precompiled, so it is only dll's and the wwwroot folder. earlier version used a more complex folder structure, but it was simplified.
unless you are using a localdb, there are no database files. if you use a localdb its in the publish root. sqlite is the typical local db and the database file is named app.db