If there is a contradiction between the .NET control properties as they are defined in Magic xpa and the .NET Object Properties, the values defined in Magic xpa will take priority.

In order to use a .NET variable, it must be instantiated first. .NET variables that are attached to a control are instantiated automatically. If the .NET variable does not have a control, you should first run its constructor before executing any function on it.

Only the .NET variables whose class inherits from System.Windows.Forms.Control can be used as a control on the form. To use a .NET control, you need to load the System.Windows.Forms assembly into the CRR.

It is not possible to attach a .NET control to a Table control or another .NET control.

Some of the Magic xpa internal events, such as Zoom, do not work when raised from a .NET control.

When clicking on a .NET control, if the click starts an action on the .NET control (for example, by clicking on a .NET spinner control), then this action will be executed even if the previous control had a Verify Error operation in the Control Verification or Control Suffix logic unit.

When using a .NET control to display the task data view, the task is not aware of the .NET control columns, so Control level logical units cannot be used. Variable Change logical units can be used.

OS reserved keyboard shortcuts (such as F10) will not work on .NET controls.