G
Guest
Hi!
I have a question on this:
A program not intended for Vista get installed with elevated privs. as it
should in the Program Files folder. A user later makes changes to, say, an
INI file by using the applications GUI to make a preference change. The INI
file then get virtualized since the user doesn't have write access to PF. So
far so good.
Later on an administrator updates the application, and the update makes
changes to the original INI file in the PF folder. What happens when the user
logs on again and uses the application? Does Vista present him with his now
OLD copy of the INI file from his VirtualStore OR does Vista recognize the
change and present him with the new INI file that was updated by the
administrator from the PF folder? If the file is the user's virtualized copy,
how does an admin go around updating virtualized files? Does the application
have to be rewritten alltogether to solve this?
I have a question on this:
A program not intended for Vista get installed with elevated privs. as it
should in the Program Files folder. A user later makes changes to, say, an
INI file by using the applications GUI to make a preference change. The INI
file then get virtualized since the user doesn't have write access to PF. So
far so good.
Later on an administrator updates the application, and the update makes
changes to the original INI file in the PF folder. What happens when the user
logs on again and uses the application? Does Vista present him with his now
OLD copy of the INI file from his VirtualStore OR does Vista recognize the
change and present him with the new INI file that was updated by the
administrator from the PF folder? If the file is the user's virtualized copy,
how does an admin go around updating virtualized files? Does the application
have to be rewritten alltogether to solve this?