1 / 27

Developing POS Applications with POS for .NET

Developing POS Applications with POS for .NET. Frank Prengel Embedded Developer Evangelist Microsoft Germany. What you will learn. What is WEPOS? WEPOS vs. XP Embedded What is POS for .NET? Using POS for .NET Managing POS Devices. What is WEPOS?. What is WEPOS?.

dara
Télécharger la présentation

Developing POS Applications with POS for .NET

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Developing POS Applicationswith POS for .NET Frank Prengel Embedded Developer Evangelist Microsoft Germany

  2. What you will learn What is WEPOS? WEPOS vs. XP Embedded What is POS for .NET? Using POS for .NET Managing POS Devices

  3. What is WEPOS?

  4. What is WEPOS? • Windows Embedded for Point of Service • XP Embedded leads to different vendors producing different devices and custom images • Great flexibility for embedded systems • POS configuration challenges • WEPOS offers a standard platform for the retail industry and more… • UPOS/OPOS Support – Allows ISVs to write one application for hardware • Offers access to upcoming technologies such as RFID and Biometric scanners • Provides integration to Enterprise solutions • Legacy support provides the best in Total Cost of Ownership (TCO)

  5. What is WEPOS? • Microsoft’s recommended OS for full-featured Point of Service terminals • Point of Sale, Kiosks, Self-Checkout/Checkin, Fuel Pumps, Automated Teller Machines, Security Terminals, etc. • First in a series of Microsoft retail-focused investments that will continue through Windows Vista • Two parts: WEPOS and POS for .NET

  6. WEPOS Features 1/2 • Standard, retail-optimised OS platform for Point of Service devices • Only POS platform to provide Plug-n-Play support for retail peripherals • Based on Windows XP with Service Pack 2 • Provides an Windows XP Pro-like setup • Reduced OS footprint • Extend PC management to POS • Support for standard PC management technologies (SMS, SUS)

  7. WEPOS Features 2/2 • Broad application support • WEPOS retail application verification • Standard SDK with consistent APIs • Comprehensive programming language & technology support: .NET 1.1 & 2.0, Win32, COM, Java, … • UPOS support: • POS for .NET 1.0 (UPOS v1.8) • POS for .NET 1.1 (UPOS v1.9) - New! • UPOS/OPOS - http://www.nrf-arts.org/

  8. WEPOS vs. XP Embedded

  9. WEPOS vs. XP Embedded XPe Database XPe Setup WEPOS Setup Component Designer Installation Options Target Designer Raw Image FBA Transfer To target FBA Install: Updates, Drivers, Apps, Etc. Final Image Final Image

  10. WEPOS Installation Options

  11. Customization • Custom themes, logon screens, splash screens • Changes through standard Window applets and tools, or custom VBscripts • Custom Shells – registry keys • Customer Security • Logon / Splash screens

  12. What is POS for .NET? • SDK to develop POS Applications and service objects in .NET • Run time for WEPOS and Windows XP Professional • Supports .NET Framework 1.1 & 2.0 • POS for .NET 1.1 supports UPOS v1.9 • Abstract POS hardware from the software • Standardise on a logic device name • Change a device without having to recode the application • Plug & Play is at the heart of POS for .NET

  13. POS for .NET • SDK install from WEPOS CD, or web download • Includes support to develop and test applications on XP Pro SP2 or WEPOS • Not supported on XP Embedded • Documentation for .NET Classes and Management tools • Sample code for service objects and applications • POS Device Management command line tools – remote or local management

  14. PosExplorer Application Application InterOp ActiveX OPOS Driver Control Object Service Object Service Object Device Driver POS Device POS Device POS for .NET OPOS POS for .NET Architecture (vs. OPOS)

  15. POS for .NET vs. UPOS • PosExplorer replaces Control Objects • Eliminates CO/SO mismatches • PnP - DeviceAdded/Removed events • Device discovery and instantiation • Integrated with management • Logical device names, default devices, enable/disable devices • Small deviations from UPOS to adhere to the .NET design guidelines • Enums replace constants • Typed arrays replace delimited strings • No in/out parameters

  16. Writing a Service Object • Typically written by device manufacturers and shipped with the device • May be installed by INF or stand alone installer (drag-and-drop) • Derive from either Interface, Basic, or Base class Scanner Scanner Service Object Device Driver Scanner Device

  17. POS for .NET Supported Devices BumpBar MotionSensor RemoteOrderDisplay CashChanger Msr SignatureCapture* CashDrawer PinPad Scale* Cat PointCardRW SmartCardRW CheckScanner PosPower* ToneIndicator* * New for POS for .NET 1.1 CoinDispenser * PosKeyboard FiscalPrinter PosPrinter HardTotals Keylock* LineDisplay Micr*

  18. Writing a Service Object • Interface classes • Abstract classes for each of the 24 UPOS defined device categories (Msr, Scanner, etc.) • Implemented as classes instead of interfaces so we can rev them to match UPOS without breaking clients • Basic classes • Implemented for all 24 device categories • Derive from interface classes • UPOS common functionality fully implemented • Integrated device statistics support • CommonProperties class allows full access to internal properties

  19. Base Classes • Available for: • CashDrawer, CheckScanner, LineDisplay, Msr, PinPad, PosKeyboard, PosPrinter, Scanner • Derive from basic classes • Implement device specific functionality • Easiest way to implement a service object • <DeviceClass>Properties class allows full access to internal properties

  20. Service Object Attributes • *PosAssembly – Assembly contains SO(s) • *ServiceObject – Class implements SO • HardwareID – Maps SO to hardware • Can also use Control Configuration XML file * Required attribute [assembly:PosAssembly("Manufacturer Name")] [ServiceObject("Scanner", "MyScanner", "Description", 1, 9)] [HardwareId(@"HID\Vid_05e0&Pid_1300&Rev_0201")]

  21. SOs & Config: Locations • Put your Service Object DLLs in"%ProgramFiles%\Common Files\Microsoft Shared\Point Of Service\Control Assemblies" • Put your config files in"%ProgramFiles%\Common Files\Microsoft Shared\Point Of Service\Control Configurations" • Configurable in the registry:[HKLM/Software/Pos for .NET]

  22. Device Management • WMI Classes (root\MicrosoftPointOfService) • ServiceObject – Information about installed SO’s • POSDevice – Information about installed devices • LogicalDevice – Alias for POSDevice • DeviceProperty – name/value pair set on POSDevice • Posdm.exe command-line tool • Exposes WMI via command line • MMC snap-in coming in next release • All tools support remote management

  23. What you have learned • WEPOS provides a common platform for Point of Service applications • Simpler to install and support than XPe, but requires some post install manual setup • POS for .NET 1.1 makes it easy to develop UPOS compliant applications using .NET

  24. Resources Windows Embedded for Point of Service homepage: http://www.microsoft.com/windows/embedded/wepos VB.NET example code for app’s and SO’s: http://www.seanliming.com/wepos.html • Product Catalog: • http://www.windowsembeddeddevices.com/wepos • News group support: (msnnews.msn.com) • news:microsoft.public.windows.embedded.pointofservice POS for .NET 1.1 SDK download:http://tinyurl.com/h3wgn

  25. Contact http://blogs.msdn.com/frankpr mailto:frankpr@microsoft.com

  26. Questions ?

  27. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

More Related