LPGPU2-CodeXL | LPGPU2 CodeXL power performance analysis and feedback tool | GPU library

After doing a bit more research, the answer to all of these questions...is yes!

Given that Microsoft states that all of private application hives loaded from RegLoadAppKey must use the original handle obtained when opening the hive, I was very curious as to how Visual Studio was achieving this, considering I couldn't see any references to such a handle anywhere, yet when I stepped over registry functions in WinDbg, Process Monitor reported that the private hive had been accessed.

After stepping into these functions I discovered that actually Visual Studio detours all of the Win32 registry functions to its own special handler that determines whether or not it needs to redirect the function call.

As such, we can conclude

• Any attempts to access Visual Studio registry keys will automatically be redirected to Visual Studio's private application hive, if required

This still leaves us with the problem of having to construct the root Visual Studio key in the first place. As it turns out, you can use the VSRegistry.RegistryRoot method to gain a reference to various configuration stores (although only user and configuration types are actually supported)

And so, we can get a reference to the user's configuration key via