I would like an additional isolation level, where the program has full access to the file system, but registry changes are virtualized.
Why? Well, many of the programs I would like virtualized are tools for various types of automated file management (mass renaming of files, automated formatting of files, automated sorting of files based on content). Of course, these would be pretty pointless if they can't access the host file system, while at the same time, I do not want any registry entries to creep into the host simply because the program needs to register some ActiveX/COM component.
Probably, it might even be best to have separate isolation level settings for file system and registry.
An additional item on my wish list would be an isolation option for the application to have full access to the host file system, but any changes written to the application's directory (or subdirectories to it) would be virtualized. That way, the application might still access the file system, yet persist settings between machines when run on portable media.
This, of course, is just my personal opinions and ideas, don't feel obliged to listen to them.
As I think of it, perhaps I'm misunderstanding how isolation levels works in regards of the registry.
If I allow the application to modify the registry, how does this work:
1. Everything is written to the "real" registry, including the entries captured during package creation.
2. Entries cuptured during package creation are virtualized, but entries created later, as the program is run from the package, is written to the "real" registry.
