Until May 1 2007 Microsoft is offering free certification testing of your software. So this is a great opportunity for the MicroISV to get the logo, and earn some partnerpoints, without spending a lot of money on it.

But is it actually realisitic for a MicroISV to comply to the demands for the software, and what are  these demands anyway? I downloaded the Certified for Windows Vista Requirements and had a brief look at what you should expect.

• First of all all processes must support User Account Control, so any application must have an embedded manifest stating the execution level, and if you need to run your application with elevated priviliges, you need to apply for a waiver from Microsoft. 
• The software must support x64 versions omf Windows Vista, which basically just means that no 16-bit components can be used, as they won't run on 64-bit versions of Windows, and if you application is dependent on kernel-mode drivers, you must supply and install these. The application doesn't have to run natively, as WOW64 will allow 32-bit code to run.
• All executable files must be signed with an Authenticode certificate. You will also need this certificate to submit your application for testing. In connection with the Vista certification program, you can aquire this from Verisign at a discounted price of $99.
• All kernel-mode drivers must have a Microsoft signature obtained through the WHQL or DRS program.
• The application should not fail to install on higher versions of the OS unless this is the intention. I should support running in multiple logon-sessions, not load in safe-mode and of course not be spyware (according to Anti-Spyware Coalition )
• Applications must use the Windows Installer (MSI) for installation.
• Applications must be installed to correct folders, and not set protected registry keys.
• Rebooting during install should be avoided, and if necessary, this should be thoroughly documented.
• Applications must install in command line in quiet mode with the switch /qn
• Component rules should be followed, for instance only one COM server per application.
• No crashes during the logo certification test, and applications must only handle known and expected exceptions.
• ISV must sign up for Windows Error Reporting, and not disable it in the application.

The conclusion is, that the document of requirements seem worse than it is. It should certainly, for a disciplined developer team, be possible to comply with these requirements, without extending the development time considerably. See the complete list of test cases with instructions, so that you can perform your own pre-tests.

You save the approximately $1000 testing fee, but you will need a Authenticode certificate at $99. Other than that, I am not aware of further cost. Although you should focus on the pre-test, because if you fail you will be billed for the test, and you can instead get a retest for free. So be sure that you won't fail using the list of test cases.

I will attempt to get my application certified for Vista, so i will be posting about the progress, and my experiences.