Help / Developing an application or website / Controls, windows and pages / Controls: Available types / .Net control (WPF) / Xaml control
  • Overview of the control
  • Notes
  • .Net controls
  • Limitations
  • Simulating the absence of .Net 3.0 framework
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
Overview of the control
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.
To create a.Net control (WPF):
  1. On the "Creation" tab, in the "Other controls" group, click "XAML".
  2. Click at the desired location to create the control. The control appears in the editor.
To view the characteristics of the control, select "Description" in the context menu.

.Net controls

To use the .Net controls, WINDEV proposes:


The limitations of the .Net control (WPF) are as follows:
  • 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 wd290xaml.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).
To simulate the absence of the framework on a computer:
  • use the XamlDisable function.
  • rename the following registry key: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v3.0".
Minimum version required
  • Version 11
Click [Add] to post a comment

Last update: 04/19/2023

Send a report | Local help