Why no registry serach in TD?

[KM]

The question is likely to MS folks.

I am really wondering why component resource search (beside the one with file name) has not been included in TD filtering feature?
Basically, all we know that sometimes a search for a registry path or value that contains a particular word may be helpful
especially if you struggle with Regmon and try to find out all component dynamic dependencies.
If it is not a secret plan, what were the reasons to exclude a search for registry from TD?
All the functionality is there (in XPE database). And it did not take a long time for me to develop a script that does the search
(I've just extended my XPeTools component). Originally I thought it might be hard to do (got that impression from MS replies here
about the lack of the feature) and did not work on it at all. However, when I looked yesterday at the XPe db, it appeared it was not
a big of deal to cover the search for any Resource info (file, registry, data, PnP, etc.). This confused me as I couldn't understand
why it has not been implemented through TD UI.

Thanks,

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

Welcome to the club of missing "so called" difficult features. I think that
many of us already asked for this filter option already

Regards,
Slobodan

The question is likely to MS folks.

I am really wondering why component resource search (beside the one with

file name) has not been included in TD filtering feature?

Basically, all we know that sometimes a search for a registry path or

value that contains a particular word may be helpful

especially if you struggle with Regmon and try to find out all component dynamic dependencies.
If it is not a secret plan, what were the reasons to exclude a search for registry from TD?
All the functionality is there (in XPE database). And it did not take a

long time for me to develop a script that does the search

(I've just extended my XPeTools component). Originally I thought it might

be hard to do (got that impression from MS replies here

about the lack of the feature) and did not work on it at all. However,

when I looked yesterday at the XPe db, it appeared it was not

a big of deal to cover the search for any Resource info (file, registry,

data, PnP, etc.). This confused me as I couldn't understand

 

[KM]

Slobodan,

Are you pessimist? I was just hoping that MS thought the feature was not important to dev.community.
You know the funny thing that is definitely not a big effort to create the filter UI to search for reg.path/value names. I did that
through my XPeTools/DependencyExplorer component (let me know if you would like to play with it and I'll send it to you via email)
but I can pretty easy save a .flt file that I can load, see and use (!) it in TD. I can't, however, change the filter as UI is not
there (TD hangs if I try to open the filter UI). Another inconvenience is I have to re-load TD in order to pick up new filters.

--
Konstantin

Konstantin,

Welcome to the club of missing "so called" difficult features. I think that
many of us already asked for this filter option already

Regards,
Slobodan

The question is likely to MS folks.

I am really wondering why component resource search (beside the one with

file name) has not been included in TD filtering feature?

Basically, all we know that sometimes a search for a registry path or

value that contains a particular word may be helpful

especially if you struggle with Regmon and try to find out all component dynamic dependencies.
If it is not a secret plan, what were the reasons to exclude a search for registry from TD?
All the functionality is there (in XPE database). And it did not take a

long time for me to develop a script that does the search

(I've just extended my XPeTools component). Originally I thought it might

be hard to do (got that impression from MS replies here

about the lack of the feature) and did not work on it at all. However,

when I looked yesterday at the XPe db, it appeared it was not

a big of deal to cover the search for any Resource info (file, registry,

data, PnP, etc.). This confused me as I couldn't understand

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

Are you pessimist?

No I had put wrong words under quote. I meant so say "so called difficult"
but my joke did not sounded well.

You can send me component you made it can be handy form time to time when I
look for reg keys.

Thanks,
Slobodan

Slobodan,

Are you pessimist? I was just hoping that MS thought the feature was

not important to dev.community.

You know the funny thing that is definitely not a big effort to create the

filter UI to search for reg.path/value names. I did that

through my XPeTools/DependencyExplorer component (let me know if you would

like to play with it and I'll send it to you via email)

but I can pretty easy save a .flt file that I can load, see and use (!) it

in TD. I can't, however, change the filter as UI is not

there (TD hangs if I try to open the filter UI). Another inconvenience is

I have to re-load TD in order to pick up new filters.

 

[KM]

Slobodan,

No I had put wrong words under quote. I meant so say "so called difficult"

but my joke did not sounded well.

You can send me component you made it can be handy form time to time when

I look for reg keys.

Sent.

Konstantin