docs/en/solution-templates/single-layer-web-application/_index.md
//[doc-seo]
{
"Description": "Explore the Single Layer Application Solution Template to learn how to create a straightforward .NET solution structure with ease."
}
This template provides a simple solution structure with a single project. This document explains that solution structure in details.
If you created your solution with the default options, you will have a .NET solution as shown below:
In the next sections, we will explain the structure based on this example. Your startup solution can be slightly different based on your preferences.
Since this template provides a single-project solution, we've separated concerns into folders instead of projects. You can see the pre-defined folders as shown below:
Data folder.Entities folder.Localization folder.Menus folder.ObjectMapping folder.Pages folder (create Controllers and Views folder yourself if you prefer the MVC pattern).Services folder.Before running the application, you need to create the database and seed the initial data. To do that, you can run the following command in the directory of your project (in the same folder of the .csproj file):
dotnet run --migrate-database
This command will create the database and seed the initial data for you. Then you can run the application with any IDE that supports .NET or by running the dotnet run command in the directory of your project. The default username is admin and the password is 1q2w3E*.
While creating a database & applying migrations seem only necessary for relational databases, you should run this command even if you choose a NoSQL database provider (like MongoDB). In that case, it still seeds the initial data which is necessary for the application.
If you choose Angular as the UI framework, the solution will be separated into two folders:
angular folder that contains the Angular UI application, the client-side code.aspnet-core folder that contains the ASP.NET Core solution (a single project), the server-side code.The server-side is similar to the solution described in the Solution Structure section above. This project serves the API, so the Angular application can consume it.
The client-side application consumes the HTTP APIs as mentioned. You can see the folder structure of the Angular project shown below: