We have been attempting to get Windows Vista Logo certification for VistaDB.  Yes, it has been a slight pain, and we even got some flack from the Microsoft people about the name Vista (we had it first!).

MSI Installer not optional

Just in case you have not gone down this route yet I thought I might point out a few non obvious things.  First, you MUST use an MSI installer.  Currently our installer is not an MSI installer.

I have wanted to change away from this installer for other reasons anyway, but it appears we will make the change with 3.4.  The next build will use the new installer (if it is ready).  Dot Net runtime installation is usually not an issue with most developers, but it is nice to be able to go get it if required. 

64 bit Install

If you install a 32 bit app on 64 bit Windows you get put into the \program files (x86) directory.  Now why they went this route is beyond me.  I would have expected all existing apps to stay in a \program files\ and a new x64 directory to be created.  I would prefer to handle the exception to the rule with new systems rather than the old code being expected to work correctly.  I have run into a number of old apps that break because of this change (and no new versions are available).

VistaDB runs 64 bit.  We are 100% managed code and JIT up to 64 bit very well.  But because the installer is not 64 bit we always get put into the 32 bit program files directory.  This has caused a number of support requests from people wanting to know where the 64 bit version is for installation.  The new installer knows the difference between 32 bit and 64 bit and puts us in the correct path.

GAC

Our current installer also has no knowledge of the GAC or how to deploy managed code.  So it is all a giant hack at the end of install to call GACUTIL to put things in the GAC.  You are not supposed to do this, and in fact it will get you rejected from Vista Logo status.

The new installer understands the GAC, and correctly deploys things and uninstalls them automatically.  Ah, nice.

Updates

The new installer has an update system for patches as well.  Have not had a chance to try it yet with anything beyond hello world style apps.  It will be interesting to see how it handles it.  One of the big problems we have right now is that the user serial number is removed when you uinstall.  That is just silly if you are performing an update on the app to make the user enter all their information again.

What is it?

InstallAware is the new installer.  Expect to see it in the next few weeks for a 3.4 build.