Namaste Satish Ji, Here I am afraid I cannot help you : extending a .NET modified OpenFileDialog control so it replaces the default operating system OpenFileDialog which is integrated at so many levels deep into the OS, is outside my technical abilities. Which doesn't mean it can't be done. But I think you'll need a "guru" who really knows a lot about COM and the internals of the OS to know if it's possible. I do think the only helpful thing I can say is that you might re-frame your question like this : "How can I take my .NET created/modified OpenFileDialog control, and EXTEND the OS so when I context click on a file or folder I now have an optional menu item that launches my custom OpenFileDialog ?" Since many applications I use every day add something custom to the default OS context-menu, I would start by looking at how they do that, and how, when the menu item is invoked, it is passed, somehow, a reference to what it was invoked (i.e., what was "selected," for example. I would start by searching CodeProject on terms like "Extending," and try and then narrow the search terms down from there; I'd also check out StackOverFlow.com and search there, and, of course, Google on "windows adding a custom menu item" and things like that. good luck, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
