Windows Vista Registry Shell Namespace Extensions

Reviewed: 1.0.0 Beta (Nov 09, 2012)

mvallino — Fri, 09 Nov 2012 09:34:11 GMT

Rated 5 Stars (out of 5) - 11 9 12 Too cool. FYI First extract RegNamespace.zip to a folder. Then from that folder extract vcredist_x86.exe to a folder. In this last folder dbl clk vcredist.msi to install the vc2005. Then in the folder where RegNamespace.msi is, dbl clk it. During installation, deselect hide the registry on the desktop check box. Open\explore he registry Icon on the desktop. MichaelJoBillyJimBob

Source code checked in, #94877

Project Collection Service Accounts — Mon, 01 Oct 2012 22:38:35 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #94876

Project Collection Service Accounts — Mon, 01 Oct 2012 22:31:06 GMT

Checked in by server upgrade

Reviewed: 1.0.0 Beta (Sep 22, 2011)

wdwester — Fri, 23 Sep 2011 04:43:00 GMT

Rated 1 Stars (out of 5) - When you attempt to install using setup.exe the file vcredist.msi is not in the extracted files and setup will not continue. RegNamespace.msi will not work either. It will not start the local installer.

New Post: RegPH sample program do not create any entry in the index

fpiette — Mon, 25 Oct 2010 16:11:13 GMT

Hello,

Using VS2008, I have compiled the protocol handler "RegPH" (The version which is in Windows Search SDK). It seems to work but do not create any entry in the index (Running on Windows Vista French, latest updates installed). Compilation went 100% OK. The protocol handler and shell folder are installed and apparently working fine.

I have looked at the eventlog and found a warning saying the content source <reg://{s-1-5-21-1259595494-1951413687-3429671250-1000}/> is not accessible (Exact message is in french because I use a localized Windows Vista). Event ID is 3036. Error code is 0x80040d07.

Maybe it is a permission problem. I have no idea about solving that issue.

Any help appreciated.

Source code checked in, #59559

ChrisGuzak — Sat, 21 Aug 2010 20:19:00 GMT

upgrade solutions to VS2010, some minor syntax cleanup

Created Feature: Update solution files to VS2010 [14054]

ChrisGuzak — Sat, 21 Aug 2010 20:07:33 GMT

Source code checked in, #57274

_TFSSERVICE — Wed, 28 Jul 2010 22:13:23 GMT

Checked in by server upgrade

New Post: Computer windows problem

Pammachio — Sun, 31 Jan 2010 23:15:00 GMT

I all,
I have a problem on my Windows Vista that began afetr the purchase of an external Hard Disk Freecom.
A few days afetr the purchase I disconnected it while it was writing and, since that moment, every time I connect and disconnect it, the PC go to freeze mode for 5 minutes.
The same thing happen even if the hard disk is disconnected: every time I start windows it go to freeze a little after the password, and every time I connect and disconnect a usb device.
I have looked for the solution everywhere, updated windows, unistalled and installed the hard disk from the device manager but I solved the problem only when I restored a recent backup.
Yesterday the Hard disk was writing a backup while Vista was installing the updates; at the end of the proceure windows restarted automatically and the problem began again!!!
The Pc go to freeze when it starts, every time I connect or disconnect the hard disk, an usb earphone that has always worked switch on but there is no audio and I don't know how many others usb devices will have problems.
Has anyone an idea to solve this problem before I throw out of the window Vista or the the hard disk?
Thank you

__________________
Never seen gift like these! (geschenkideen fur on german or ideas para regalos originales on espanol), fotografie matrimoni

New Post: Address Bar/Direct Path Option - One step to perfection?

jonusc — Tue, 13 Oct 2009 08:58:20 GMT

Hello :)

This is a great extension and it's great for browsing the registry. However, the main reason I am greatly interested in this is a quick ability to browse to a specific key - short of manually opening the folder namespace and pasting the Key Path after.

For tinkerers and testers like myself, i'm sure you understand where I'm coming from - when trying to diagnose or inspect any sort of software (via Process Explorer for example) we come across a specific key we need to inspect. For the average tinkerer trying to tweak or fix a windows problem, a support person may query the user on a Registry value to check on and mention the path. It'd be great if there was a super quick way of getting there.

