{"id":804,"date":"2020-10-09T08:55:46","date_gmt":"2020-10-09T08:55:46","guid":{"rendered":"https:\/\/serkanseker.com\/?p=804"},"modified":"2020-12-07T15:47:37","modified_gmt":"2020-12-07T15:47:37","slug":"asp-net-core-web-api-application-structure","status":"publish","type":"post","link":"https:\/\/serkanseker.com\/tr\/asp-net-core-web-api-application-structure\/","title":{"rendered":"ASP.NET Core Web API Application Structure"},"content":{"rendered":"\n

Here you will learn the structure and importance of the Web API project created with ASP.NET Core 3.1<\/a>.<\/p>\n\n\n\n

Before starting, I recommend you to review the article called Create And Consume ASP.NET Core Web API<\/a>, where I show you how to create a project.<\/p>\n\n\n\n

Project Structure<\/h2>\n\n\n\n

The following is a default project structure when you create an ASP.NET Core Web API project in Visual Studio.<\/p>\n\n\n\n

\"ASP.NET
ASP.NET Core Web Application Project Structure<\/figcaption><\/figure><\/div>\n\n\n\n

.csproj File Structure<\/h2>\n\n\n\n

The .csproj file contains settings such as .NET Frameworks, project files, NuGet packages. It does not create .csproj in ASP.NET Core 1.0, instead the project is managed with .xproj and project.json files.<\/p>\n\n\n\n

Right-click the project and select Edit Project File<\/strong> to access the .csproj file.<\/p>\n\n\n\n

\".csproj
.csproj structure<\/figcaption><\/figure><\/div>\n\n\n\n

Dependencies <\/h2>\n\n\n\n

Dependencies includes all installed server-side NuGet packages<\/strong>, Analyzers <\/strong>and Frameworks<\/strong>. To add NuGet packages, right-click the project and select Manage NuGet Packages<\/strong>.<\/p>\n\n\n\n

Properties <\/h2>\n\n\n\n

Properties contains the file launchSettings.json<\/strong>, which contains Visual Studio profiles of debug settings.<\/p>\n\n\n\n

\"launchSettings.json
launchSettings.json structure<\/figcaption><\/figure><\/div>\n\n\n\n

Program.cs<\/h2>\n\n\n\n

The Main method in the Program.cs file in the project is the starting point of the project. The most basic components needed by the application are connected to the WebHostBuilder object created here, and the application is run over this object.<\/p>\n\n\n\n

Startup class is the second method that runs after the main method. While the basic components are determined in the Main method, the middleware and service components needed in the next step will be determined in the class named Startup. The WebHostBuilder object determines this class with the UseStartup() method.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"Program.cs
Program.cs structure<\/figcaption><\/figure><\/div>\n\n\n\n

Startup.cs<\/h2>\n\n\n\n

There are two important methods in this class; Configure <\/strong>and ConfigureServices<\/strong>.<\/p>\n\n\n\n

Middleware components are determined in the Configure <\/strong>method. They structures that we can liken to HttpModules in ASP.NET. They are structures that take place in the application pipeline and run on every request-response.<\/p>\n\n\n\n

In the ConfigureServices<\/strong> method, service components are registered to the container object and are used in different parts of the application (for example, Controller classes).<\/p>\n\n\n\n

\"Startup.cs
Startup.cs structure<\/figcaption><\/figure><\/div>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

In this article, I tried to explain the structure of a project created with ASP.NET Core 3.1. The titles here should be discussed in detail.<\/p>\n\n\n\n

Related Posts<\/h2>\n\n\n\n