POS for .NET Architecture
The POS for .NET architecture supports both developers writing POS applications and peripheral device hardware vendors writing .NET-based Service Objects. The following illustration shows the POS for .NET architecture.
The POS for .NET public API provides POS applications with information about connected POS devices. The public API also creates instances of the Service Object (SO) classes for interacting with the devices.
POS for .NET uses Plug and Play for Windows Embedded to detect POS device connection and disconnection. The public API conveys Plug and Play events to the application.
For older applications, the POS for .NET legacy interoperability system exposes legacy OLE for Point of Service (OPOS) controls as .NET Service Objects.
For more information, see POS for .NET API Support.
Hardware vendors write device-specific Service Objects that interact with peripheral hardware. The Service Objects also implement interfaces as specified in the Unified Point of Service (UPOS) standard. With POS for .NET device classes, hardware vendors can concentrate their efforts on implementing the device-specific details.
POS for .NET offers abstract Basic device classes for all of the device types defined in the UPOS specification. The enhanced Basic classes, called Base classes, supply functionality common to all POS devices. In addition, POS for .NET provides abstract Base device classes for nine devices. The Base classes further implement core POS functionality specific to the particular device class.
POS for .NET supplies Base classes for the following devices:
Magnetic Stripe Reader