Windows Embedded Compatible Applications Chooser FAQ

Image Configuration Editor (ICE) is one of the tools that are included in the Standard 7 toolkit. You can use ICE to create answer files or configuration sets from scratch or using a template. You can then use the answer file or configuration set with IBW or a deployment service to install your custom image onto an embedded device.

You can use Image Builder Wizard (IBW) to quickly and easily install Standard 7 on your target device. You can select the necessary components yourself or use an answer file that includes the necessary component and feature package information.

An application template is an XML file that contains feature packages that are first-level dependencies of the application the template supports.

You use templates with ICE. You can download a template from the Web site and use the XML Merge functionality in ICE to combine the application template with your existing answer file. This creates a new answer file that includes everything in your original answer file, plus any additional component and feature package information that is required to support that application. You can also use the template without merging it with another template, by resolving all its dependencies, and turning it into an answer file.

For more information about how to create a template, please see this white paper.

Both are XML files that contain components and feature packages. The main difference is the level of dependencies that have been resolved. Application templates only include first-level dependencies needed for a particular application. Answer files have all dependencies fully resolved in ICE and include all required dependencies to install Standard 7 using the ‘Deploy an Answer File’ option in IBW. In addition, an application template has not been fully resolved and cannot create a Standard 7 installation using IBW.

Components are groups of Windows binaries that all perform a certain function and feature packages are groups of components that correspond to a certain feature or Windows-based application. . Examples include of feature packages IIS, Internet Explorer, or Windows Media Player. Components control or provide certain functionality within those feature packages. Dependencies are the packages that are required for a certain component or feature package to work. For example, Message Queuing has a dependency on IIS, because it relies on a component in IIS for some if its functionality. To learn more about Windows Embedded Standard 7 technical details please visit the development pages for Standard.

Determining the dependencies of a particular application can sometimes be a long and painful process. If you are a developer or OEM, we can help save you time and money by doing the analysis for you and providing a template you can use in ICE. If you are a software vendor (ISV), you can work with us to help create a template for your application and make it easier for developers to include your application on the images they create.

Although we have not created templates for all applications that may be useful to our customers, we are continually adding new templates. If you do not find the template you are looking for, please contact us at wesatt@microsoft.com. We will consider adding the application to our growing list of templates. We can also work with you to help you create the template yourself.

The primary audience will be developers, whether they are working for large OEMs or they are hobbyists. These are the people using ICE to create Windows Embedded images and we want to help make their life as easy as possible.

A team at Microsoft creates many of the templates. We have also collaborated with several ISVs to create additional templates that are also available on the Web site.

Although we are considering adding that functionality in the future, currently all templates are posted by Microsoft. However, if you want to have your template included, please contact us at wesatt@microsoft.com.

Dependency analysis can frequently be complex and difficult task. Therefore, we are striving to make it as easy as possible for our customers. Currently, ICE includes a tool named Static Dependency Analyzer (SDA) that maps all static dependencies to Standard 7 components so that you can include them in your template or answer file. You can use tools such as Process Monitor to analyze dynamic dependencies and track which binaries and registry keys are touched while the application is running. To learn more about dependency analysis, please read this white paper.