in message | >I haven't delved into the beast that is Vista from a programming
standpoint
| >yet. But, if the blog at
http://west-wind.com/WebLog/posts/4983.aspx is
| >any indication of what we're in for.....I say we all refuse to deploy
this
| >monstrosity and make Redmond get it right.
| >
| > There is NO WAY people are going to go for a system this locked down.
| > Never....ever........ever!
|
| You are absolutely right.
| Let's drop windows everywhere, install linux and spend billions of euros
| porting applications, based on 1 blog post with information about a
product
| that has not even been released yet, only to discover that linux is locked
| down even tighter by default.
|
| The issues mentioned there are mostly due to earlier bad design. Users
| having RW access to program files is considered OK?
| After years of bad press, Microsoft are finally locking down the OS, and
lo
| and behold: OMG my applications that were not developed for an OS that has
| not yet been released have compatibility problems. Sue!! Bring out the
| pitchforks!! It is a conspiracy!!!
|
| Well Boohoo.
|
| Of course there will be compat problems.
| And most of them are caused by bad design, and will have to be fixed by
the
| app devs themselves.
| Some are caused by bugs in Vista, and will have to be fixed before Vista
| goes gold, which is still over 4 months away.
|
| --
Funny that the Blog concludes with "the OS being crappy" while in fact it's
the application being crappy (10 years old FoxPro?) probably designed for a
'crappy?' OS called W9X having administrative dependencies.
Such legacy applications can indicate that they want to perform 'legitimate'
administrative operations by implementing an application manifest.
The issue with writing to a config file is not valid either, Vista uses
something called virtualization which redirect writes to a per-user location
when the account is restricted.
Another point he is missing is that it's still possible to run as local
administrator (which is disabled by default), something he obviously does
when running on XP because "users" don't have write access privileges on
"Program Files". But that doesn't change the issue, it's Foxpro which is to
blame not the OS (Vista or XP).
Developers should carefully read all they can about UAC (something the blog
poster failed to do) and run the "Microsoft Standard User Analyzer" in order
to identify the administrative dependencies of their applications, this will
allow them to take some corrective measures, or at least to provide a
manifest for their applications.
Willy.
