Edit

Share via


Support.SetCancel(Button, Boolean) Method

Definition

Caution

Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862

Sets the CancelButton property of a Form.

public:
 static void SetCancel(System::Windows::Forms::Button ^ btn, bool Cancel);
public static void SetCancel (System.Windows.Forms.Button btn, bool Cancel);
[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 SetCancel (System.Windows.Forms.Button btn, bool Cancel);
static member SetCancel : System.Windows.Forms.Button * bool -> 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 SetCancel : System.Windows.Forms.Button * bool -> unit
Public Sub SetCancel (btn As Button, Cancel As Boolean)

Parameters

btn
Button

A Button.

Cancel
Boolean

true if the Visual Basic 6.0 CommandButton control's Cancel property is true; otherwise false.

Attributes

Remarks

In Visual Basic 6.0, the Boolean Default and Cancel properties of a CommandButton control determine whether the control responds to the ENTER or ESC keys, respectively. In Visual Basic, the Button control no longer has Default or Cancel properties. The Form object has AcceptButton and CancelButton properties that provide the same functionality; these properties take the name of a Button control as an argument.

This function is used by the upgrade tools to set the CancelButton property of a Form.based on the Cancel property of an upgraded Visual Basic 6.0 CommandButton control.

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.

Applies to