UWP Bridges for Retail Applications

Sign in to queue

Description

This session explores two bridging technologies which enable UWP applications on Windows desktop to interact with a wide variety of peripherals used in retail environments. The OPOS Bridge allows your UWP application to interact with OPOS enabled peripherals using the Windows.Devices.PointOfService namespace, while the Desktop Bridge allows you to access even more peripheral types from your application using third party extensions such as OPOS or POS for .NET even if they are not supported in UWP at this time.

Day:

0

Session Type:

Pre-Recorded

Code:

P4050

Embed

Download

The Discussion

  • User profile image
    SB34

    Thanks, for this webcast ! I think that OPOS bridge needs support for more type of devices...

    The link to the sample code doesn't works, and leads to the main POS website :

     https://aka.ms/pointofservice.build2017.samplecode

     

  • User profile image
    MarcusBreda

    @SB34: Thanks for your Feedback SB34, we will check why the fwlink is not working, but you can access the code here: https://github.com/Microsoft/DesktopBridgeToUWP-Samples/tree/master/Samples/DesktopBridgeOPOSscale

    Please be sure to have POS for .net installed to be able to compile the win32 C# classical project.

     

  • User profile image
    MarcusBreda

    Forward link has been updated

    Presentation: https://aka.ms/pointofservice.build2017

    Sample Code: https://aka.ms/pointofservice.build2017.samplecode

    Please submit your feature request for Windows.Devices.PointOfService to https://aka.ms/pointofservice.uservoice.

  • User profile image
    Tim

    Many thanks for this webcast. It has helped me to understand the two different approaches for connecting a USB receipt printer to a UWP app.

    I successfully implemented the Desktop Bridge approach, exactly as per your explanation, and it works perfectly, Unfortunately, as I discovered when the time came to distribute my app, packaging a UWP app with a Win32 background process is a complicated and time-consuming manual process, with no tooling available to automate it.

    So, I decided to try the OPOS Bridge approach (clearly understanding that I would then only be able to target Creators Update). Unfortunately, contrary to your demo, this doesn't work at all; it fails when trying to find and claim the same printer that is working fine using the Desktop Bridge pattern. Specifically, when running your PosPrinter sample app, it throws an exception "A device attached to the system is not functioning" while executing GetFirstDeviceAsync().

    I know the device is functioning correctly, because other apps can access it, so I wonder if there is some additional step required to enable OPOS bridge on Creators Update?

    Thanks, in advance, for your advice.

  • User profile image
    shubham sahu

    Can we use same for usb thumb reader device

Add Your 2 Cents