Microsoft Point of Service for.NET (POS for.NET) is a class library that enables POS developers to apply Microsoft.NET technologies in their products. When installing runtime components, you won't need to install the SDK (that's what is contained in this package). Included in this package are the SDK assemblies and documentation. Microsoft POS for.NET is Microsoft’s implementation of the industry’s Unified Point of Service (UPOS) version 1.12 standards for the.NET platform. Microsoft POS for.NET is also backward compatible with existing implementations of UPOS on the Microsoft Windows platform, named OLE for Point of Service (OPOS).
Symptoms
An application uses Microsoft Point of Service (POS) for .NET 1.12 to claim a device. In this case, applications that are running under a different user account cannot claim this device. When this problem occurs, POS for .NET 1.12 performs incorrect claim logic and incorrectly returns an ArgumentNullException exception. Additionally, successive attempts by the other user account to claim the device fail even after the device is released.
Notes
This problem does not occur if applications that claim the device are running under the same user account.
The ArgumentNullException exception is not the exception that corresponds to the failure that occurs. When this problem occurs, you expect the exception that corresponds to the failure to be returned.
Cause
This problem occurs because only one user account can access the global event that POS for .NET 1.12 uses. POS for .NET 1.12 uses global events to track the status of a device when a service object that uses a named event claims the device.
Note In POS for .NET 1.12, Basic device classes and Base device classes use named events. However, service objects that are based on Basic device classes can provide their own implementation to make sure that only one instance of the device is claimed at any time.
Resolution
Update information
This update provides a security attribute when the global event is created. This security attribute lets multiple user accounts access the global event. If problems occur when an application claims a device, POS for .NET 1.12 performs correct claim logic and then returns exceptions that correspond to the failures that occur.
How to obtain this update
The following file is available for download from the Microsoft Download Center:
Download the update package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
To apply this update, you must be running POS for .NET 1.12.
Registry information
To apply this update, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
File name | File size | Date | Time |
|---|---|---|---|
Kb980087.msp | 78,336 | 01-Feb-2010 | 07:04 |
Status
Microsoft Pos For .net 1.12 Download
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft ships major releases, minor releases, and servicing updates (patches) for .NET 5.0 (and .NET Core) and later versions. This article explains release types, servicing updates, SDK feature bands, support periods, and support options.
Release types
Information about the type of each release is encoded in the version number in the form major.minor.patch.
For example:
- .NET Core 3.0 and NET 5.0 are major releases.
- .NET Core 3.1 is the first minor release after the .NET Core 3.0 major release.
- .NET Core 3.1.7 is the seventh patch for .NET Core 3.1.
Major releases
Major releases include new features, new public API surface area, and bug fixes. Examples include .NET Core 3.0 and .NET 5.0. Due to the nature of the changes, these releases are expected to have breaking changes. Major releases install side by side with previous major releases.
Minor releases
Minor releases also include new features, public API surface area, and bug fixes, and may also have breaking changes. Examples include .NET Core 2.1 and .NET Core 3.1. The difference between these and major releases is that the magnitude of the changes is smaller. An application upgrading from .NET Core 3.0 to 3.1 has a smaller jump to move forward. Minor releases install side by side with previous minor releases.
Servicing updates
Servicing updates (patches) ship almost every month, and these updates carry both security and non-security bug fixes. For example, .NET Core 3.1.8 is the eighth update for .NET Core 3.1. When these updates include security fixes, they're released on 'patch Tuesday', which is always the second Tuesday of the month. Servicing updates are expected to maintain compatibility. Starting with .NET Core 3.1, servicing updates are upgrades that remove the preceding update. For example, the latest servicing update for 3.1 removes the previous 3.1 update upon successful installation.
Feature bands (SDK only)
Versioning for the .NET SDK works slightly differently from the .NET runtime. To align with new Visual Studio releases, .NET SDK updates sometimes include new features or new versions of components like MSBuild and NuGet. These new features or components may be incompatible with the versions that shipped in previous SDK updates for the same major or minor version.
To differentiate such updates, the .NET SDK uses the concept of feature bands. For example, the first .NET Core 3.1 SDK was 3.1.100. This release corresponds to the 3.1.1xx feature band. Feature bands are defined in the hundreds groups in the third section of the version number. For example, 3.1.101 and 3.1.201 are versions in two different feature bands while 3.1.101 and 3.1.199 are in the same feature band. When .NET Core SDK 3.1.101 is installed, .NET Core SDK 3.1.100 is removed from the machine if it exists. When .NET Core SDK 3.1.200 is installed on the same machine, .NET Core SDK 3.1.101 isn't removed.
Runtime roll-forward and compatibility
Major and minor updates install side by side with previous versions. An application built to target a specific major.minor version continues to use that targeted runtime even if a newer version is installed. The app doesn't automatically roll forward to use a newer major.minor version of the runtime unless you opt in for this behavior. An application that was built to target .NET Core 3.0 doesn't automatically start running on .NET Core 3.1. We recommend rebuilding the app and testing against a newer major or minor runtime version before deploying to production. For more information, see Framework-dependent apps roll forward and Self-contained deployment runtime roll forward.
Servicing updates are treated differently from major and minor releases. An application built to target .NET Core 3.1 runs on the 3.1.0 runtime by default. It automatically rolls forward to use a newer 3.1.1 runtime when that servicing update is installed. This behavior is the default because we want security fixes to be used as soon as they're installed without any other action needed. You can opt out from this default roll forward behavior.
.NET Core and .NET 5 version lifecycles
.NET Core, .NET 5, and later versions adopt the modern lifecycle rather than the fixed lifecycle that has been used for .NET Framework releases. Products with fixed lifecycles provide a long fixed period of support, for example, 5 years of mainstream support and another 5 years of extended support. Mainstream support includes security and non-security fixes, while extended support provides security fixes only. Products that adopt a modern lifecycle have a more service-like support model, with shorter support periods and more frequent releases.
This update provides a security attribute when the global event is created. This security attribute lets multiple user accounts access the global event. If problems occur when an application claims a device, POS for .NET 1.12 performs correct claim logic and then returns exceptions that correspond to the failures that occur.
How to obtain this update
The following file is available for download from the Microsoft Download Center:
Download the update package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
To apply this update, you must be running POS for .NET 1.12.
Registry information
To apply this update, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
File name | File size | Date | Time |
|---|---|---|---|
Kb980087.msp | 78,336 | 01-Feb-2010 | 07:04 |
Status
Microsoft Pos For .net 1.12 Download
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft ships major releases, minor releases, and servicing updates (patches) for .NET 5.0 (and .NET Core) and later versions. This article explains release types, servicing updates, SDK feature bands, support periods, and support options.
Release types
Information about the type of each release is encoded in the version number in the form major.minor.patch.
For example:
- .NET Core 3.0 and NET 5.0 are major releases.
- .NET Core 3.1 is the first minor release after the .NET Core 3.0 major release.
- .NET Core 3.1.7 is the seventh patch for .NET Core 3.1.
Major releases
Major releases include new features, new public API surface area, and bug fixes. Examples include .NET Core 3.0 and .NET 5.0. Due to the nature of the changes, these releases are expected to have breaking changes. Major releases install side by side with previous major releases.
Minor releases
Minor releases also include new features, public API surface area, and bug fixes, and may also have breaking changes. Examples include .NET Core 2.1 and .NET Core 3.1. The difference between these and major releases is that the magnitude of the changes is smaller. An application upgrading from .NET Core 3.0 to 3.1 has a smaller jump to move forward. Minor releases install side by side with previous minor releases.
Servicing updates
Servicing updates (patches) ship almost every month, and these updates carry both security and non-security bug fixes. For example, .NET Core 3.1.8 is the eighth update for .NET Core 3.1. When these updates include security fixes, they're released on 'patch Tuesday', which is always the second Tuesday of the month. Servicing updates are expected to maintain compatibility. Starting with .NET Core 3.1, servicing updates are upgrades that remove the preceding update. For example, the latest servicing update for 3.1 removes the previous 3.1 update upon successful installation.
Feature bands (SDK only)
Versioning for the .NET SDK works slightly differently from the .NET runtime. To align with new Visual Studio releases, .NET SDK updates sometimes include new features or new versions of components like MSBuild and NuGet. These new features or components may be incompatible with the versions that shipped in previous SDK updates for the same major or minor version.
To differentiate such updates, the .NET SDK uses the concept of feature bands. For example, the first .NET Core 3.1 SDK was 3.1.100. This release corresponds to the 3.1.1xx feature band. Feature bands are defined in the hundreds groups in the third section of the version number. For example, 3.1.101 and 3.1.201 are versions in two different feature bands while 3.1.101 and 3.1.199 are in the same feature band. When .NET Core SDK 3.1.101 is installed, .NET Core SDK 3.1.100 is removed from the machine if it exists. When .NET Core SDK 3.1.200 is installed on the same machine, .NET Core SDK 3.1.101 isn't removed.
Runtime roll-forward and compatibility
Major and minor updates install side by side with previous versions. An application built to target a specific major.minor version continues to use that targeted runtime even if a newer version is installed. The app doesn't automatically roll forward to use a newer major.minor version of the runtime unless you opt in for this behavior. An application that was built to target .NET Core 3.0 doesn't automatically start running on .NET Core 3.1. We recommend rebuilding the app and testing against a newer major or minor runtime version before deploying to production. For more information, see Framework-dependent apps roll forward and Self-contained deployment runtime roll forward.
Servicing updates are treated differently from major and minor releases. An application built to target .NET Core 3.1 runs on the 3.1.0 runtime by default. It automatically rolls forward to use a newer 3.1.1 runtime when that servicing update is installed. This behavior is the default because we want security fixes to be used as soon as they're installed without any other action needed. You can opt out from this default roll forward behavior.
.NET Core and .NET 5 version lifecycles
.NET Core, .NET 5, and later versions adopt the modern lifecycle rather than the fixed lifecycle that has been used for .NET Framework releases. Products with fixed lifecycles provide a long fixed period of support, for example, 5 years of mainstream support and another 5 years of extended support. Mainstream support includes security and non-security fixes, while extended support provides security fixes only. Products that adopt a modern lifecycle have a more service-like support model, with shorter support periods and more frequent releases.
Release tracks
There are two support tracks for releases:
Current releases
These versions are supported until 3 months after the next major or minor release ships.
Example:
- .NET Core 3.0 shipped in September 2019 and was followed by .NET Core 3.1 in December 2019.
- .NET Core 3.0 support ended in March 2020, 3 months after 3.1 shipped.
Long Term Support (LTS) releases
These versions are supported for a minimum of 3 years, or 1 year after the next LTS release ships if that date is later.
Example:
- .NET Core 2.1 was released in May 2018 and was deemed an LTS release in August 2018.
- .NET Core 3.1 was the next LTS release and was released in December 2019.
- Because August 2021 (3 years) is later than December 2020 (one year after the 3.1 release), .NET Core 2.1 is supported through August 2021.
Releases alternate between LTS and Current, so it's possible for an earlier release to be supported longer than a later release. For example, .NET Core 2.1 is an LTS release with support through August 2021. The 3.0 release shipped more than a year later but went out of support earlier, in December 2019.
Servicing updates ship monthly and include both security and non-security (reliability, compatibility, and stability) fixes. Servicing updates are supported until the next servicing update is released. Servicing updates have runtime roll forward behavior. That means that applications default to running on the latest installed runtime servicing update.
How to choose a release
If you're building a service and expect to continue updating it on a regular basis, then a Current release like .NET 5.0 may be your best option to stay up to date with the latest features .NET has to offer.
If you're building a client application that will be distributed to consumers, stability may be more important than access to the latest features. Your application might need to be supported for a certain period before the consumer can upgrade to the next version of the application. In that case, an LTS release like .NET Core 3.1 might be the right option.
Servicing updates
.NET servicing updates are supported until the next servicing update is released. The release cadence is monthly.
You need to regularly install servicing updates to ensure that your apps are in a secure and supported state. For example, if the latest servicing update for .NET Core 3.1 is 3.1.8 and we ship 3.1.9, then 3.1.8 is no longer the latest. The supported servicing level for 3.1 is then 3.1.9.
Microsoft Pos For .net V 1.12
For information about the latest servicing updates for each major and minor version, see the .NET downloads page.
End of support
End of support refers to the date after which Microsoft no longer provides fixes, updates, or technical assistance for a product version. Before this date, make sure you have moved to using a supported version. Versions that are out of support no longer receive security updates that protect your applications and data.
Supported operating systems
.NET 5 (and .NET Core) and later versions can be run on a range of operating systems. Each of these operating systems has a lifecycle defined by its sponsor organization (for example, Microsoft, Red Hat, or Apple). We take these lifecycle schedules into account when adding and removing support for operating system versions.
When an operating system version goes out of support, we stop testing that version and providing support for that version. Users need to move forward to a supported operating system version to get support.
For more information, see the .NET OS Lifecycle Policy.
Get support
You have a choice between Microsoft assisted support and Community support.
Microsoft support
For assisted support, contact a Microsoft Support Professional.
You need to be on a supported servicing level (the latest available servicing update) to be eligible for support. If a system is running 3.1 and the 3.1.8 servicing update has been released, then 3.1.8 needs to be installed as a first step.
Community support
For community support, see the Community page.
Microsoft Pos .net 1.12 App
See also
For more information, including supported date ranges for each version of .NET Core and for .NET 5, see the Support Policy.
