Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
A macro component is a component that has dependencies upon other components and has no file or registry resources of its own. Macro components are useful for bundling components that must appear together in a configuration, or for bundling functionality that will be used again.
To create a macro component
- In Component Designer, from the File menu, choose New to create a new component definition (.sld) file. 
- Expand the Windows XP Embedded Client (x86) tree. 
- Right-click Components, and then choose Add a Component. The Component Properties appear in the Details pane. 
- In the Component Properties pane, type the name and description of the macro component, and then select Macro component check box. 
- To create a dependency on another component, follow these steps: - Right-click Component or Group Dependency, and then choose Add and then choose Component Dependency. The Add Component Dependency dialog box appears.
- Select the component you want to include in your macro component from the component list.
- Choose OK.
 
- To create a dependency on a group, follow these steps: - Right-click Component or Group Dependency in the tree, and then choose Add and then choose Group Dependency. The Add Component Dependency dialog box appears.
- Select the group you want to include in your macro from the group list.
- Choose OK.
 
- To allow the components that will be pulled in by this macro component to be optionally excluded from a configuration, in Target Designer, follow these steps: - In the Component Properties pane, for the Prototype field, choose Browse. The Select Prototype Component dialog box appears.
- Under Software\Test & Development, choose Selector Prototype Component.
 
- Save the component definition. 
- Using Component Database Manager, import the macro component into the component database. - The macro component can now be added to a configuration by using Target Designer. When you run a dependency check on the configuration, the components upon which the macro component is dependent will be added as well. 
See Also
Using Macro Components | Macro Components
Last updated on Wednesday, October 18, 2006
© 2006 Microsoft Corporation. All rights reserved.