A few years ago, I developed a Silverlight component that is called from an ASP.net web application that uses PInvoke to access USB (serial COM port) on a client machine to allow commands to be sent to some scanner equipment.
With the advent of Windows 10 and the inevitable demise of Silverlight, I am looking for alternatives to accessing hardware on a client PC (this is the entire Intranet web application, where we have a lot of control over the implementation)
I am currently looking at registering an application for a URI scheme (simple solution) according to this page: https://msdn.microsoft.com/library/aa767914(v=vs.85).aspx
OR, alternatively, there may be a Javascript navigator. msLaunchUri (this doesn't seem to be supported on Windows 7, which we need to support) See https://connect.microsoft.com/IE/feedback/details/864863/documented-api-function-navigator-mslaunchuri-not-present- in-windows-7
Registering an application in a URI scheme works fine in Windows 7/8 / 8.1, but it seems to have changed in Windows 10. Does anyone know how I can implement this (via C # code, registry, something) so that Allow to work on Windows 10
source
share