0

I am wondering how I will be able to integrate my KMDF driver into a Universal App. Currently I have the user download a KMDF driver which is used in my desktop application. If I transition to a universal app, how will I be able to use my drivers? Does "Universal Driver" mean it can run in a "Universal App"? How does the phone or xbox download my driver?

I think this is what I gather from my research:

it more relates to the fact it can run on any Microsoft device (Desktop, phone, tablet, xbox). However those devices must be UWP (Universal Windows Platform) which pretty much means they must have at least Windows 10.

The Universal Driver and Universal App are two separate things. The Universal App can implement the Universal Driver, but it can also implement a KMDF driver (but only in a Windows 10 desktop application). A Universal Driver can be used by WPF application (but only on a Windows 10 desktop).

If I turn my application into a Universal App, and change my drivers to be universal, any platform should be able to use my app.

Is this correct?

Still unsure how something besides a desktop runs a Universal Driver.

Seth Kitchen
  • 1,526
  • 19
  • 53

1 Answers1

2

As you surmised, Universal Drivers mean that the drivers can run on any device running Windows 10 (PC, Phone, IoT, etc. -- in theory Xbox as well but that's a closed platform). A Universal Windows App can also run on any device running Windows 10, but it can't contain drivers; drivers must come from Windows Update or from a legacy installer like MSI for the desktop.

Whether or not your Universal App can talk to your Universal Driver depends on whether you need to pass Store certification or not; how the driver is exposed (eg, via HID or something else); etc.

Peter Torr - MSFT
  • 11,824
  • 3
  • 18
  • 51
  • This is exactly what I'm looking for. Could you give some ways to make the driver communicate to the universal app? And how does the driver get to a Phone? – Seth Kitchen Jun 18 '15 at 12:57
  • 1
    Unless you're a phone hardware manufacturer I don't think there's a way to get it onto the phone. What is your driver for? – Peter Torr - MSFT Jun 18 '15 at 18:08
  • One is for USB interaction and the other is for a camera with image processing – Seth Kitchen Jun 18 '15 at 18:15
  • 1
    I don't understand, if we can't put universal drivers on things, what is the point of them? – Seth Kitchen Jun 18 '15 at 18:15
  • 1
    Device drivers are for hardware vendors that make devices. If you build a Widget that goes into PCs, Tablets, Phones, IoT boards, etc. you can write a single driver that works everywhere. Do you manufacture the device and ship to OEMs? – Peter Torr - MSFT Jun 18 '15 at 21:29
  • 1
    If you have an external device, can you use the existing USB APIs to talk to it? – Peter Torr - MSFT Jun 18 '15 at 21:38
  • So even though the driver works everywhere, I can't get it on every device? Can I upload my driver to phones, etc. through USB? We manufacture our device, but we do not want to start manufacturing our own tablet to go with our device. We ship directly to consumer. There is no way to get drivers on existing phones, tablets, etc? – Seth Kitchen Jun 19 '15 at 12:58
  • Is there an MSI for phones that could run through an app? If there is not this seems like a pretty proprietary thing to make. – Seth Kitchen Jun 19 '15 at 13:05
  • Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/81020/discussion-between-peter-torr-msft-and-seth-kitchen). – Peter Torr - MSFT Jun 19 '15 at 16:56