Hear it from someone who started out writing a shell namespace extension
for the same reasons. It was so hard ro get the SNE to work because there is
so little documentation on it. We ran to problems with auto refresh among
and decided to pull the plug on the SNE and write the GUI from scratch. It
out to be a clean design this way but I recommend against SNE for sure.
It will take you less time to write one from scratch.
>Unfortunately there is no way to build on the default behaviour of explorer
>if you are writing a namespace extension. If you write a namespace
>the functionality is entirely up to you to implement (using the explorer
>interfaces). This is a real pain as there is a lot of code to write just to
>(Please note my e-mail address has been altered to avoid spammers, use the
>address above if you wish to reply)
>>As mentioned in the David's "Extending the Windows Explorer with Name
>>Space Extensions", there are two kinds shell namespace, one is root
>>namespace, the other is nonroot namespace.
>>I have built a SDK sample RegView, I think it creates a nonroot namespace.
>>Because its icon is listed in the Desktop folder. Now I want to make it
>>a root namespace. That is, open a new explorer and can only view the
>>registry view namespace.
>>Further more, I want to build an Explorer-like application, but I don't
>>want to write the total GUI, it is a grind. So I think shell extension
>>by namespace maybe a good option.
>>Any idea/suggestion/information will be appreciated.
>>Thanks in advance.