\Tips and TricksTesting Your MSI
This section provides tips and a checklist for testing your product,
if you find a problem then you will probably want to see the
help for debugging installation problems.
If you find that you can't uninstall a product once its installed then I'd recommend that you read the "Uninstall Fails (Don't Panic)" section :-)
Needs more work, and a bit of a check list:
- Only you know how likely your MSI is to "stuff up' your
Think twice about installing there or use a
if possible (now that Virtual PC is free there is no excuse).
I've never yet done something I haven't been able to undo
but I've been close...
- Check that all launch conditions work
(install, repair, uninstall).
- Test on multiple operating systems if supported.
(such as VmWare or Virtual PC) are very useful here.
If not supported on an OS then check that a
launch condition exists to
prevent installation where not supported.
- Try installing as administrator, "normal user", basically different
Any issues may need you msi modified or at least some documentation.
- Logon with separate test administrator and normal users.
This can test any install or repair on demand as well as any logon
scripts you may have set up.
- Try silent install (repair and uninstall).
If not supported (and why not?) check that a
launch condition exists to
prevent silent installation.
This will annoy (or turn away) any large customers who want to
automatically deploy the product.
- Double click on an MSI that has already been installed,
see what happens, try all options (uninstall/repair).
- Test repair of product (or disable it).
Double check any configuration (registry, INI etc) in case it
- Try uninstall/repair via the Windows
- Test all conditions on all
custom actions you have defined.
- Specifically test install followed by deletion of the installed MSI
(rename is good enough), see what happens during repair and uninstall.
If you got prompted
(when files didn't need installation - files always need source):
- Is this what you wanted or expected?
- Manipulation/use of the "SourceDir"
property is one possible reason.
- Version lying
on files can also cause this.
If you got prompted for any reason, did the dialog prompt in
an "friendly" manner?
- Test per-machine installs/repairs/uninstalls under the SYSTEM account
(see "Testing Under the Local System Account").
This should be in "silent" mode, but should work as some
deployment tools use the system account.
- Test deployment using your chosen mechanism.
- Create a new version of your product, try upgrade to make sure you
don't have any issues.
Its no good finding out when you want to deploy your second version
that you have done (or not done) something in the first version that
- Some links to other testing pages: