With the release of Windows Embedded Compact 7 in March 2011, Microsoft stopped making this low cost license available.Therefore, most of the embedded devices developed with Windows CE 6.0 (or earlier) did not migrate to WEC7 (or WEC2013), and even new product designs continued being developed with Windows Embedded CE 6.0 till the end of the Standard support period in April 2013, even though the new versions Windows Embedded Compact 7 or 2013 were available.
Navione Windows Ce 6.0 License Dates SourcedThe majority of this information is sourced directly from Microsoft, with End of License dates sourced from Advantech.
Extended support includes security updates and limited non-security updates. End of License is the date from which runtime licenses can no longer be shipped. The easiest (and likely most effective path) would be to stay with Windows Embedded technologies and migrate to Windows Embedded Compact 7 or 2013. This solution allows most of the application stack to be kept as is, as.NET or Win32 applications developed on Windows CE 6.0 are mostly compatible with the more recent releases. Thus, it is very likely that the hardware architecture of the device would not be compatible with WEC2013 which would imply a significant hardware redesign. With this solution, the main stake relates to the migration of the application layers, which might require significant rewriting. However, there are solutions on the market which can help with minimizing the pain. Navione Windows Ce 6.0 Windows 10 IoT CoreMore specifically, Windows 10 IoT Core application support is limited to UWP, which supports only a subset of the.NET Framework. Therefore, application migration from Windows CE Windows Embedded Compact to Windows 10 IoT Core might be as challenging as to any non-Microsoft OS. Navione Windows Ce 6.0 Full Flexibility ForThere is an extensive number of hardware platforms and architectures supported and full flexibility for OS porting and customization, which allows smooth and efficient OS migration, with probably no risk of HW incompatibility. The current level of market adoption along with the current organization of the open source community allows for a high level of confidence regarding the longevity of the technology. The most challenging part relates to the application migration, but for which there are possible solutions as detailed later on in this article. However, in these cases, there is a very high probability of complete redevelopment of the application due to limited compatibilities between the application framework. An alternate solution in such cases is to consider using Linux RealTime extensions such as Xenomai or RTLinux. Fortunately, there are existing solutions on the market to avoid the need for full redevelopment. This framework allows cross-platform compatibility and is a good way to minimize the migration effort as most of the pre-existing.NET applications running on Windows CE would execute in a Linux or Android environment. However, it might not be a good fit when there are performances challenges, since it obviously introduces an additional intermediate layer that will impact the overall system performance. Using Qt would likely imply some significant redevelopment of an existing.NET application. However, its compatibility with multiple OS architectures such as Linux, Android, QNX, Windows and Windows CE allows having an iterative approach with some potential parallelization of the efforts. Thanks to its cross-platform interoperability, the same Qt application running on the Windows CE-based device would run with the new OS. ![]() Such migration might represent significant investments in the redesign, and therefore should be well thought through to avoid facing the same issues again a few years later.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |