Tuesday, July 3, 2007

Silent Installations Should Actually BE Silent

It seems to come up a lot: How an installation should be silent. My belief on the topic is that a silent installation should follow 4 basic rules.

  1. Actually be silent. I don't want to see any dialogs of any kind
  2. Don't do something sneaky and try to elevate yourself somehow. Just fail nicely
  3. Provide some form of command-line argument list, help, or silent installation guide
  4. If you don't follow rules 1 - 3, don't allow the installation to run silently.

The worst thing about silent installations is when someone demands you see their EULA. Typically, if someone is installing the product silently, they don't care about your EULA anyway. Most people disregard the EULA about as quickly as they can percieve it.

I also find it very bothersome when an installation allows you to proceed silently and has never been tested/authored to work silently. It's better user experience to just not have an installation then have to root around in a log file to try to resolve some issue only to realize later that there's no way you could have fixed it anyway.

1 comment:

Christopher Painter said...

One of my favorites is if you support a silent install, you must support a silent uninstall!

When I worked at Continental Avaya was guilty of this one big time. I had to write a forced uninstall utility to get the crap off of the machines and then repackage as an MSI.

BTW, Bloggers Wanted if you want to come join the team!