OverviewFrom my past posts about implementing your own Shell Namespace, there have been some great questions posted by readers.  Many of these stem from the fact that the Namespace example is fairly simple in that it does not implement all of the behavior that is possible in Explorer.  This was done to focus on the core steps in getting ...

OverviewIn my earlier post, I showed how to create a Shell Namespace Extension using the default IShellView implementation (also known as DefView).  One thing you might have noticed from the sample is that the Commands Module is void of even the default items such as “Organize” and “Views”.  If you are developing ...

In the first part of my posts for the IFileOperation interface, I wanted to give an overview of what it is used for and leave the real meat for later.  Now it’s time for the fun stuff.  In this post I want to dig into the use of the IFileOperationProgressSink.   In the MSDN docs for IFileOperation, you will notice that some of ...

In past versions of Windows, when a user encountered a file that is in use by another process, he would be presented with an unfriendly dialog like this:What process is using this file?  What should the user do?  There is nothing actionable for the user on this dialog.  Some savvy users may use a utility to determine which process ...

OverviewWhen implementing a Shell namespace extension, a developer must provide an object that implements the IShellView interface. However, Microsoft® Windows® provides a default implementation of IShellView known as the System Folder View Object (colloquially known as DefView), that can be used in place of a custom implementation. This ...