Versions 16 and laterCaution: The Xaml control found in the earlier WINDEV versions (up to version 15) is now called the ".NET 3.0, 4.0, ... control (WPF)". In this documentation, we will be using the term of ".Net control (WPF)".

New in version 16Caution: The Xaml control found in the earlier WINDEV versions (up to version 15) is now called the ".NET 3.0, 4.0, ... control (WPF)". In this documentation, we will be using the term of ".Net control (WPF)".

Caution: The Xaml control found in the earlier WINDEV versions (up to version 15) is now called the ".NET 3.0, 4.0, ... control (WPF)". In this documentation, we will be using the term of ".Net control (WPF)".

The .Net control (WPF) (also called "XAML") is used to easily manage the .NET controls in WPF format (for .NET 3.0, 3.5 and 4.0) and especially the Xaml language.

To use this control, we strongly advise you to check the Microsoft documentation.

The .Net framework version 3.0 (or later) must be installed on the computer. This framework is included in Vista and it can be downloaded for Windows XP (from the Microsoft site).The first use of a control that requires this framework (Carousel control, Cube control, ".NET 3.0, 4.0, ... control (WPF)") loads this framework, which may cause delay (out of our control).

The application cannot be started from the network.

The DDW feature is disabled for all the windows containing a ".NET 3.0, 4.0, ... control (WPF)".

This control does not operate under TSE.

This control uses the wdxxxxaml.dll library. This library cannot be renamed when creating the executable.

Simulating the absence of .Net 3.0 framework

When developing an application that contains a .Net control (WPF), it may be useful to find out how the application will operate when it is started on a computer not equipped with the .Net 3.0 framework (or later).