Re: Application-installation registry nightmares
From: David White (will@not.give.email)Date: 04/12/02
- Previous message: hongkongwolf: "Re: Blocking internet access"
- In reply to: Erwin Richard: "Re: Application-installation registry nightmares"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "David White" <will@not.give.email> Date: Fri, 12 Apr 2002 09:45:48 +1000
Erwin Richard <erwin@richard.net> wrote in message
news:a949ei$67oj$1@ID-88072.news.dfncis.de...
> - Use the Microsoft Installer Service to install the application
Quite a bit of work here, since it's complex, has many components, and an
InstallShield installation has already been done.
> - During Installation you can only write to LOCAL_MACHINE (in the context
> of Installer Service)
> - Rewrite the Application to store user specific settings under
CURRENT_USER
> provide defaults for these values either hardcoded or in LOCAL_MACHINE
> but
> let CURRENT_USER settings override.
Okay, though I think I might as well have hard coded defaults for
CURRENT_USER in the app and forget about LOCAL_MACHINE altogether.
> Changing the permissions in LOCAL_MACHINE is a bad idea because:
>
> - It does not conform to standard expected behaviour
> - If several users work on the same machine, they probably want different
> user settings for each user.
> - network administrators will not like your application
lol
> - security risk - depending on the information you want to store
Thanks for your suggestion.
David
- Next message: David White: "Re: Application-installation registry nightmares"
- Previous message: hongkongwolf: "Re: Blocking internet access"
- In reply to: Erwin Richard: "Re: Application-installation registry nightmares"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|