If you want an example of how **not** to do an installer the SQL Server is
the one to go for! It is not the Windows Installer parts that are bad it
is the bootstrapped that warps it all up.
I had SQL server Express 2012 on my server a few months ago, had to
uninstall it to clear out some errors,
He's just installing the product itself and I think that it downloads .net if
not already installed. I talked to him about it last night, and he said that
because it was crunch time and beta time, he simply wanted a quick solution
with less of a learning curve in order to get the product out
Oh really? Nasty; I mean, why not just use a standard UI for that anyway
rather than that very complicated and non user friendly interface? I'm not
talking about accessibility here; some sighted individuals struggle with it as
well. Maybe we should talk to them about that? I tried over on
On 05/10/2012 17:23, Katherine Moss wrote:
Oh really? Nasty; I mean, why not just use a standard UI for that anyway
rather than that very complicated and non user friendly interface? I'm not
talking about accessibility here; some sighted individuals struggle with it
as well. Maybe we
Hi guys,
Since I am just learning to be a .NET C# programmer, can somebody shed light on
why using WiX over something like Inno would be more complicated and why
programmers are often less compelled to use WiX? I'm asking this because my
friend has got a project he's working on where the main
Hey Katherine,
For the past 20 years I have been using various InstallShield products,
InstallAware, Wise Studio etc...
When I first found out the company I work for was using WIX I shuddered... but
now after using it for 5 weeks it's pretty good (and free), there have been
some hiccups but
I don't know much about Inno, but reasons for us to use MSI include:
- rollbacks
- patches (i.e., replacing less than full files), including with rollbacks
- logging
- integrates with Windows directly
- and, maybe in the future, SCCM connections
- Visual Studio integration (not as important now,
Yeah; I know all about this, though I'll be learning more. And what you said
about VS integration, you guys should develop full integration with VS; all
project types including patches and what not, dialogue editors, and wizards.
But anyway, that's another topic for another day. Well, I
I would argue that developing MSI with wix is a little bit more complicated
than developing in c# or other scripting language at the beginning, because
programmers which use to tell the compiler How to do things now need to
use declarative language and tell the compiler What to do
Some
Don't forget validation (ICE's) and support for existing and future platforms.
If you utilize the Burn approach for any (limited) customization to the
installation and simply property drive your MSI's then they become incredibly
simple to manage (over some custom script that may or may not work
Hmmm COM is love? I always thought COM was COMplicated... lol.
-Original Message-
From: tom [mailto:tomer.d...@intergraph.com]
Sent: Thursday, October 04, 2012 3:29 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] I have heard that MSI is too complicated from a
I feel your pain. Over the years I have used lots of install technologies,
installShield (script and windows installer), wise (script and windows
installer), inno setup, plain batch files, custom exes, NSIS etc, etc. The only
one that has provided me with a 100% reliable installation is windows
MSI is complicated. Setup is complicated. There is a learning curve but
once you nail it, it's easy for your users.
The key to MSI is that it's declarative (functional programming),
transactional and has standardized support for upgrades, patches,
uninstall, repair, silent and so on. Learn
Thanks; I wish that MSI could prove so simple for users though in some of
Microsoft's own products. Example? I had SQL server Express 2012 on my server
a few months ago, had to uninstall it to clear out some errors, and are you
kidding me? I had to reinstall the operating system to reinstall
It seems a bit unfair to blame MSI for the SQL Server install.
On Thu, Oct 4, 2012 at 6:00 PM, Katherine Moss katherine.m...@gordon.eduwrote:
Thanks; I wish that MSI could prove so simple for users though in some of
Microsoft's own products. Example? I had SQL server Express 2012 on my
What is he doing in his current installer? There are some things in MSI
that are more complex than in InnoSetup and NSIS (although Burn in WiX v3.6
tackles most of them). I'm curious because tackling the complexity
problem/perception is very important to me in WiX v4.0.
On Thu, Oct 4, 2012 at
16 matches
Mail list logo
