Category:High-Level Configuration: Difference between revisions
From OPC Labs Knowledge Base
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:Configuration]] | [[Category:Configuration]] | ||
The high-level configuration allows you to set parameters of main QuickOPC components. It is based on Microsoft's {{Style=Identifier|IConfiguration}} abstraction, and it also uses some | The high-level configuration allows you to set parameters of main QuickOPC components (such as {{Style=Identifier|EasyUAClient}}). It is based on Microsoft's {{Style=Identifier|IConfiguration}} abstraction, and it also uses some concrete implementations related to it. | ||
There are following kinds of high-level configuration: | There are following kinds of high-level configuration: | ||
; [[Built-in Component Configuration]]: Always available. You can set the parameters of components externally (using e.g. environment variables, or ''apsettings.json'' files). The software does not have to be prepared upfront. [[Built-in Component Configuration|Details]] | ; [[Built-in Component Configuration]]: Always available. You can set the parameters of components externally (using e.g. environment variables, or ''apsettings.json'' files). The software does not have to be prepared upfront. [[Built-in Component Configuration|Details]] | ||
; Programmatic Component Configuration: Available when you decide to use it. You can instantiate the components while passing them a configuration to use. See the User's Guide for instructions. | ; Programmatic Component Configuration: Available when you decide to use it. You can instantiate the components while passing them a configuration to use. See the User's Guide for instructions. | ||
Revision as of 14:12, 18 January 2021
The high-level configuration allows you to set parameters of main QuickOPC components (such as EasyUAClient). It is based on Microsoft's IConfiguration abstraction, and it also uses some concrete implementations related to it.
There are following kinds of high-level configuration:
- Built-in Component Configuration
- Always available. You can set the parameters of components externally (using e.g. environment variables, or apsettings.json files). The software does not have to be prepared upfront. Details
- Programmatic Component Configuration
- Available when you decide to use it. You can instantiate the components while passing them a configuration to use. See the User's Guide for instructions.
Pages in category "High-Level Configuration"
The following 3 pages are in this category, out of 3 total.
