Oh, not to mention that the cost just described is for a single release. If you start sending bug fixes or new versions then you pretty much go broke - not from the fees to verisign, but from the people you need to employee to run through the lengthy process of sending Versign each individual file needing to be signed and getting them to update it and send it back.

You think that is annoying - try signing for WM5 apps. The only option you have is through Verisign and not only do you pay for a cert you have to pay for every single exe, dll, and cab file that is signed (think it's about $30 each time). So if for instance you have an app with 4 dlls, and an exe and you want to package it in a cab then you are up for 6 x $30. If you have different builds for different languages or platforms then you just start multiplying. It's not the normal cert process so you can't use comodo etc. Obviously someone at MS holds a few shares in Verisign.