how to use register selectively

[TraxexPain]

I am looking for a way to create a virtual registry and force only certain programs to use this one? Or to create a virtual Registry but which i can shut down (this registry will be only used while i activate it)?!

Or redirect all querys to another place in the registry
I've seen similar issues. But there is no answer how to use the register selectively!
Open for any help. Appreciate your help.

Greetings.

[weaknessforcats]

You might have a look at the Observer design pattern.

This pattern allows objects to enroll themselves as observers. The enrollment may be managed by mediator object.

Then when an event occurs in a target object, that object can call its Notify() method which wil contact the Mediator object who in turn will pass the event info to all of the observers.

It's like notifying the subscription department that has 50 magazines of a change of address of a subscriber. The address maintenance object senses and address change and gets 50 mailing lists updated automatically.

In your case, your certain object signs up as an Observer and your control object can notify the mediator which passes the info along to the observers as to what registry to use. Similarly, your control object can notify the observers that the registry is not available.

[JulsSmile]

Hi, I had never met such a question. I think it's impossible to use virtual registry selectively.

[TraxexPain]

Thank you, perhaps there are other ideas?

[Jurnero]

Look, maybe this site will help you http://portableapps.com/
I want to ask how you are going to create a virtual registry?

[TraxexPain]

Thank you, what tools do you use to create virtual registry?

[Jurnero]

I know a lot of tools to create a virtual registry. One of the most popular - vmware. As for me, I use boxedapp.
Maybe this link will be useful for you http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

[OldStory]

I do not know how to use a virtual register selectively. But you can use portable applications that do not require entries in the register. What do you think about this?

[TraxexPain]

Thanks, I'll think about it

[OldStory]

Registry virtualization is an application compatibility technology that enables registry write operations that have global impact to be redirected to per-user locations. This redirection is transparent to applications reading from or writing to the registry. It is supported starting with Windows Vista.
This form of virtualization is an interim application compatibility technology; Microsoft intends to remove it from future versions of the Windows operating system as more applications are made compatible with Windows Vista and later versions of Windows. Therefore, it is important that your application does not become dependent on the behavior of registry virtualization in the system.
Virtualization is intended only to provide compatibility for existing applications. Applications designed for Windows Vista and later versions of Windows should not write to sensitive system areas, nor should they rely on virtualization to remedy any problems. When updating existing code to run on Windows Vista and later versions of Windows, developers should ensure that applications only store data in per-user locations or in computer locations within %alluserprofile % that properly use an access control list (ACL).

[TraxexPain]

Thanks for the advice. I think I understand how to implement my plan.
Closed

[JulsSmile]

I think that there is no difference how to use the virtual registry

[OldStory]

If you re interested in this topic again, I want to add. Recently read on the forum that one guy tried to install two identical portable programs simultaneously. It turns out that this is impossible!

[TraxexPain]

Thanks, guys! I have read this topic and now realized my mistake. I can't use the virtual registry selectively. Perhaps only so far

[MoonRider]

Hi!
I thought that a program like microsoft detours will be useful in your case.
!Software developers can use Detours to create an automatic distributed partitioning system. Developers and architects can also use this technology to instrument and analyze the DCOM protocol stack, and to create a thunking layer for a COM-based OS API!