Developing a Custom Service Object
The POS for .NET SDK delivers support for developing UPOS-compliant applications. The POS for .NET class tree delivers support for both applications that use a specific UPOS device, and Service Objects which provide the link between the physical hardware and the application.
Service Objects are typically implemented by independent hardware vendors (IHVs) to provide an interface between POS for .NET applications and the IHVs particular UPOS device. The POS for .NET SDK includes a set of .NET classes which you can use to create fully functional, UPOS-compliant Service Objects. By taking advantage of the POS for .NET SDK classes, you can write Service Objects quickly and with relatively little device-specific code.
- POS for .NET Service Object Architecture
Presents an overview of the POS for .NET architecture used for building custom Service Objects.
- System Configuration
Provides information about settings and configuration for POS for .NET installations.
- Service Object Samples: Getting Started
Provides a step-by-step guide to creating a functional, multithreaded Service Object.
- Developing Service Objects Using Base Classes
POS for .NET includes a nearly complete Base class implementation for nine POS device types. This section explains how to use these classes as a foundation for device-specific Service Objects.
- Device Input and Events
Explains how events are used to send input from the POS device to the application.
- Device Output Models
Explains the difference between synchronous and asynchronous output to POS devices.
- Asynchronous Output Sample
Implements a simple PosPrinterBase Service Object in order to demonstrate how POS for .NET manages asynchronous output.
- Statistics Sample
Implements a sample Service Object that uses the POS for .NET statistics methods.
- Base Class DirectIO Method
Explains how Service Objects can implement the method DirectIO to provide access to manufacturer-specific data to the application.
- Capability Properties
Demonstrates how certain properties, such as capability properties, are set by the Service Object.