On Sun, 11 Feb 2007 04:50:27 GMT, "mayayana" wrote:
€ > Look guys,
€ >
€ > It has *never* been acceptable to MODIFY files in Program Files.
€ >
€ > Just because it WORKED in earlier version of Window doesn't mean it was
€ *OK*
€ > to do so!
€ >
€
€ We all know Microsoft's party line. What Microsoft
€ decides is "OK" is not particularly relevant here. They
€ designed a product. They sell it. Now people writing
€ software need to decide the best way to deal with it.
€
€ You know perfectly well that Program Files has always
€ been where most software worked out of until recently.
€ (After all, what point would there be to VB's App.Path
€ property if nothing there could be accessed?

And very
€ few people other than corporate lackeys on workstations
€ run XP as anything other than admin.
€
€ It's not as simple as just "going along with the plan".
€ Even if you think that Microsoft's general plan makes
€ sense, it's only geared toward corporate users. Home
€ and small office users want functionality...they don't want
€ frivolous warnings...and they usually don't want settings
€ changing between users. So the challenge is to work
€ out the simplest way to seamlessly allow people to run
€ software that way, as unrestricted for all users.
€
€ I think that everyone wants to try to do that in a
€ standard way that makes it easy for users, but the
€ options in Vista for all-user-accessible software seem
€ to come down to either cutting the security in Program
€ Files or moving everything to All Users App Data. There
€ doesn't seem to be an option that's in accord with what
€ MS officially defines as "OK".
€
Make up your mind. If you want to provide your application with free reign over the system then
disable UAC. Otherwise follow the rules that are implemented in a secure environment and play in
your own sandbox.
Paul
~~~~
Microsoft MVP (Visual Basic)