Merge pull request #78 from TRUMPF-IoT/77-update-docs

Removed obsolete call to UseServiceHost from docs

docs/diContainerOverview.md

@@ -10,7 +10,6 @@ applicationServices.AddHost(config => {}, null);
 applicationServices.AddCdeInfrastructure(cdeConfig => {});
 
 using var applicationServiceProvider = applicationServices.BuildServiceProvider();
-applicationServiceProvider.UseServiceHost();
 ```
 
 This code builds the main DI container by adding the SAF `ServiceHost` and the [C-DEngine](https://github.com/TRUMPF-IoT/C-DEngine) specific infrastructure service implementations. In addition it loads available SAF Plug-ins. While loading the SAF Plug-ins, SAF internally creates one independent DI container for each of them. It registers the infrastructure services added to the main DI container to the independent Plug-in specific DI container. With that the added SAF infrastructure can be used inside the loaded SAF Plug-ins.
@@ -19,8 +18,6 @@ Additionaly the SAF Service Host calls the Plug-ins `IServiceAssemblyManifest.Re
 
 All services registered to the Plug-in specific DI container are isolated in that container and are therefore not accessible from inside other Plug-ins. Plug-in to Plug-in communication is therefore only possible through the messaging infrastructure service registered in the main DI container.
 
-Afterwards the code snippet above runs the SAF application by calling the `UserServiceHost` extension method.
-
 The following diagram shows the existing DI containers inside a SAF application:
 
 ![SAF DI Container Overview](./diagrams/saf-di-container-overview.svg).