Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Application.md #18265

Open
wants to merge 1 commit into
base: rel-7.4
Choose a base branch
from
Open

Update Application.md #18265

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions docs/en/Startup-Templates/Application.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,12 +175,14 @@ This project contains the main `appsettings.json` file that contains the connect
* Depends on the `.HttpApi` project since the UI layer needs to use APIs and the application service interfaces of the solution.

> If you check the source code of the `.Web.csproj` file, you will see the references to the `.Application` and the `.EntityFrameworkCore` projects.
> They are there so that you can host the Web, API and application layers in a single application endpoint.
>
> These references are actually not needed while coding your UI layer as the UI layer normally doesn't depend on the EF Core or the Application layer's implementation.
> This gives you the ability to use domain entities & repositories in your presentation layer which you should avoid as it is considered as a bad practice according to DDD.
>
> If you choose the `--tiered` option, the startup template will be configured for tiered deployment where the API layer is hosted on a separate server than the UI layer.
> In this case these references will be removed.
>
> These references are actually not needed while coding your UI layer, because the UI layer normally doesn't depend on the EF Core or the Application layer's implementation. These startup templates are ready for tiered deployment, where the API layer is hosted on a separate server than the UI layer.
>
> However, if you don't choose the `--tiered` option, these references will be in the .Web project to be able to host the Web, API and application layers in a single application endpoint.
>
> This gives you the ability to use domain entities & repositories in your presentation layer. However, this is considered as a bad practice according to DDD.

#### Test Projects

Expand Down