Re: Vista and .NET
- From: Andrew <skylogdev@xxxxxxx>
- Date: Sun, 01 Oct 2006 12:31:35 GMT
In article <4514323b@xxxxxxxxxxxxxxxxxxxxxx>, Jon Robertson wrote:
Yes, VirtualStore folders completely break our application in many areas.
Our answer to our customers is that we do not support running our product
on Vista until we've modified our app to accomodate these breakages. And
we won't start on that until after Vista is released.
IMO, the VirtualStore implementation changed between an early beta and
beta 2. There's no reason for us to accomodate Microsoft's changes until
we're sure what the final changes will be. :(
Agreed in principle, but how do you stop users installing older versions of
apps in Vista or simply upgrading their OS to Vista with old apps already
installed? Lots of support issues whatever you do! Anyway, UAC in RC1 has
apparently changed. See my msg to an MS product manager for User Account
Control blog:
'I see that RC1 has, I believe, stopped users from being able to switch UAC
off? If so, that is a step in the right direction - from the Developer's
perspective anyway.
However, there is still a problem when, for example, the user installs new
Vista-compatible versions of our app (over earlier versions existing in the
pre-Vista upgrade OS) which try to copy his data to a new
c:\users\<username>\AppData\<Appname> folder. How does the installation
program know which files to copy to the new location: those in the program
files folder (not accessed since the Vista upgrade), or those in the
VirtualStore folder (accessed since the upgrade)? Still, this is a much
lesser problem than that pertaining to Beta 2!'
.
- Follow-Ups:
- Re: Vista and .NET
- From: Jon Robertson
- Re: Vista and .NET
- From: I.P. Nichols
- Re: Vista and .NET
- Prev by Date: Re: Assembly Reference Problem
- Next by Date: Re: Assembly Reference Problem
- Previous by thread: Delphi 2005 Personal ENGLISH
- Next by thread: Re: Vista and .NET
- Index(es):
Relevant Pages
|
Loading