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

;

XAML Namespace

Integration via XAML namespace

In addition to the iPlus standard controls, you can use any WPF controls from different manufacturers (e. g. from Telerik, syncfusion, devexpress) for the user interface

You will need some basic knowledge, which you can acquire on the Microsoft website https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml.

However, you only have to observe the following steps:

Your control library must be located in the program directory of the iPlus installation.
You create a new design in Variobatch Studio or change an existing one.
In the first XML element of the XAML file, you must specify the namespace to which the control you want to use belongs.
Use the control in the XAML code by setting the prefix with a colon in front of the control class name.

Example:

In order for an XAML file to be parsed, the first two Microsoft namespaces must be announced:

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

If you want to use controls from the iPlus standard control library (gip.core.layoutengine) specify the namespace xmlns:vb="http://www.iplus-framework.com/ACFramework/xaml".

Control elements for the process technology are included in the gip.core.visualcontrols and are announced with xmlns:vbv="http://www.iplus-framework.com/ACFramework/visual/xaml".

In order to be able to display curve diagrams we recommend you to use the gip.core.scichart.dll (xmlns:vbs="http://www.iplus-framework.com/ACFramework/scichart/xaml" ) which extends the section Abt.Controls.SciChart.Wpf.dll (xmlns:s="http://schemas.abtsoftware.co.uk/scichart").

Which prefixes you use for the namespace mapping is up to you and can be freely assigned. However, we recomend that you use the suggested ones.

CLR-Namespace

Using libraries that have not defined an XAML namespace.

Usually, WPF libraries are provided with an xmlnsdefinitionattribute attribute to enable a mapping of XAML namespace to the CLR namespace, and the XAML parser can find and instantiate the controls. If such a definition is missing, the CLR namespace must be specified directly using the following syntax:

xmlns:custom="clr-namespace:SDKSample;assembly=SDKSampleLibrary"

In the clr-namespace attribute, specify the .NET-namespace.

The Full-Qualified-Assembly-Name must be specified in the attribute assembly.

Cookie settings