I know about registry virtualisation, but thanks anyway as that was an
interesting and well written article.
However, I don't see how that relates at all to my previous message. How
does this force you to release 32-bit and 64-bit versions of your app
rather than one for any CPU?
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Tony McGee
Sent: Friday, 5 February 2010 10:31 AM
To: ausDotNet
Subject: Re:
Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles)Issue?
http://tinyurl.com/6yfc5c
Welcome to the wacky world of file and registry virtualization
introduced in windows vista.
It's designed for app compatibility but makes things confusing
if you don't know the reason for it
On 05/02/2010, at 11:38, <[email protected]> wrote:
Really? That doesn't sound right to me.
I thought if your app works fine as a 64-bit version for
64-bit hosts then you compile one version of your app with the target as
"Any CPU". It will run as a 64-bit or 32-bit app depending on the host.
If you use the correct system calls for folder paths etc then it will
just work. No need to compile a 64-bit and and 32-bit version.
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Ian Thomas
Sent: Friday, 5 February 2010 9:23 AM
To: 'ausDotNet'
Subject: RE:
Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles)Issue?
Really, you should compile a 64-bit version for
your 64-bit host systems and a 32-bit version for 32-bit hosts.
On a 64-bit system, registry and program files
etc are virtualized so that a 32-bit app "sees" what appears to be a
32-bit Windows. Refer to (amongst many others) Raymond Chen ("Old New
Thing" blog).
However (and it has been said many times before)
you shouldn't be storing your app's working or data files in that
location.
________________________________
Ian Thomas
Victoria Park, Western Australia
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Anthony
Sent: Friday, 5 February 2010 8:32 AM
To: 'ausDotNet'
Subject:
Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles)Issue?
Iam using some
code....Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles
) which apears to return the same path when i use it on an application
deployed by Clickonce or run through VS 2008
But i have noticed that it stores any files
physically on the computer(Windows 7) under
c:\Users\anthony\AppData\Local\VirtualStore\Program Files (x86)\test
When i resolve the address in code the address
is c:\Program Files (x86)\test I think this has been spoken about but
what should i use to be able to store file on any computer in a
consistent way?
Is your website being IntelliXperienced?
<http://www.intellixperience.com/signup.aspx>
regards
Anthony (*12QWERNB*)
Is your website being IntelliXperienced?
No virus found in this incoming message.
Checked by AVG - <http://www.avg.com>
www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2664
- Release Date: 02/05/10 03:35:00
This email is intended for the named recipient only. The information it
contains may be confidential or commercially sensitive. If you are not
the intended recipient you must not reproduce or distribute any part of
this email, disclose its contents to any other party, or take any action
in reliance on it. If you have received this email in error, please
contact the sender immediately and delete the message from your
computer.
This email is intended for the named recipient only. The information it
contains may be confidential or commercially sensitive. If you are not the
intended recipient you must not reproduce or distribute any part of this email,
disclose its contents to any other party, or take any action in reliance on it.
If you have received this email in error, please contact the sender
immediately and delete the message from your computer.
