One thing to consider with this type of requirement, is how to define
the scope of "installation"

Many setup developers consider "install" as a much narrower scope than
those who are defining the requirements. Leveraging a configuration
utility on MSI setup completion (via a bootstrapper or the "finish"
button) is still part of the "install" process from a users point of
view.

For example, our installation comes in two flavours...

For retail customers, we provide an interactive installation that
doesn't try to gather any config date, they step through the UI,
install the software and on pressing the "Finish" button we launch a
separate configuration utility.

For corporate customers, we provide a tool to set installation
parameters, then using the Windows Installer API we create an MST
file. The MSI provided to corporate customers doesn't provide any UI,
so the application checks on first run to ensure it's configured
properly and only requires post-install steps as a fallback option for
when information wasn't provided pre-install.

HTH.

Sascha

On Thu, Dec 10, 2009 at 1:46 PM, Castro, Edwin G. (Hillsboro)
<edwin.cas...@fiserv.com> wrote:
> Enter Requirement X: There should be no post-install configuration.
>
> I tell you, these requirement peoples just love to get in the way! ;-)
>
> BTW: I completely agree with you. I'm just pointing out that sometimes we get 
> forced to implement ugly requirements. I have to choose my battles. This one 
> is relatively minor so I don't complain so much.
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
>> -----Original Message-----
>> From: Richard [mailto:legal...@xmission.com]
>> Sent: Wednesday, December 09, 2009 6:19 PM
>> To: wix-users@lists.sourceforge.net
>> Subject: Re: [WiX-users] How Do I Verify Group Membership?
>>
>>
>> <shrug>  I don't think I would try to cram this into the installer.
>> If the installer isn't going to change the group membership, then it
>> shouldn't be gathering the information to query the group membeship.
>>
>> Do it after installation time with a standalone configuration
>> utility.  That way they can change which domain user/group they use
>> at any time.
>> --
>> "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for
>> download
>>  <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-
>> pipeline/>
>>
>>       Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
>>
>> -----------------------------------------------------------------------
>> -------
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to