POS for .NET FAQ

  • Article

Q. Is POS for .NET compatible with an OPOS “device”?
A.  POS for .NET is compatible with many legacy OPOS device categories.  See the following posting for a complete list of legacy OPOS device categories that are supported:
https://blogs.msdn.com/pointofservice/archive/2008/12/01/supported-device-categories.aspx

Q. How do we install POS for .NET with our product?
A.  You can invoke the POS for .NET installer from within your installer.  Prior to version 1.12, you were able to invoke the installer from within the compressed archive directly.  In version 1.12, however, you must extract the files first, and then invoke the setup from your installer.  To learn more, refer to the documentation and this blog post:
https://blogs.msdn.com/pointofservice/archive/2008/06/20/installing-pos-for-net-from-your-installer.aspx

Q. What is involved in writing a .NET service object? How do we get started?
A.  It depends on the type of device that you would like to support?  For some devices, we offer base classes that implement most of the UnifiedPOS specific functionality, thus you only need to focus on the communications between the service object and the device.  For other device categories, you can leverage our basic class for much of the functionally but are still responsible for certain aspects of the Unified POS specific functionally.  Finally, you can choose to do everything yourself, in which case you implement the entire class based upon a provided interface.  To help you get started, POS for .NET SDK includes documentation and code for sample service objects.  Also, we’ve posted a Hands-on Lab on the team blog: https://blogs.msdn.com/pointofservice/attachment/8590083.ashx

Q. Will POS for .NET work on Vista Basic edition? Windows Embedded XP?
A.  The License agreement does not extend to these platforms at this time.

Q. Where can I find the service object that I need for a specific device?
A.  You should contact the device manufacture or your vendor to see if they offer a .NET Service Object or a legacy OPOS service object for one of the supported legacy devices.  Anybody is allowed to develop a .NET service object, and there are no requirements to register the service object with Microsoft, thus we don’t have a list available that identifies what devices are compatible with POS for .NET or OPOS.