What my point is, how good would it be if I could whack Winkey+R and just paste/type in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\IDE and a new Explorer process would jump straight there? I understand the security concerns of such a thing of course, but it'd be very useful.

I don't know much at all about this kind of programming, but I am reading up on Namespace Extensions to try and achieve exactly this. At first I thought - maybe I could map a drive letter to the Registry Extension....

Browsing the source, I notice references to a reg:// protocol. Trying to fiddle with that via Run command either gives me a catastrophic failure or "No program is registered with this protocol" prompt. Is this related?

Hope someone can give some insight on this one! Until then i'll keep doing my research to see if I can get anywhere with my limited skill.

Definately the best explorer Extension since PowerMenu. Where's the donate link? Someone deserves a beer or two!

New Post: Windows Vista x64

jonusc — Tue, 13 Oct 2009 08:18:37 GMT

Hi Juraj,

The solution converted to VS2008 fine and built successfully after switching the active config from Debug to Release. I recieved an error from WixSetup but of course that was not a critical error, and the built RegNamespace.dll in your copy requires elevation before registering. But both DLL's regsvr32'd fine and I now have the icon successfully visible on my desktop :)

Thanks very much for sharing Juraj! Have you (or the developers) considered making a commit to provide x64 support out of the box? It'd be a good thing to do sometime in the future. Thanks again!

New Post: Windows Vista x64

juraj — Tue, 13 Oct 2009 07:22:49 GMT

Hi,

try my version of the project which is working fine under Vista x64.

You will find the project files here:

http://rapidshare.com/files/292340133/RegNamespace_x64.zip.html

However, in this project I hardcoded the processor architecture in the manifest file and I didn't use pragmas.
But for you just in order to verify whether it's working or not, it should be sufficient that way.

Juraj

New Post: Windows Vista x64

jonusc — Mon, 12 Oct 2009 18:38:41 GMT

Hi guys,

