I'm looking for a great link that describes deployment of the CLR to an installed base. If you're 99% sure you're app is going to be the very first .NET application that your clients download and try to use, what is the user experience for installation? Zip files won't cut it, putting "requres CLR" in the sysreqs won't cut it. I want an integrated experience that wraps up the CLR installation so ordinary folks can get it if they need it. I'm pretty sure Sam Gentile has this information, as it's implied in his famous rant but not actually itemized. Also pretty sure buying a major install app (Wise, InstallShield) would solve this. How to solve this on the cheap then?
Sells had a dynamic checker on his web site to let folks know if they could run his game "wahoo." Handy, (and by the way how did he do this), but only half the battle. His presumption is that users read (I'm the only one who does, which is how I found it). Those who don't read had better understand error dialogs.
comment 2:23:20 PM trackback