Difference between revisions of "Dependency Injection"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
:# [[ Truxton CLI options ]] | :# [[ Truxton CLI options ]] | ||
:# [[ How Reports are Displayed ]] | :# [[ How Reports are Displayed ]] | ||
| + | :# [[ How Dialog Forms Work ]] | ||
| + | :# [[ Forms with Images ]] | ||
| + | :# [[ Images ]] | ||
| + | :# [[ Bookmarks ]] | ||
== Dependency Injection == | == Dependency Injection == | ||
Latest revision as of 11:28, 30 November 2021
This page documents the Dependency Injection (DI) of the application, or how each class's dependencies(services, etc) are loaded automagically. This document is intended to detail the references and flow of the DI used in the UI.
UI Guide Menu
Dependency Injection
Services
- There are two types of Services found in the UI:
- Services that provide data for content.
- Services that support UI functionality (Overlays, Dialogs, Images, etc) (\Truxton\Client\TruxtonClient\TruxtonClient\Services\)
- This is a loose definition and it may change but it'll work for now. Here, we'll be talking about Services that provide data for content.
- Services can be found in
\Truxton\Client\Libraries\TruxtonClient.Services
- They'll need a matching Interface for DI to work. Interfaces can be found in
\Truxton\Client\Libraries\TruxtonClient.Services\Interfaces
- Once the service and interface are created, they need to be registered in ServiceRegistrar.cs
\Truxton\Client\TruxtonClient\TruxtonClient\PresentationCore\ServiceRegistrar.cs
