POS for .NET v1.12 Release Notes

Installing the SDK overwrites SDK source files. If you have changed these files and want to keep them, make sure that you make backup copies of the sample source code files before you install the SDK.

POS for .NET 1.12 supports the UPOS v1.12 Specification. For more information about the new features of UPOS v1.12, see the Release 1.12 section of the Appendix D of the UPOS v1.12 Specification. The UPOS v1.12 Specification can be found at this ARTS Web site.

For information about new and updated POS device classes, see the topic What's New in POS for .NET 1.12 in the documentation.

We recommend using the latest version of POS for .NET. The installed version of POS for .NET can be determined by reading the following registry key:

HKLM/Software/POSfor.NET/Setup/ProductVersion.

Version Check During POS Application or Service Object Setup

When you install POS applications and Service Objects (SOs), it is important to check the version of POS for .NET and make sure that it is compatible.

For example, Service Objects written for UPOS 1.12 must check the platform for POS for .NET version 1.12.*.* or greater. If the current version is incompatible, the installer should block the installation and inform users that they have to install the latest version of POS for .NET.

POS for .NET 1.12 depends on the Microsoft .NET Framework version 2.0. For your application to work, you have to make sure it is loading the version 2.0 of the .NET Framework. There are several ways that you can achieve this:

Recompile your POS application against the .NET Framework 2.0.
Have only the .NET Framework 2.0 installed on your computer.
Add the following content to your application’s Config file (create the file if it does not exist):

<?xml version ="1.0"?>

</startup>

</configuration>

POS for .NET Log File Location

Problem

POS for .NET writes its log file according to a path that is specified in the registry entries. By default, the WMI provider process that uses POS for .NET writes the log to C:\Windows\Temp.

Solution

Inspect both locations. When you try to find the POS for .NET log, the location of the log file may not be intuitive. This is because the POS Device Manager Command Line Tool (POSDM) or another application that uses the WMI provider may have been used, changing the environment path (%TEMP%) that specifies the location of the log. The value of %TEMP% varies depending on the account. Logging should be enabled only when the developer is debugging an SO or an application.

PowerState - Ambiguous Reference

Developers who use this SDK may encounter the following problem when trying to compile existing code:

Problem

Error CS0104 - 'PowerState' is an ambiguous reference between System.Windows.Forms.PowerState and Microsoft.PointOfService.PowerState.

Cause

This error occurs because the .NET Framework version 2.0 has added a new enumeration, System.Windows.Forms.PowerState, that conflicts with Microsoft.PointOfService.PowerState.

Solution

Use the fully qualified name Microsoft.PointOfService.PowerState.

Any additional issues that are found with this release of POS for .NET will be posted as Knowledge Base (KB) articles on the Microsoft Customer Support Web site. To find a list of articles, see this Microsoft Web site and search for "POS for .NET" (include the quotation marks).

Table of Contents

Supported OS Platforms

Development Platforms

Target Platforms (Production)

POS for .NET Updated to UPOS v1.12

POS for .NET Version Compatibility

Version Check During POS Application or Service Object Setup

.NET Framework Compatibility Issues

Known Issues

POS for .NET Log File Location

Problem

Solution

PowerState - Ambiguous Reference

Problem

Cause

Solution

Product Support