Advanced programming

collapse

#
- 1.) Application.config
- 2.) Basic concepts
  - 1.) Composite pattern
    - 1.) Lifecycle
    - 2.) Programming
  - 2.) Properties
    - 1.) Local
    - 2.) Network
    - 3.) Persistance
    - 4.) Configuration
    - 5.) Logging
  - 3.) Synchronous Methods
    - 1.) Virtual methods
  - 4.) References
    - 1.) 1 Object
    - 2.) N Objects locally
    - 3.) N Objects Network
  - 5.) Events
  - 6.) Asynchronous methods
  - 7.) Configuration
    - 1.) Config storage
    - 2.) Overriding
  - 8.) Messages and Alarms
    - 1.) Alarms
  - 9.) Database
    - 1.) Usage
    - 2.) Extend
      - 1.) EF 4.0
      - 2.) EF 7.0
    - 3.) Persistable queries
  - 10.) Designs
    - 1.) GUI Design
      - 1.) Set and convert Properties
      - 2.) Styles and Setter
      - 3.) Property trigger
      - 4.) Datatrigger
      - 5.) Events & trigger
      - 6.) Animations
      - 7.) Resources
    - 2.) Reports
      - 1.) Programming
  - 11.) Diagnose and Debugging
  - 12.) Updates
- 3.) UI-Controls
  - 1.) UI-Library integration
  - 2.) iPlus-Controls
  - 3.) Custom Controls
- 4.) Application programming
  - 1.) Multithreading
  - 2.) Businessobjects
    - 1.) Navigationless
    - 2.) Navigable
    - 3.) Context dependant dialogs
    - 4.) Background Tasks
  - 3.) Manager classes
  - 4.) Process applications
  - 5.) Workflow classes
  - 6.) External systems
    - 1.) Mobile devices
    - 2.) OPC UA Communication
      - 1.) Server
    - 3.) Simatic S7
  - 7.) Bit masking
- 5.) []

;

Configuration properties are a special variant of persistable properties. Unlike the local properties in section 1, they cannot be read or written from a proxy object using network access. Therefore, A WPF data binding to this property is not possible. Configuration properties are the most primitive variant of storeable properties. They are primarily used to set the behavior of an ACComponent (server-side instance or business objects).

The value of a configuration property can be changed either by the ACComponent itself or in the development environment in the Configuration tab.

Technically, the value of a configuration property is stored in as an entry in the ACClassConfig table. Please refer to the "Configuration" section for more information, because the actual configuration is larger than just saving configuration properties.

Usage and Programming

First, the following code example:

Configuration properties are instances of the generic class gip.core.autocomponent.ACPropertyConfigValue<T> .

Declare a private field of this type.
Declare a public property with getter and setter that encapsulates access to the ACPropertyConfigValue-Instance. In the getter and setter method, read or set the ValueT property.
Use the ACPropertyConfig attribute class to register the configuration property to the iPlus type system.
Instantiate the ACPropertyConfigValue class in the constructor or the overriden ACInit() method in your derived class ACComponent. In the constructor of the ACPropertyConfigValue class, you pass the this pointer of the ACComponent in the first parameter. In the second parameter, you specify exactly the same name as you declared your configuration property in the C#-code (step 2). The third parameter is the default value. Please note that the default value is only set when the ValueT property is first accessed and a new entry is made in the ACConfig table.

Important: Caching!

Please keep in mind that config values are cached. If ValueT is accessed several times, a fresh database query is not performed. Explicitly call the ACComponent.ResetConfigValuesCache() method to reset the cache and force it back to load from the database.

Important: Caching!

Cookie settings