Is there a way to programmatically determine currently installed version of WinUSB? I searched WinUSB documentation and there is no such API at the WinUSB DLL level. It seems to depend on WDF version, and how can one find that out programmatically?
Is there a way to programmatically determine currently installed version of
WinUSB? I searched WinUSB documentation and there is no such API at the WinUSB
DLL level. It seems to depend on WDF version, and how can one find that out
programmatically?
Is there a way to programmatically determine currently installed version of
WinUSB? I searched WinUSB documentation and there is no such API at the WinUSB
DLL level. It seems to depend on WDF version, and how can one find that out
programmatically?
It doesn’t really matter, does it? If you’re going to use WinUSB, you
need to create a driver package with an INF and the WinUSB co-installer,
so you’ll be installing your own version anyway. That ensures that you
will have at least the version you’re shipping, possibly later. If you
can take advantage of a later version, then you should be shipping the
later version.
I don’t see how this information could be of any use.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>Is there a way to programmatically determine currently installed version of
WinUSB?
Can you read the version resource of the binary? GetFileVersionInfoEx should
work eh?
–
David Mott
Disclaimer: This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> Can you read the version resource of the binary?
This is not a robust approach. In some cases the driver in memory can be different than the file on disk such as an installer update that needs a system restart.