Breaking Dependency Rules

[Paul Nash]

Hi,

I am still trying unsuccesfully to break some dependency rules between the
base XPE components.

The problem is that I want to add most of the WMI components however I do
not want to add any printing components which WMI seems to depend on. The
"WMI Win32 Provider" component depends on the "Server Printing" component.

When I disable dependency auto resolution and I disable all dependencies
under the resources tab of the "WMI Win32 Provider" I still get the
dependency problem in the task list when I perform "Check Dependencies".

I want to be able to get rid of these tasks so I can do a clean build
without having to skip the "Check Dependencies" step.

Any ideas?

Thanks,

Paul Nash

 

[Slobodan Brcin]

Ideas yes, but MS has to implement them.


You can add all required components, and then for each you can disable
files, reg entries, etc. Very ugly. but it wont complain and your image size
wont be affected.

Slobodan

 

[Paul Nash]

Ok thanks. I tried that and it works fine.

What I find strange is that if I disable all the dependencies for "WMI Win32
Provider" it still says I require "Server Printing". Where are the hidden
dependency rules?

I guess Microsoft is trying to simplify support by reducing the amount of
different allowed configurations.

 

[Slobodan Brcin]

You don't have user interface in TD to change dependencies.
You can make your component in CD with your own dependencies.
But once you import it in data base, you can't influence its dependencies
from TD.

Regards,
Slobodan