Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
ABOUT THE BLOGGER
David CampbellProgram Manager
David Campbell is a Program Manager on the Windows Embedded Compact team. David’s been at Microsoft since 1994 and has spent most of his time working on embedded software and hardware projects.
Posted By David CampbellProgram Manager
At the recent Visual Studio launch event, it was confirmed that Visual Studio 2012 will once again include support for Windows Embedded Compact. Included in that support we’re targeting much of the newest compiler and tools functionality, most notable of which includes new compiler features such as C++11 language standards, faster more efficient code generated, an updated CRT, auto-parallelization and auto-vectorization (Wow, that’s a mouthful.), range based loops, RValue references, and more. Also included will be an updated version of .net CF which has greatly improved performance, particularly around memory allocation and garbage collection - using the “generational” garbage collector. This not only provides more performance, but more predictability in the execution of applications.
More information about the new Visual Studio, including support for Compact, can be found at the Visual Studio Launch site. (Yes, I’m in the video and no, I’m not going to be able to make a living in front of the camera. But it’s the message that’s important here.)
Be sure to check back in the future as we release more information on the upcoming Windows Embedded Compact release.
Comments Windows Embedded Compact
In a previous post, I discussed the Windows Embedded Compact 2013 announcement and a number of great new features in the OS and tools. With those posts, I received a number of questions about the tools. As you all know, Windows Embedded Platform builder (PB) is a plug in to Visual Studio. For Windows Embedded Compact 7, our Platform Builder plug in and tools were hosted by Visual Studio 2008, while Platform Builder in Windows Embedded Compact 2013 will be hosted in Visual Studio 2012. A number of people asked whether PB from Windows Embedded Compact 7 could be hosted in Visual Studio 2012, or alternatively whether PB from Windows Embedded Compact 2013 can target Windows Embedded Compact 7. Unfortunately, the answer to that is no. There had to be significant changes to both Windows Embedded Compact 2013, including PB, as well as Visual Studio 2012 to support the latest versions of each. The hosting has changed, and more importantly, the compilers and ABI (Application Binary Interface) to the ARM chipset has changed and are incompatible with each other. Even though each version of Windows Embedded Compact 7 can target the same chipset in this case, the compilers from each cannot support the other. More information will be posted on this in a future article.
While the Windows Embedded Compact 2013 announcement is certainly exciting, we want to continue posting great information on Windows Embedded Compact 7 as well. To that end, we have another great in-depth article from Doug Boling to share.
Microsoft Platform Builder is a tool that anyone who ports Windows Embedded Compact will live in throughout the project. (PB is also used when creating new device images from scratch. This information certainly applies to that scenario as well.) Given the time spent in this tool, it’s critical that your development machine be properly configured to maximize the performance of the tool and by implication your performance.
Woo hoo, it’s finally time to share more information about the upcoming release! First, the release now officially has a name: Windows Embedded Compact 2013. (I know that folks probably have questions around why we chose this name. We thoroughly considered a long list of potential names, including Windows CE again, and Windows Embedded Compact 2013 really did receive the best response.)
I’ll be doing a number of posts about the various key features and changes in Windows Embedded Compact 2013 over the next few posts, but I want to start with arguably the most interesting of the new features: the investments made for Visual Studio 2012 support, both ISV/app development via Visual Studio directly; and the OEM/device development experience with Platform Builder, now hosted in Visual Studio 2012!
With all development now in Visual Studio 2012, there is no longer a need for multiple versions of Visual Studio to support Compact development alongside other Windows platforms. Plus, you’ll get many of the new features and productivity improvements available in Visual Studio 2012 when developing for Compact! We now have the same C++ toolset and standards supported everywhere. (And of course Visual Studio 2012 includes the new features from Visual Studio 2010, which were not previously to Compact developers.)
I’d like to welcome Doug Boling back as a guest blogger. Doug has another interesting topic this month, the customization of Windows Embedded Compact’s Internet Explorer for Embedded. As a quick introduction again, Doug has been working for many years with Windows Embedded Compact and Windows Embedded CE. He is an author, trainer and consultant specializing in Windows Embedded Compact and CE. Doug also does monthly webcasts on a variety of Windows Embedded Compact topics, like this one, that I would encourage you to check out. You can learn more about Doug by visiting his website at www.bolingconsulting.com.
Windows Embedded Compact has a customized version of Microsoft’s Internet Explorer named Internet Explorer (IE) for Embedded. This powerful browser can be used in a number of ways in an embedded system to enhance the functionality of the system. This post will discuss the various ways to tune, customize and even embed IE for Embedded inside embedded applications.
IE for Embedded is a customized version of Internet Explorer 7 for the desktop with performance enhancements from IE 8 added as well. Specifically, the JScript engine brought from IE 8 provides a 400% performance improvement over the original IE 7 scripting engine. In addition gesture support along with zoom and pan support is in this browser.
Comments Windows Embedded Automotive
He’s back! Doug Boling has once again supplied us with a great write-up for those who missed his July webcast. The topic will be a two-part post. In the first part, Doug details an overview of the three CEPC boot loaders as well as the boot sequence on a PC - which is key to understanding the Windows Embedded Compact process:
It may come as a surprise that the most popular hardware platform for Windows Embedded Compact 7 (WEC) is the standard PC chassis. This is also the hardware platform for Windows Embedded Standard (WES), but Compact 7 brings its own unique features. A properly tuned Compact system can boot faster than WES. Writing drivers is significantly simpler on WEC than on Standard. And of course, there is the dramatically lower licensing cost. This isn’t to say that Windows Embedded Standard isn’t a great operating system, it is. The point is that Compact has a different feature set than Standard and many embedded systems choose Compact over Standard on their embedded PCs.