How to, or feature wish.

  • Thread starter Thread starter Slobodan Brcin
  • Start date Start date
S

Slobodan Brcin

How to find all component that don't have dependency on them any more?

This would be useful for identifying and removing primitives and other
components that are no longer needed.


Thanks,
Slobodan
 
Thanks Brad,
One way to avoid this is to save your config from start to finish several
different ways. Basically I start with just the results of devices.pmq, then
start to add feature sets (networking,IE,Shell,etc..) and in between each
dependency resolve, and each added component I do a quick save and append a
number to it. As I'm building the runtime I'll use a text document for
reference to the numbering, and archive the document in the final build
folder. I know it's not fixing the problem of orphaned components, but maybe
it will help to keep your runtime a little more organized. HTH,
Click to expand...

I'm doing something like that.

But this was targeted for MS to consider implementing similar feature in
future releases. To ease finding orphaned components.


Best regards,
Slobodan
 
Back
Top