Partager via

Implementation Block

  • Article

The implementation block defines an instance of a component type. The implementation block exists within the scope of a component type block. A component type can have multiple implementation blocks. A component type block is not required to have an implementation block. There is no limit to the number of implementation blocks that a component type block can have. The following code example shows a component type block with an implementation block.

ComponentType(
  Name( MyGWESFeature )
  GUID( <GUID Value> ) 
  Description( "This is the GWES Feature" )
  Implementations(
    Implementation(
        Name( MyComp )
        GUID( <GUID Value> )
        Children( MyChild1 MyChild2 )
        BuildMethods( <See next section> )
    )
  )
)

The following table shows the elements of implementation block sub blocks.

Element Description
Name Element that identifies the name of this specific implementation.
GUID Optional element that supplies the GUID. If the GUID is not present, it is created when the implementation is imported. The default is none.
Description Optional element that describes this feature implementation. The description must be surrounded by quotation marks.
Vendor Optional element that specifies the vendor for this implementation. The default is none.
Date Optional element that specifies the implementation date. The format for date is mm/dd/yy.
Children Optional element that lists child component types by name or GUID. The default is none. You do not need to include quotation marks for a list of children. Any children will automatically be pulled into the platform when a parent is added to the platform. Parent features are added to a platform any time a child is added.
OptionalChildren Optional element that specifies children that contribute to this implementation but are not required for this implementation. An optional child feature will not be pulled into the platform when a parent is added. They must be added manually. Parent features are added to a platform any time an optional child is added.
BuildMethods Element that describes how the implementation is built.
BibInfo Optional element that describes the Project.bib file entries for an implementation.
ExcludeWhenSet Optional element that lists a set of variables that when set (in the platform) cause this implementation to be excluded from the build.
HelpID Optional element that contains the help identifier used for ComponentType lookup in the Platform Builder Help system.
FeatureVariable Optional element that contains the variable that associates this implementation with an operating system feature. The parameter set by this element is the sysgen variable used by the build system.
ImplSize Optional element that contains the physical size of memory that this feature adds to the built platform image.
BSPPlatformDir Optional element that lists the BSP directory with which this implementation is associated. When set, this variable causes this implementation to be shown in the catalog under all BSPs that have the same BSP directory as the BSPPlatformDir variable.
Variable Optional element that specifies any environment variables associated with this feature, using the following format.

Variable( <variable name>, <value> )
Version Element that specifies the version of this feature, using the following format. 
Version( <major version>.<minor version>.<build number>.<update number>)

For features imported with a higher version number than an existing feature, the new feature will replace the existing one. If version numbers are identical, the new BIBInfo and BuildMethod blocks are appended to the existing blocks. If the existing feature has a higher version number, Platform Builder will reject the new feature.
DefaultDrivers Element that specifies the default drivers to use for this feature, using the following format. 
DefaultDrivers( <Implementation GUID (of a driver)> )

Only BSP features should use this element.
Locale Element that specifies the locale of the feature, using the following format.

Locale( 0409 )

See Also

Catalog Feature Files

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.