>>>I don't think his problem had to do with versioning, or anything like that.
>>Uhm, no. IIS has never not been on these machines.
>
>That could be, but I was talking about Tim's problem in particular which looks like exactly what I described.

Ooopps... well, you know it's all about *me* <bg>...

Even if IIS isn't installed, the install should either install it (it's sort of a requirement) or at least should let the user know that some things werent' installed and will require a reinstall.

That whole setup procedure is scary as hell if you ask me. That whole hoky looking install program, the way it runs several extremely large batch files and sometimes appears to comletely lock up without any UI feedback (it's OK - it's only *your* apps that aren't supposed to touch the operating system, it's Ok for Big Brother to mess with it and fuck up our systems <s>).

Remember that the CLR at least will have to be installed for many people if you build apps with .NET - then there's whole issue of configuring the basic security system to run anything that isn't on the local machine... Installations of non-server apps is going to be a ton of fun...