Re: Writing to registry
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Thu, 19 Jan 2006 09:55:35 -0600
"MikeD" <nobody@xxxxxxxxxxx> wrote in message
news:u0bSWmPHGHA.3200@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Gary Nelson" <gn@xxxxxxxxxx> wrote in message
> news:ek87P9NHGHA.2012@xxxxxxxxxxxxxxxxxxxxxxx
> > Jack,
> >
> > When I do setup I install all of the default keys into
HKEY_LOCAL_MACHINE,
> > and then when a new user starts the program I copy them over to HKCU.
>
> Why? That's just adding even more bloat to the Registry. IMO, it'd be
> better to code defaults in your program. Save non-default values to
> HKEY_CURRENT_USER as needed.
>
> --
> Mike
> Microsoft MVP Visual Basic
>
>
I agree.
One should never ignore the importance of clearly delimiting
properties/attributes/options/defaults as to whether they concern the
Application-at-large or a specific user. Lumping them together only causes
confusion and trouble down the road - when you attempt to administer,
upgrade, or backup the application; when you need to migrate to a multiple
user scenario; or when addressing security issues.
I keep harping on this subject as it one of my biggest pet peeves with OPAs
(Other People's Applications). Applications developed by programmers who
don't recognize the difference become become a PITA to migrate to a
distributed environment.
-ralph
.
- Follow-Ups:
- Re: Writing to registry
- From: Gary Nelson
- Re: Writing to registry
- References:
- Writing to registry
- From: Jack
- Re: Writing to registry
- From: Gary Nelson
- Re: Writing to registry
- From: MikeD
- Writing to registry
- Prev by Date: USB And VB
- Next by Date: Re: USB And VB
- Previous by thread: Re: Writing to registry
- Next by thread: Re: Writing to registry
- Index(es):
Relevant Pages
|