Posted By Barb EdsonGeneral Manager, Marketing and Business Development
On the heels of our recent release of the Windows Embedded 8 platform, we’re making another member of the Windows Embedded family available today — Windows Embedded 8 Industry. David Wurster, Microsoft Windows Embedded’s senior product manager, has details on how Windows Embedded has evolved beyond point-of-service (POS) systems in retail to do much more in the Windows 8 era.
A couple of weeks ago, we announced the availability of Windows Embedded 8 Pro and Windows Embedded 8 Standard, bringing a modern OS with tons of capabilities to edge devices within intelligent systems.
Building on that announcement, today we’re making available Windows Embedded 8 Industry. The name reflects a broad scope of possibilities to further expand the Windows Embedded 8 family across a range of industries and targeted intelligent system scenarios.
Comments Windows Embedded Standard
Posted By David CampbellProgram Manager
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.)
Comments Windows Embedded Compact
Posted By Jeff WettlauferSr. Technical Product Marketing Manager
With the release of Windows Embedded 8.1 and our alignment to the Windows code base, a significant amount of new capability and tools are now available. In a recent blog, we talked about management for Windows Embedded; in this post, we’ll focus on deployment.
In the past, deployment for Windows Embedded products was, well, different. There were different tools, processes and procedures for standing up a master image of Windows Embedded. With 8.1, organizations can now use tools like the Assessment and Deployment Kit (ADK) for Windows 8.1, Microsoft Deployment Toolkit 2013 and System Center 2012 R2 Configuration Manager.
Posted By Partha SrinivasanSenior Product Manager
When we launched Windows Embedded Compact 2013 in June 2013, we created an operating system platform well suited for creating small-footprint devices that provide silicon flexibility with real-time capabilities. We also updated the product with the latest tools and technologies by integrating with the latest Visual Studio (at the time, Visual Studio 2012), Compact .Net Framework 3.9 (based on .Net Framework 3.9), and a new compiler with better optimization, networking and cloud capabilities.
Windows Embedded Standard 2011 provides a tool called Image Configuration Editor (ICE) to help developers configure the components to be installed on the run time image. The configuration is stored in XML file format and is called an answer file.
Before creating an answer file, you should gather the hardware configuration of the target device by running TAP.EXE. This will generate a PMQ file. For instructions on how to generate a PMQ file, please refer to the “How to Generate a .PMQ File Using Target Analyzer” section in ICE Help.
Let us go through how to create a simple answer file that represents the configuration to be installed on the run time image.