From a5d5a781e2b2170fd094d127c2a4640efef84dc1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kemal=20Gen=C3=A7?= Date: Wed, 6 Dec 2023 12:10:11 +0300 Subject: [PATCH] Update Application-Startup.md use instead of create --- docs/en/Application-Startup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Application-Startup.md b/docs/en/Application-Startup.md index 5711d61dc4..0b120bd534 100644 --- a/docs/en/Application-Startup.md +++ b/docs/en/Application-Startup.md @@ -144,7 +144,7 @@ AbpApplicationFactory.CreateAsync(typeof(MyConsoleDemoModule)); Both overloads work exactly the same. So, you can use the second one if you don't know the module class type on development time and you (somehow) calculate it on runtime. -If you create one of the methods above, ABP creates an internal service collection (`IServiceCollection`) and an internal service provider (`IServiceProvider`) to setup the [dependency injection](Dependency-Injection.md) system internally. Notice that we've used the `application.ServiceProvider` property in the *Installing a Framework Package* section to resolve the `IEmailSender` service from the dependency injection system. +If you use one of the methods above, ABP creates an internal service collection (`IServiceCollection`) and an internal service provider (`IServiceProvider`) to setup the [dependency injection](Dependency-Injection.md) system internally. Notice that we've used the `application.ServiceProvider` property in the *Installing a Framework Package* section to resolve the `IEmailSender` service from the dependency injection system. The next overload gets an `IServiceCollection` parameter from you to allow you to setup the dependency injection system yourself, or integrate to another framework (like ASP.NET Core) that also sets up the dependency injection system internally.