Udostępnij za pośrednictwem


WindowClass Constructors

Definition

Initializes a new instance of the WindowClass class.

Overloads

WindowClass()

This API supports the product infrastructure and is not intended to be used directly from your code.

Initializes a new instance of the WindowClass class.

WindowClass(String, Boolean)

This API supports the product infrastructure and is not intended to be used directly from your code.

Initializes a new instance of the WindowClass class, specifying information about the versioning status of the window class.

WindowClass()

Source:
FileReference.cs

Initializes a new instance of the WindowClass class.

This API supports the product infrastructure and is not intended to be used directly from your code.

public:
 WindowClass();
public WindowClass ();
[System.Runtime.TargetedPatchingOptOut("Performance critical to inline this type of method across NGen image boundaries")]
public WindowClass ();
Public Sub New ()
Attributes

Applies to

WindowClass(String, Boolean)

Source:
FileReference.cs

Initializes a new instance of the WindowClass class, specifying information about the versioning status of the window class.

This API supports the product infrastructure and is not intended to be used directly from your code.

public:
 WindowClass(System::String ^ name, bool versioned);
public WindowClass (string name, bool versioned);
new Microsoft.Build.Tasks.Deployment.ManifestUtilities.WindowClass : string * bool -> Microsoft.Build.Tasks.Deployment.ManifestUtilities.WindowClass
Public Sub New (name As String, versioned As Boolean)

Parameters

name
String

The name of the class.

versioned
Boolean

Controls whether the internal window class name that is used in registration contains the version of the assembly that contains the window class.

Remarks

The versioned parameter controls whether the internal window class name that is used in registration contains the version of the assembly that contains the window class. The value of this attribute can be yes or no. The default is yes. The value no should be used only if the same window class is defined by a side-by-side component and an equivalent non-side-by-side component and you want to treat them as the same window class. Note that the usual rules about window class registration apply: only the first component that registers the window class will be able to register it, because it does not have a version applied to it.

Applies to