Engine Rules Framework

[GoogleCodeExporter]

The Engine Rule Framework should basically provide users with the ability to 
onfigure specific AccessMechanism values for specific keys, key trees, or 
key values.

Original issue reported on code.google.com by simon.al...@kahosl.be on 9 May 2010 at 10:44

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The following is an overview of what's already done:
r277 - Added the underlying data structures for the engine rule framework.
r278 - Added the registry side implementation of EngineRuleCollectionBase.

Now the engine rule framework is in place, the next step is to implement its 
usage 
in the registry virtualization engine. (the FileSystem is ignored, since a 
major 
rework is pending anyway)
In order to make the engine rule framework usable in the virtualization engine, 
it 
first must be possible to bind the defined rules to each request:
r279 - Introduced RegistryRequest and RegistryValueRequest

The next step is to be able to get the engine rules from the host process to 
the 
guest process, and to make the guest process apply these rules in its 
virtualization 
engine:
r280 - RegistryRuleCollection is now marshaled from host to guest and is now 
used by 
RegistrySwitch.

The collection of rules must also be binded to the virtualized application's 
startup 
data:
r281 - Renamed XmlSerializationHelper to SerializationHelper and made this 
class 
support both XML and binary de/serialization.
r282 - Added RegistryEngineRuleCollection as property to ApplicationSettings, 
which 
is now passed to VirtualProcessStartInfo.

Since the ApplicationData is now binary serialized, it's not possible anymore 
to 
change settings by directly editing the data file. As a solution, a 
configuration UI 
will be introduced in some later revision.
This UI needs to be able to list the engine rules to the user, therefore it's 
made 
possible to enumerate through the collection of rules:
r283 - EngineRuleCollectionBase is now enumerable

Original comment by simon_al...@hotmail.com on 25 May 2010 at 10:30

[GoogleCodeExporter]

The implementation of the Engine Rule Framework is completed,
it now sits in front of the old system which is still used as fall back 
mechanism.

A basic configuration UI is also implemented, users can start this from the 
main window and right before the packaging process is started.
As an example use case we can take the installer of VLC, users can now specify 
that all matches for "%VIDEOLAN%" must only use the virtual registry.
Of course, in a later stage all of this should be made more user-friendly.

Original comment by simon_al...@hotmail.com on 21 Jun 2010 at 3:26

• Changed state: Fixed