Article ID: 267369
Article Last Modified on 12/26/2003
APPLIES TO
- Microsoft Windows NT Embedded 4.0
This article was previously published under Q267369
SYMPTOMS
When you use Component Management to add components that have new capabilities, and then you add additional components to those capabilities, Target Designer may display an error message saying that the capability does not exist or that the component cannot be added because the capability already exists.
CAUSE
This problem is caused by the location within the component definition file (KDF) that Component Designer places the new capability.
RESOLUTION
When a capability is added to a KDF, an entry for the capability is created under the All Nodes tree. The new KDF for the subsequent component ("Component 2") does not have this capability entry.
There are two ways to work around this problem:
- Ensure that you add any components with new capabilities before you add other components that also use those capabilities.
- If it is necessary to delete the first component added ("Component 1"), manually add the new capability section to Component 2's KDF by editing the .kdf file.
MORE INFORMATION
Steps to Reproduce Behavior
- Create a new KDF that has both a component (Component 1) and a capability.
- Add this KDF to Target Designer by using Component Management.
- Add Component 1 to an image.
- Add another component (Component 2) under the same capability as added in step 1 in Target Designer. Everything is fine to this point.
Problem Scenario 1:
- Remove Component 1.
- Try to re-add Component 1. Target Designer returns a message that says the component cannot be added because the capability already exists.
Problem Scenario 2:
- Remove both Component 1 and Component 2 under the capability.
- Try to add the Component 2 again. Target Designer displays an error message saying that Component 2 cannot be added because the capability does not exist.
Keywords: kbprb KB267369
