Upgrading Vista Non-compliant installed apps

[NewsArchive]

Hopefully this has been addressed and I just couldn't find the
messages....<g>

I have an app that we are finally making Vista compliant. We are modifying
the installer to install data into Common_Appdata for VISTA & 2008 ONLY and
ONLY when installing into ProgramFiles. XP and the like will remain as
before.

I have this resolved in the application. But not in the Setup....

If I detect a Vista and if installed in Program Files I want to install into
CommonAppData.
I also want to move existing datafiles from Program Files to Common Appdata
so the users don't lose anything.
How can I detect this situation?
How can I move the data files?

paul macfarlane

[NewsArchive]

Hi Paul,

This is absolutely no problem. It can be done with a few lines of
SetupScript code.

You say "only for Vista and 2008" (and I assume also for Win7). What do you
do on XP (and prior). Where is the application (configuration) data stored
at the moment (in your non-Vista-aware product)?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

The data is currently with the EXE and a Data folder under the program
install folder.

Some Vista users have installed the app to C:\ ..... So their data is in
C:\MyApp and C:\MyApp\Data

Other have installed to a network drive (ie G ..... So their data is in
G:\MyApp and G:\MyApp\Data

In these cases (especially the network drive case) I do not want to move the
data.

In my app the test is (is it Vista and are we running in CSIDL Program
Files)....

paul macfarlane

[NewsArchive]

Hi Paul,

See what Arnór posted. I thought you wanted to copy application
configuration data to CSIDL_APPDATA and you accidentally wrote
Common_Appdata. If you really meant CSIDL_COMMON_APPDATA, then this will
definitely not work. CSIDL_COMMON_DOCUMENTS is the way to go (and to make
it work from XP in a locked-down environment, you have to give write access
permission to your subdirectory).

Please see:
http://www.lindersoft.com/forums/showthread.php?t=11410

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> definitely not work. CSIDL_COMMON_DOCUMENTS is the way to go (and to make
> it work from XP in a locked-down environment, you have to give write access
> permission to your subdirectory).

Is there an iron clad reason NOT to use a folder in APPDATA and just set the
write access? I know that using everyone for the write access is probably
not a smart thing to do, but that will ONLY give (write) access to that
particular folder.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Is there an iron clad reason NOT to use a folder in APPDATA and just set
> the write access? I know that using everyone for the write access is
> probably not a smart thing to do, but that will ONLY give (write) access
> to that particular folder.

CSIDL_APPDATA (part of the User profile) can only be used to store
user-specific application preferences (per-USER).

CSIDL_COMMON_APPDATA can be used to store application preferences or data
that is not user specific (per-MACHINE). The only "disadvantage" is that
this folder is, by default, hidden (the "Do not show hidden files and
folders" option is enabled by default). You can enable "Show hidden files
and folders" to make it visible. If an application requires Standard Users
to write to that folder, the recommended approach is to create a
subdirectory under CSIDL_COMMON_APPDATA at install-time and give write
access permission to that particular subdirectory. The modified security
should always be documented in the manual.

The advantage of CSIDL_COMMON_DOCUMENTS is that it is *always* visible.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

>
> The advantage of CSIDL_COMMON_DOCUMENTS is that it is *always* visible.
>

And that we do not have to manipulate the ACL for a subdirectory under the
above CSIDL_COMMON_DOCUMENTS (no need to give write access permission) when
running under Vista/2008/Win7.

Friedrich

[NewsArchive]

Not under Vista, but yes (need to change permissions) under XP for ordinary
users

Jane Fleming

[NewsArchive]

Hi Jane,

> Not under Vista, but yes (need to change permissions) under XP for ordinary
> users

I thought we had solved that by setting the permission for the folder under
COMMON_DOCUMENTS to write for everyone? I'm doing that now and so far so
good.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Yes, that's what I meant... in response to Friedrich's saying that not
having to change permissions for Vista users is some kind of advantage to
Common Docs.

You do have to set those permissions for XP users if using Common Documents.
You have to set permissions if using Common Appdata.
Es gibt no free lunch <G>

Jane