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.) []

;

Functionality

With storable properties, you can ensure that after an unexpected program crash or the more regular termination of the iPlus-service, the state is restored after the service is restarted.

For a property to be storable (persistent), you must set the IsPersistable property of the various ACPropertyBase attribute classes to True.

The save operation is performed immediately (asynchronously) when calling the setter method (by calling the OnPropertyChanged() method) or when changing the ValueT property of network-capable properties.

On the other hand, the iPlus framework performs the recovery by calling the setter method once at startup with the value that was last stored in the database.

From a technical point of view, serialization or deserialization always takes place when writing or reading using the DataContractSerializer. The serialized string is stored in the property XMLValue of the table ACClassTaskValue. Therefore, only data types that have been previously made known to the DataContractSerializer can be stored.

Serializability

For serialization iPlus uses the DataContractSerializer from .NET. The DataContractSerializer is not only used to persist the properties but also for network transmission (client/server). In both cases, all types that are to be stored or transmitted over the network must be made known to the DataContractSerializer in the KnownTypes property.

However, the iPlus framework simplifies this for you by only having to use the attribute class ACSerializeableInfo. Declare it before a ACComponent-Class where you want to use this type:

bleInfo(new Type[] { typeof(ACMaintWarning), typeof(List<ACMaintWarning>), typeof(List<ACMaintDetailsWarning>) })]

Exaple for Smart-Pointer:

[ACSerializeableInfo(new Type[] { typeof(ACRef<Weighing>) })]

You must also describe the types with the DataContract- and DataMember-Attribut classes as the WCF specifies.

Entity objects

Attention: Avoid this with Entity objects! Entity objects should be read and written manually by using your own ObjectContext or DatabaseContext. Read more about this in the section "Database Contexts and Entity Framework".

Cookie settings