An association between a service access point (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one logical device, operating in conjunction. Any device can provide more than one SAP. When many logical devices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the access point. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the SAP object. These individual instantiations would then have associations to the unique implementations.
The following syntax is simplified Managed Object Format (MOF) code, and it includes all of the inherited properties.
Syntax
[Association, Dynamic, Provider("VmmsWmiInstanceAndMethodProvider"), AMENDMENT]
class Msvm_WiFiDeviceSAPImplementation : CIM_DeviceSAPImplementation
{
Msvm_WiFiPort REF Antecedent;
Msvm_WiFiEndpoint REF Dependent;
};
Members
The Msvm_WiFiDeviceSAPImplementation class has these types of members:
Properties
The Msvm_WiFiDeviceSAPImplementation class has these properties.
Antecedent
Data type: Msvm_WiFiPort
Access type: Read-only
Qualifiers: Override ("Antecedent")
An instance of the Msvm_WiFiPort class that represents the logical device.
Dependent
Data type: Msvm_WiFiEndpoint
Access type: Read-only
Qualifiers: Override ("Dependent")
An instance of the Msvm_WiFiEndpoint class that represents the service access point implemented using the logical device.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows 8 [desktop apps only] |
| Minimum supported server | Windows Server 2012 [desktop apps only] |
| Namespace | Root\Virtualization\V2 |
| MOF | WindowsVirtualization.V2.mof |
| DLL | Vmms.exe |
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
