Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This topic describes caveats you should be aware of when calling WDF functions from a NetAdapterCx client driver.
| Function | Description |
|---|---|
| WdfDeviceInitAssignSDDLString | By default NetDeviceInitConfig assigns SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RW_RES_R as the default SDDL. If you specify a more restrictive SDDL, the application might not be able to send query OIDs to the adapter. |
| WdfDeviceInitSetFileObjectConfig | The client driver must not set WdfFileObjectWdfCanUseFsContext in the FileObjectClass member of WDF_FILEOBJECT_CONFIG. |
| WdfDeviceInitAssignName, WdfDeviceInitSetReleaseHardwareOrderOnFailure, WdfDeviceInitSetDeviceType, WdfDeviceInitSetCharacteristics, WdfDeviceInitSetIoType, WdfDeviceInitSetPowerPageable | NetDeviceInitConfig calls these routines on behalf of the client driver. The client driver should not call these. |
| WdfDeviceCreateDeviceInterface | If the client driver calls WdfDeviceCreateDeviceInterface with the ReferenceString parameter equal to NULL, NDIS intercepts I/O requests sent to the device interface. To avoid this behavior, specify any reference string. |