Next release of Microsoft POS for .NET

Question

Does anyone have any information about a future release of Microsoft POS for .NET? The current version (1.12) is getting old and is causing us grief in .NET 4.0.

As you know by the other posts in this forum, the library uses the now deprecated CAS model. The common workaround is to simply tell the application to use the legacy CAS model in the configuration files, but this prevents us from using other technologies such as dynamic operations in ASP.NET MVC. 

Example error message: "Dynamic operations can only be performed in homogenous AppDomain". 

We're stuck between choosing to set the legacyCasModel="true" (and thus enabling the hardware integration) or setting it to false, breaking the POS but enabling dynamic operations. 

Alternatively, would anyone have any tips on how to load the POS in its own AppDomain (with legacyCasModel=true) separate from that of the main application?

 

Answer 1

Don't hold your breath.

 

Answer 2

Has there been any official statement from the POS for .NET Team? Does anyone know if the team still exists and is active within Microsoft?

Answer 3

It is still active. I hope we see an update with the next release of the UPOS sepc.

-Sean

---

www.sjjmicro.com / www.seanliming.com / www.annabooks.com, Book Author - ProGuide to WES 7, XP Embedded Advanced, WEPOS / POS for .NET Step-by-Step

Answer 4

It sounds like there needs to be a interim hotfix for the issues with .net4.

Do we know when the next UPOS spec is supposed to be released?

Does anyone from Microsoft monitor this forum?

Can anyone point to any statements from Microsoft about current POS for .NET development? We are currently using it, but I have seen software teams at Microsoft disapear before.

Answer 5

Does anyone have any information about a future release of Microsoft POS for .NET? The current version (1.12) is getting old and is causing us grief in .NET 4.0.

As you know by the other posts in this forum, the library uses the now deprecated CAS model. The common workaround is to simply tell the application to use the legacy CAS model in the configuration files, but this prevents us from using other technologies such as dynamic operations in ASP.NET MVC. 

Example error message: "Dynamic operations can only be performed in homogenous AppDomain". 

We're stuck between choosing to set the legacyCasModel="true" (and thus enabling the hardware integration) or setting it to false, breaking the POS but enabling dynamic operations. 

Alternatively, would anyone have any tips on how to load the POS in its own AppDomain (with legacyCasModel=true) separate from that of the main application?

 

Still no news about this issue ?

 

Answer 6

Does anyone from Microsoft POS for .NET going to answer our question?

Answer 7

Please try posting to the POSReady forum: http://social.technet.microsoft.com/Forums/en-US/posready/threads. Maybe Terry will answer the question.

-Sean

---

www.sjjmicro.com / www.seanliming.com / www.annabooks.com, Book Author - ProGuide to WES 7, XP Embedded Advanced, WEPOS / POS for .NET Step-by-Step

Answer 8

Has anyone heard an update on this yet?

It seems there should be a new release that is compatible with .NET 4.0.