Resolving dependencies -- are they really necessary?

  • Thread starter Thread starter Venkat
  • Start date Start date
V

Venkat

I am trying to improve my boot performance and am following this MSDN
article:

http://msdn.microsoft.com/library/d...l/xeconremovinginternetexplorercomponents.asp

However, when I remove the "Help and Support Services Component",
Target Designer says that the following components require "Help and
Support Services":

"User Interface Core"
"System Restore Core"
"System Restore User"
"Shell Namespace Extensions"
"Remote Assistance Automation Framework"


Clearly I need to have "User Interface Core", but I don't need the
Windows Help services at all -- but do I need to include it so that the
run-time image will work?

In general, is it a requiremet to resolve these dependencies in order
for the image to work?

For example, "Volume Shadow Copy" depends on "Indexing Service", but I
don't need indexing services in my image, so I'm not sure if it's safe
to remove it.

Thanks
 
Venkat,

You can turn off AutoResolve dependency option in TD and ignore some build errors. Then you will get the answer whether you could
remove particular components from the Configuration if the image work fine (meeting your requirements).
In general, is it a requiremet to resolve these dependencies in order
for the image to work?
Click to expand...

It is absolutely hard to say in general what happens with the image if you don't resolve some dependencies. Just think about how
many component combinations are possible out of > 12000 components from database.
You will have to do much testing of your runtime anyway.
 
Venkat ha scritto:
For example, "Volume Shadow Copy" depends on "Indexing Service", but I
don't need indexing services in my image, so I'm not sure if it's safe
to remove it.

Thanks
Click to expand...

For example I've removed "Indexing Service" for my image (about 15 MB of
space required) and it works correctly.


ciao, roby.
 
Back
Top