shell-extensions

I am developing namespace extension which gives a virtual view of files on a server. In this view, I need to provide different states(in use, offline, out of sync, etc) of a file using overlay icons. I was read through article implementing overlay handler, and thought I will try to handle this in one of our overlay handlers, which implement IShellIconOverlayIdentifier interface. I see that IShellIconOverlayIdentifier::IsMemberOf(), and other functions are called only when I access files on normal filesystem, i.e., c:\, d:\ etc. When I browse a namespace extension, these calls are not called at

I'm looking for a programmatic way to prompt the user for filenames using the explorer shell and I only want system shell extensions loaded. The reason I'm looking for this feature is that I want to eliminate 3rd party shell extension as a possible cause for crashes and other nondeterministic behavior. Ideally, there's a flag somewhere that I missed that I can pass in to a function that means something like a "safe mode" for an explorer instance where it only loads the system shell extensions. This seems like such an essential feature and I've spent a good amount of time poring over docs to

For a shell extension (UI is similar to "New/" context menu), I need to create a file, select it and enter "rename" mode, so the user can adjust the default name. Q: How do I enter "rename" mode for a file? The correct way to do this is to use IShellView::SelectItem with the SVSI_EDIT flag. Have you tried sending "F2" to the window? 来源： https://stackoverflow.com/questions/6258846/windows-explorer-shell-extension-create-file-and-enter-rename-mode

The recommendation used to be "Do not write in-process shell extensions in managed code." But with .NET Framework 4 and In-Process Side-by-Side the main reason not to write shell extensions in managed code should be resolved. With that said, I have three questions. Is it now okay to write shell extensions in managed code? Which problems, if any might there be with writing shell extensions in managed code? What reasons might there be to write shell extensions in unmanaged code? It is now OK to write shell extensions in .NET 4 managed code. You should still avoid writing shell extensions in .NET