I noticed this thread is over a year old, but I am trying to compile from source for Windows 7 x64 and not having a great amount of luck. Bear with me, i'm only a web developer and scripter and don't have a lot of experience in C(++/#) coding but I can recognize syntax and have a very basic understanding of pointers and methods and whatnot.

I have compiled things in Visual Studio before, although this is the first time I've tried to compile for a 64-bit machine. The last post by juraj seems to cover everything, I have also read articles on 64-bit porting such as the CodeProject C++ 64-bit article here however I encounter errors when trying to register the RegNameSpace DLL.

I am running Visual Studio 2008 with the Windows SDK v7.0 (for Windows 7 x64) integrated. That may be part of the issue. Anywho, in reference to the guide I mentioned above, I have did not find any issues with pointer length and 32>64-bit compatibility (via a recursive Find Text In Files command in UltraEdit) apart from that single size_t variable, so I'm sure it's the architecture setting that I can't figure out. If I simply change my Configuration by copying the Win32 to x64 architecture as outlined on this MSDN article I get the same 'This DLL is not for 64-bit architecture' message or whatever it is when trying to register it. Fair enough, I take it that changing the "processorArchitecture attribute" is more than that. So taking that code you posted juraj and inserting it after (and I tried before) the #pragma once line in stdpch.h under the RegLib project, seems to build a correct x64 DLL. However, I get this error in Event Log:

Activation context generation failed for "S:\Storage\Software - Windows 7\Registry Shell Namespace Extension\RegNamespace_x64\RegNamespace\x64\Release\RegNamespace.dll".
Error in manifest or policy file "" on line . 
A component version required by the application conflicts with another component version already active. Conflicting components are:. 
Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6.manifest. 
Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc.manifest.

I understand that it's basically conflicting between the 32-bit and 64-bit comctl32.dll but I have no idea how to resolve it =( My not-so-educated guess is that these "preprocessor pragmas" should be put somewhere else instead...? If someone could give me a tip or has any ideas, I'd be very grateful - I have missed using this extension since moving from Vista 32-bit to 7 64-bit very much. I have subscribed to this thread via E-Mail and look forward to replies.

Thank you for the great explorer extension you've created.

New Post: How search in NSE works

lsag — Thu, 17 Sep 2009 14:33:35 GMT

Can you please explain to me how Windows search searches NSE? I was unable to figure out when search protocol is invoked when I search for any data in Windows registry NSE. I though Windows search would use properties and PKEY_Search_Content particularly to perform deep search inside NSE. Does it search recursively?

Also when I go into Vista main search it does not seem to include NSE in search.

Updated Wiki: Overview

ChrisGuzak — Mon, 29 Jun 2009 01:19:57 GMT

Intro
Windows developers, and especially those with an interest in developing Shell data sources (namespace extensions) are probably familiar with the original Shell namespace extension sample RegView. This project is an attempt to bring that sample into the Vista era of programming and demonstrates some of the key advances available in the Vista platform.

Also note that the Windows 7 has a modern data source sample installed here:
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\Shell\shellextensibility\explorerdataprovider

Project Structure
The solution consists of three subprojects:

RegNamespace - Implements all of the Shell namespace objects including the data source (IShellFolder2), the view (via SHCreateShellFolderView with an implementation of IShellFolderViewCB), the property store factory, and various other pieces, which will be discussed in more detail in other sections of this wiki.
RegPH - Implements the protocal handler and filter for the registry data source. This allows Windows Search to index the content of the registry.
RegLib - A static library of utilities shared between the other two projects.

Created Release: 1.1.0 Beta (Jun 04, 2009)

thayn — Thu, 04 Jun 2009 21:03:27 GMT

This is primarily a collection of bug fixes. It also allows this sample to run on Windows 7. More bug fixes and changes for Windows 7 to come.

Released: 1.1.0 Beta (Jun 04, 2009)

Thu, 04 Jun 2009 21:03:26 GMT

This is primarily a collection of bug fixes. It also allows this sample to run on Windows 7. More bug fixes and changes for Windows 7 to come.

New Post: Vista Sync Handler and IShellItem2

pete0815 — Tue, 21 Apr 2009 05:48:37 GMT

hi
Sorry but it seems i cannot help you cause i used the interfaces in c++ but i think if you should be able to connect via c#. there should be no reason why you cannot connect from c# cause mobsync would connect via com. do you have registered your sync handler and handler collection and updated thoses infos in HKLM\Software\Microsoft\Windows\CurrentVersion\SyncMgr? as far as i know you don't need the collection handler but you need to register the info in the apporp. registry key.

gl and cya
pete

New Post: Vista Sync Handler and IShellItem2

masique — Fri, 17 Apr 2009 05:48:53 GMT

Helo, It is kind of off-topic, but I also was playing with ISyncMgrHandler and legacy ISyncMgrSynchronize. Do you using this interfaces from C# ? I have trouble to connect throught new ISyncMgrHandler with C# on Vista. But old ISyncMgrSynchronize works well on both Windows XP and Vista.

New Post: IPropertyStore vs. IFilter

rlrcstr — Sat, 03 Jan 2009 06:50:02 GMT

Matt, Jerry -

Hopefully you guys are still monitoring this thread... I've got a project where I'm building an IFilter for a file format based on the Microsoft Exchange journaling feature which, in turn, is based on the .eml file format. So I register a new file extension (.jeml) and created an IFilter for it. The filter emits a series of properties specific to the journal envelope and then feeds the rest of the document through the standard .eml IFilter (mimefilt.dll). Everything seems to run just fine when I test with FiltDump.exe. But getting the filter to run in the context of Explorer.exe or general desktop indexing seems to be an issue.

As far as I can tell, I've got all the proper registry entries, but the system never loads my filter.

For standard indexing for WDS, I don't have to implement IPropertyStore or create a separate property handler if I've got the fill IFilter interface implemented, do I. What's the point of IFilter::GetValue, if I still have to implement the other interface?

Any clarification you can lend here would be much appreciated. I feel like I'm so close to getting this thing up and running, but I'm missing one tiny bit...

Thanks.

J