I don't want to hijack the list but your understanding of IntallScript is
outdated by nearly a half decade. InstallShield hasn't required you to
bootstrap the InstallScript engine for about 5 releases now. Also you
don't even have to use InstallScript with Basic MSI projects and I don't. I
tend to use WiXExtensions and C#/DTF custom actions now and only when
absolutely
needed.
If you are talking about legacy InstallScript projects, I don't use that
anymore
either. I prefer the declarative approach of Windows Installer using either
WiX or InstallShield as my authoring tool. I don't like NSIS because it's
a procedural programming language that goes against leverage the benefits of
Windows Installer. The same can be said of legacy InstallScript projects.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
----- Original Message ----
From: Bruce Cran <br...@cran.org.uk>
To: General discussion for Windows Installer XML toolset.
<wix-users@lists.sourceforge.net>
Cc: chr...@deploymentengineering.com
Sent: Tue, August 31, 2010 8:49:20 AM
Subject: Re: [WiX-users] Bootstrapping and Burn
On Tue, 31 Aug 2010 06:22:56 -0700 (PDT)
Christopher Painter <chr...@deploymentengineering.com> wrote:
> NSIS? Sorry, I'd rather go to the dentist.
You *really* don't like it, do you? :)
I don't understand why not; I consider it better than InstallShield for
example where you end up having to install InstallScript engine updates
before you can even launch the main installer.
--
Bruce Cran
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
