The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
They simply don't know what to do with embedded. They had a great push in the early 2000's. I started on CE 4.0, delivered products on 4.1, 5.0 and now Windows Embedded Compact 7. Very solid platform.
That said, they had this great idea with .net 2.0 and then later versions to be brought to CE. They made commitments to the developer base, and then abandoned .net support. To say the developer meetings were heated is an understatement. Along about this time, the little company called google started bringing Android to market. The rest is history.
Pulled defeat from the jaws of victory.
And as a side note, what the hell is wrong with Microsoft and their anal desire to constantly rename products?
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
You mean their entire Windows NT based OSs (XP, Win7), with a handful of UI components removed?
Well, you could call them embedded, if you had something the size of a desktop to embed them in!
Or do you mean the weird latest IoT embedded, that run on linux?
I havent seen the former for quite a while, I guess it died. As for the latter it seems to live in the 'Windows IoT' stable, along with what is left of CE and Windows 10 (or 11 as it should be called).
Not quite what you mean, but I'm currently working on a project that's PIC18 (4k ram. OS? LOLWUT!!) on the backend, and UWP on the front.
Other options had been considered for the embedded part including an RPi or some other ARM board running both halves, but time to market requirements on our clients part meant there wasn't time to switch to a new hardware architecture.
Other than needing to add a work queue to avoid race conditions decoding messages when the board is being extra chatty I was able to use the UWP serial IO sample more or less out of the box. Other than being limited to FTDI chips (so no hardware COM port support) the UWP RS232 library has worked great out of the box. After the utter farce that was their implementation in the main .net framework they've apparently managed to get it right this time.
Hm, as an old time (since the 70's) embedded engineer, I've never used a Microsoft embedded OS. By the time CE came out I was already familiar with multiple RTOSes and CE was really lacking compared to the RTOSes I'd used. The CE display side was ok though since the RTOSes I used didn't have any display features built into the RTOS itself. Display for the RTOSes (if any) were in a separate library/module. However, in all my years of embedded development, I've never worked on a device that had a built in display so I never bothered to look at CE. Heck, the device I'm developing for now has, to me, lots of RAM (256k) and FLASH (1Mb). From what I remember of the old Windows CE and and Windows Embedded, it's not going to fit (compact version required 1Mb of RAM) and I'm betting their new IoT system isn't going to fit either. So to finalize, in my 'embedded' world, Microsoft was never in the race.