Switch to MSIX so that you can use all the WinRT APIs via Windows 10 WinRT API Packs NET Core based inter-app com process like the 2 examples for older Windows SDKs above) Switch to from Microsoft POS partially and get Microsoft POS to work on. Hope you get OPOS Bridge working or somehow get BrokeredPointOfService to work. The previous migration path (Windows 8 or 10 2015) was:ĭump existing code and switch to UWP with NET Core for specific peripherals but that is about it. People have come out with their own libraries for. Probably got to do with the UnifiedPOS 2.0 standard being a "WIP" since 2017 - perhaps you have some questions to ask from OMG also. The update in 2017 seemed to be the only update to it since 2014. And who knows for how long MAUI will *it* until Microsoft replaces *it* with something else.īut again, I really appreciate your help, thanks a lot although the sarcasm felt a bit unnecessary. Xamarin.Forms has improved *a lot* in the past 4 months but it is far behind other cross-platform alternatives. MAUI looks great and I was super excited for it until I read that it won't be ready until probably mid-late 2021. The only thing I don't agree with you is Xamarin. Maybe the problem is with Toshiba but the majority of our clients user TCx. NET Core 3 PosPrinter sample, it found all the Epson printers in the office but not a single Toshiba printer. NET Core 3.0, with platform extension it was a breeze but we were not successful at connecting to any OPOS/UPOS peripherals. We did some experiments porting our product to. Our entire business logic lib is running on. Thank you for taking the time to share your thoughts, very informative and we'll have to give gRPC a better look! ![]() Also, maybe I missed something and this is all just a big misunderstanding, but the problems we are facing now will only get worse so I just wanted to see what developers in the same field are thinking or how they are planning the future (primarily connecting to OPOS peripherals and supporting "legacy" Windows 10 versions). I'm not trying to be negative, I love C# and our software was build using the best tools as the time. As my name suggests I'm not a fan of Xamarin and it seems not even Microsoft likes it as they rewrote the entire Office Suite in React Native. NET 5 (and later 6) is supposed to unify the whole fiasco but I honestly don't trust it. I don't know how many frameworks Microsoft has released in the past decade but they aren't few. What frightens us the most is that Microsoft's vision is blurred. WinUI 3.0 minimum requirement is Windows 10 1803, about 40% of our clients have Windows 10 LSTB 2015-17 so version 1507-1703. There are of course *ways* to install UWP on LTSB but we are not guiding our clients to do some PowerShell hacks. UWP sounds like great fun but LTSB (on basically all high-end POS hardware) doesn't support "App Installer" (Windows Store) that is used to install UWP applications. Windows 10 isn't the same as Windows 10, there are multiple versions of it. NET 5 was probably the right thing to do and here the fun begins. NET Framework 4.8 (we are supporting two versions of our software).Īfter a little research, we figured migrating to. ![]() NET will not receive further updates and we are already having issues with Windows 10 LTSB/LTSC 2015 as it doesn't support. NET (OPOS/UPOS) to use peripheral devices like receipt printers (mainly Toshiba and Epson), line displays, cash drawers, scales, etc. I'm working for a small software developer, our main product Point-of-Sale software.Īs of today, our main product uses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |