This was broken when ISO endpoint support was added.

This property will always return true.

If LibUsbDotNet is compiled as Win32 instead of Any CPU it would not work on 64bit operating systems with libusb-win32.

The LUDN edition of libusb-win32 has been discontinued as it is no longer needed. LibUsbDotNet v2.2.6 and above are packaged with the official libusb-win32 signed drivers. (http://sourceforge.net/projects/libusb-win32)

Previous version of the InfWizard required the user to download driver resource package(s) before it could be used. InfWizard will continue to support these downloadable driver packages but now comes with a libusb-win32 driver resource package embedded into InfWizard.exe.

This event is fired on the DataReceivedEnabled property changes state.

InfWizard no longer uses the 'Find Drivers' option. Instead, it uses driver resource packages that contain the drivers/coinstallers, inf/cat file templates, and all other files that may be required by the installation. Driver resource packages can be downloaded automatically by InfWizard or from http://sites.google.com/site/libusbdotnet/driver_resources. As of v2.2.5 Winusb 1.9 and libusb-win32 0.1.12.2 packages are available.

InfWiard has an install now feature, thanks to Peter Batard and the Libusb-1.0 team. After a driver package is created, it can be automatically installed.

InfWizard remove device function enhancements. The remove device function can remove usb devices by the device instance id or all devices matching the hardware id. It now calls SetupDiUnintallOEMInf as well as SetupDIRemoveDevice.

Detailed logging added. Most of the InfWizard pages have a log status rtf box which indicates the current progress of an operation. All log status boxes can be saved, copied and cleared via the context menu.

Improved support for composite devices. Added DeviceID and InterfaceID property

The endpoint type must be specified for linux Libusb-1.0 compatibility.

Thank Xiaofan (http://mcuee.blogspot.com) for helping debug this application and getting it ready for release.

The xbuild utility failed to build the LibUsbDotNet.sln. This was caused by an invalid resource in the InfWizard application and a casting issue for function that take a Predicate<> as a parameter.

USB devices that have VID or PIDs greater than 0x7FFF are not found by the UsbDeviceFinder class.

For more details see the NewAsyncTransfer()()()() and SubmitAsyncTransfer()()()() functions in the UsbEndpointBase class.

The low-level MonoLibUsb API (Libusb-1.0) is supported on many platforms including windows via the Libusb-1.0 windows-backend port.

Unlike the LibUsbDotNet API, MonoLibUsb has full support for all Libusb-1.0 functions.

This option forces LibUsbDotNet to gather extra device information via the windows setup api for devices using drivers that do not support the setupapi.

This option forces LibUsbDotNet to use only the Libusb-1.0 windows backend driver.

The UsbDevice.Open()()()() method requests the usb devices current configuration upon opening. This causes problems in some situations.

If .NET 3.5 is not installed, a System.Threading.WaitHandle.WaitOne missing member exception is thrown. LibUsbDotNet should not require the 3.5 runtime. It should work with 2.0 and greater.

If an attempt is made to open and transmit to a non-existent endpoint a stack overflow occurs. Expected behavior is to throw an exception.

[Windows Only] If the UsbDevice.KernelType is accessed when no device are connected it does not update properly when a device is connected.

On Linux like OSes the DeviceNotifier never fires events. On Windows, a DllNotFound exception is thrown.

WinUSB interfaces that are part of a composite device do not appear in the WinUsbRegistry.DeviceList.

On big-endian platforms, the descriptor type and index bytes are reversed.

The benchmark application now uses a timer control to periodically update the display instead of "Invoking" an update everytime data is transferred. This provides a more accurate benchmark reading as well as a work-a-round for Mono .NET runtimes on platforms that do not properly implement the Control.Invoke method.

The LINUX compiler option is no longer used. LibUsbDotNet (v2.2.1 and above) is fully platform independent.

LibUsbDotNet supports linux via the linux libusb v1.x driver.

If an attempt is made to open an endpoint on a unconfigured device (GetConfiguration = 0) an exception is thrown.

If an attempt is made to open a non-existent or invalid endpoint an exception is thrown.

A New property, 'EndpointInfo' is available from the UsbEndpointBase class.

The UsbGlobals class has been rendered obsolete and will be removed in future release. Update your code you use the UsbDevice class instead.

When connecting 2 (or more) identical USB devices, the library has problems opening each device instance.

Some devices having no SymbolicName. In this case, the main application or .NET framework crashes.

The InfWizard throws an exception when loaded.

If the LibUsbDotNet native kernel driver is not detected it falls back to the original libusb-win32 kernel driver. Using the native driver is recommended.

Opens a libUsb device from a user suppiled device filename.

public static bool Open(string deviceFilename, out LibUsbDevice usbDevice)

Opens a WinUSB device from a user suppiled device path (symbolic link).

public static bool Open(string devicePath, out WinUsbDevice usbDevice)

A DeviceInterfaceGuid is not required for a WinUsbDevice.

A UsbRegistry instance is not required for the UsbDevice classes.

The device and endpoint level locking features had specfic requirements pertaining to the usb symbolic name that could not always be met.

The GET_INTERFACE request in the libusb kernel driver fails on Windows XP SP3 but works under windows Vista.

The InfWizard spawn driver function fails to locate WinUSB support drivers from the DDK install directory.

If an an attempt is made to open an endpoint that does not exists, a UsbException is thrown.

Applied LibUsbDotNet kernel driver patches to libusb-win32 v0.1.12.2. LibUsbDotNet-libusb-win32 v2.1.12.2 kernel created.

Removed all references to benchmark device. The Test_Bulk apllication is more universal and easier to tailor to specific devices.

The USBSymbolicName class is converting the bcd revision number to a hex number.

On the final wizard page of the InfWizard the "Driver Information" property under the "Info" category is never populated.

Calling UsbGlobals.OpenDevice(UsbDeviceFinder) generates an exception if the device is not found.

Field passed in is not a marshaled member of the type 'LibUsbDotNet.DeviceNotify.Internal.DevBroadcastPort'. Parameter name: fieldName.

• VendorID
• ProductID
• Revision Code
• Serial Number
• Device Interface GUID