What are the different reasons for getting red component?

If that component do not have key path or that component is not assigned to feature,,

Any other reasons?

Answer Summary:
If any component violates any component rules (like one exe, one ocx, one hlp, one dll per component etc... etc.. )then it becomes red component to alert you that this particular component is violating component rule :)
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

4

If any component violates any component rules (like one exe, one ocx, one hlp, one dll per component etc... etc.. )then it becomes red component to alert you that this particular component is violating component rule :)

Answered 07/23/2012 by: jagadeish
Red Belt

Please log in to comment

Answers

0

If that component have HKCU and HKLM enteries then also it will be red.

Answered 07/23/2012 by: vmnit
Third Degree Blue Belt

Please log in to comment
0

May i know in what respect are u getting the red component. Probable reasons are

1. Keypath doesnt exits

2. No associations/incorrect associations in featurecomponent table

3. improper GUID

4. Component having per user and per machine files , even when the component is installing in either per user or per machine location

5. ICE 38, i hope u know what it is related to

6. ICE 43 related to non advertised shortcuts

These are some of the reasons, which can give u red component

 

Answered 07/23/2012 by: talonsprem87
Tenth Degree Black Belt

  • Thanks for your answer. Does 4 point mean that a component must have either hkcu or hklm entries and not both.
  • That means, Per-User and Per-Machines resources should not co-exist in one component
Please log in to comment
0

Take proper training and practice yourself before posting here. Many candidates are just posting questions that are being asked in Interview.

Answered 07/23/2012 by: mekaywe
Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity