Quick & Dirty Vista Virtualization Hack
-
I have a legacy app that writes to the program's current working directory, which if the user accepts the default install folder, is under Program Files. Thus Vista's virtualization kicks in. With a single CD install, everything is cool. But because my app can be distributed on multiple CD's (with different sets of content) which are obviously installed sequentially, Vista's virtualization breaks down somehow (not sure how) such that only the most recent content install shows up in the program. While you can hack around it by changing permission settings of the Program Files subfolder, the quick and dirty answer seems to be to simply install the app to a unique folder other than Program Files. Then it works happily. The unintend consequence of Microsoft's paternalism would then seem to be hard disk clutter. :)
-
I have a legacy app that writes to the program's current working directory, which if the user accepts the default install folder, is under Program Files. Thus Vista's virtualization kicks in. With a single CD install, everything is cool. But because my app can be distributed on multiple CD's (with different sets of content) which are obviously installed sequentially, Vista's virtualization breaks down somehow (not sure how) such that only the most recent content install shows up in the program. While you can hack around it by changing permission settings of the Program Files subfolder, the quick and dirty answer seems to be to simply install the app to a unique folder other than Program Files. Then it works happily. The unintend consequence of Microsoft's paternalism would then seem to be hard disk clutter. :)
-
Do you read Raymond Chen's blog? If not I'd suggest doing so :P http://blogs.msdn.com/oldnewthing[^]
There is a lot there. I'm not sure what you think I should be looking for.