Posted By David CampbellProgram Manager
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.
Comments Windows Embedded Compact
Posted By Cuong PhamProduct Manager, Windows Embedded
Today, the Windows team shared that we have started releasing Windows 8.1 to our hardware partners, including Windows Embedded 8.1. This important and exciting milestone builds on the platform alignment we discussed during the release of Windows Embedded 8 by marking Microsoft’s first simultaneous release of Windows across devices – from the smallest tablets to the most lightweight notebooks to versatile 2-in-1s, as well as industry devices and intelligent systems for business.
In a previous blog, we shared that we would deliver updates to Windows Embedded 8, bringing the latest Windows 8.1 innovations to industry devices, in a number of areas: enhanced security, deeper lockdown control, expanded peripheral capabilities, better manageability, updated user experience, and improved connectivity and mobility.
Today, we’d like to share with you how Windows Embedded 8 delivers value through industry devices:
Windows Embedded Standard
Microsoft announced this week that Windows 8.1 will become generally available on October 18. At Windows Embedded, we’re excited to be a part of that announcement, as we continue to extend the power of Windows to industry devices. Building on the aligned release schedule first announced in June during the Windows Embedded 8.1 Industry Release Preview, on October 18 we will also deliver updates to Windows Embedded 8 to our embedded OEMs.
Windows Embedded 8.1 Industry brings the latest Windows 8.1 innovations to industry devices:
To preview the capabilities and innovations in Windows Embedded 8.1 Industry and Windows Embedded 8.1 Pro, download the public preview and evaluate how this modern platform will enable your next intelligent system-ready industry device.
Comments Intelligent Systems
Posted By Jeff WettlauferSr. Technical Product Marketing Manager
In this post, I would like to talk about the advancements we have made with our relationship with Microsoft System Center to manage Windows Embedded devices. As organizations today are looking to integrate intelligent connected devices into their existing distributed infrastructure (AD, Server, System Center), it has become more important than ever to ensure those devices are secure and well managed.
There are some classic challenges with managing embedded devices. I’ll highlight some of those general issues for you first, and then discuss how System Center has addressed these through Service Pack and R2.
Comments Product Updates
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.)