Nonrooted and Rooted Explorers - Win32 Programmer's Reference

Custom Search

Nonrooted and Rooted Explorers

Your namespace extension can be implemented in either of two ways and there is no set criteria for determining which to use. Rather, it depends only on your evaluation of which is more logical and better suited to your particular application.

You can implement your extension so the user can browse into it using the standard Explorer. In this case, your new namespace is presented as a sub-namespace to the system namespace already there. Since the Desktop is the root folder of the system's namespace, it also serves this purpose for your extension. Accordingly, your extension resides within the existing hierarchy of objects on the desktop and appears to the user as just another item in the system namespace.

On the other hand, if you analyze your application and determine that a completely separate namespace makes more sense, you can choose to implement your extension in just this way. However, the user will not be able to browse into it without running a special instance of the Explorer rooted in an item of your choosing. The rooted Explorer's top level is referred to as a junction point. It can be a file or a folder but if the extension uses anything as a junction point, it is by definition "rooted" because the Explorer does not support exploring directly into files.

As noted earlier, whether you choose to implement your extension as rooted or nonrooted is largely situational. There is no hard-and-fast rule. If your extension logically blends into the existing hierarchy of objects, a nonrooted Explorer might be best. If not, it will probably be better to implement a rooted Explorer with a specific file as your entry point to the new namespace,

Last news from Greatis Software

    Nostalgia .Net     .Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More »

Recommended software for developers

    Ultimate Pack     Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More »

    Form Designer .Net     Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More »

    Print Suite .Net     Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More »

    Gradient Controls .Net     Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More »

    Greatis iGrid     iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More »

All the contacts and projects

Dmitry Vasiliev (just.dmitry)

More Online Helps

Win32 Programmer's Reference
Win32 Multimedia Programmer's Reference
OLE Programmer's Reference
Microsoft Windows Pen API Programmer's Reference
Microsoft Windows Sockets 2 Reference
Microsoft Windows Telephony API (TAPI) Programmer's Reference
Unix Manual Pages

greatis just4fun network