I said `generally` per-machine, I never said that I've never encountered a
situtation where I found opposing approaches. I've written installs for
products that used one, the other or both. For example certain call center
applications that I've packaged required per machine settings and per user
settings to provide the correct information to tie the CRM and Telephony
systems all together. As an aside, our Active Directory model took that
scenario into consideration also. The system also wasn't strictly setup time,
it colloborated with setup and the application via a common pattern and
configuration data attribute classes that describe the implementation of the
data.
For instance, if fired up a new VM from a VM machine type, AD and GPO would
take over at the machine startup script and apply the correct configuration
settings based on OU membership and installed applications. When the user
logged in the logon script would do the same for user settings. The result
would be when you run the application it would be configured.
Jason Swager <[EMAIL PROTECTED]> wrote:
I think you might find that the installation-versus-configuration,
and the per-machine, per-user arguments to be very much based on what sort of
applications you write. Just because you've never encountered a situation
where an opposing approach is more appropriate doesn't invalidate that
approach. Personally, I've found that the majority of client-based apps that I
write need to have per-user settings, so setup is a bad place for
configuration. Likewise, I've found that when writing server applications,
that there is only one configuration, so setup could be used for configuration.
But with virtualization becoming more common in the enterprise apps area
(install once into a virtual image, then reconfigure on every new instance) is
making the setup program a bad place for configuration once again.
Jason Swager
----- Original Message ----
From: Christopher Painter <[EMAIL PROTECTED]>
To: Bob Arnson <[EMAIL PROTECTED]>
Cc: WiX Users <wix-users@lists.sourceforge.net>
Sent: Monday, January 14, 2008 1:11:47 PM
Subject: Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?
I don't agree that installation and configuration are automatically distinct
nor do I agree that configuration is generally per-user. In fact, 12 years of
development, setup authoring and enterprise engineering has convinced me that
it's generally per-machine. Even Windows Installer TAO seems to concede that
per-user stories are a pain to support.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------
Never miss a thing. Make Yahoo your homepage.-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
