We're getting ready to launch a blog for Windows Embedded for Point of Service and POS for .NET.
Stay tuned...
- Shayna
Why not focus on SO's.
Just a frustrated programmer’s question.
I understand the dedication to UPOS, but I’ve been working with the Pos.net and WEPOS for quite some time now, and I’m more interested in the support for (previously) OPOS devices then just another Pos.Net.
Why are Pos.Net and or WEPOS not more like the other Os’es.
I’ve been struggling with Star micronics for quite some time now, but I can’t seem to get through to them. Their Opos drivers are outdated, their WEPOS doesn’t support the new printers like TSP100 futureprint, but there advertising suggests otherwise.
Why aren’t Pos.net / WEPOS, supporting (like an ordinary Windows) a set of default SO’s. Nothing fancy, just printing and a cash drawer, even the shim solution is an option.
What’s the point in releasing Pos.Net 1.1.1, when there is no support from the industry?
Star is a major player in the market, but their efforts towards POS.Net, UPOS and WEPOS is dragging. The only answer I get on my emails is; “We are currently looking into it.”
Why not choose Epson, you might say? Well the answer to that’s easy. The customer has a set of rules outlined, so working in a model restricts that choice. Then try to convince them that the choices they’ve made are the wrong ones.
Star micronics, Opos, Jpos, ESC/POS, we support everything. (as long as it’s legacy). MS POS.Net the solution for the Retail. The customer baffled by those marketing slogans, chooses the right (hopeful) direction. After some deep digging and bilateral hanky panky, the system designers drop their rulebook on your table and wish you all the best.
Is it possible for the POS.Net team to trigger the common sense of the Star (and other hardware vendors) mind. Just to put more effort into the development of SO’s? Or if that’s not working, could develop a set of / or a SO for the most (Pos)common devices. It would really help me a lot.
We will talk to Star Micronics and try to spark their interest for POS for .NET.
In the meantime, have you tried to install their OPOS driver and use the Legacy Interop capabilities of POS for .NET? POS for .NET Legacy Interop lets you "wrap" OPOS Control Objects (CO) and exposes them to POS for .NET. (Note: not all device classes are Interop capable.)
Thanks for the reply.
No haven't tried that one. Is there an example of how to use those capabilities. Or is it as simple as using the Legacy Bool in the device class, and the rest stays the same.
In most cases, you just need to install the OPOS driver and then configure the OPOS driver for your device using the Star provided utility (if required). Once this is done, POS for .NET should recognize the device as a "Legacy" device and enumerate it like any other.
