Support.ValidateControls(ContainerControl) Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Caution
Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862
Emulates the behavior of the Visual Basic 6.0 ValidateControls
method.
public:
static void ValidateControls(System::Windows::Forms::ContainerControl ^ Form);
public static void ValidateControls (System.Windows.Forms.ContainerControl Form);
[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public static void ValidateControls (System.Windows.Forms.ContainerControl Form);
static member ValidateControls : System.Windows.Forms.ContainerControl -> unit
[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
static member ValidateControls : System.Windows.Forms.ContainerControl -> unit
Public Sub ValidateControls (Form As ContainerControl)
Parameters
- Form
- ContainerControl
The ContainerControl where the control is parented.
- Attributes
Remarks
In Visual Basic 6.0, the ValidateControls
method was used to force the Validate
event for the control that has focus when a form is closed; if the Validate
event fails, an error was raised. In Visual Basic, the ValidateControls
method is replaced by the Validate method, which returns true
or false
.
This function is used by the upgrade tools to emulate the Visual Basic 6.0 behavior.
Note
Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.