And the reason they don't allow .exe files is to avoid ending up
in this situation.
Most don't, but some do:
http://www.wergittep.com/hosting/features.html
http://www.lfchosting.com/scripts/frameset.cgi?/hosting_packages.shtml
I've seen a few others in the past. A lot of companies seem
to go along with the restrictions and wind up using PERL, PHP,
etc. This is a mistake, in my opinion if they hope to grow
via good customer service. They will eventually either not
make it or wind up switching to another language. It is better
to get started on the right track. It may mean paying a little more
for hosting, and development may take longer as well
(especially when the size of the project is small), but in the long
term they will at least give themselves a shot at having a stable and
efficient website.
I think the situation is similar to supporting multiple client
versions in distributed systems. It isn't ideal, but reality
imposes itself. It is reasonable to expect a certain amount
of continuity from a web host. I don't know of any that have totally
dropped one vendor and started using a new one. And
if they just move to new systems from the same vendor, your company is
probably heading in the same direction. If your
host isn't flexible about maintaining an older system, you
might have to buy a newer system a little sooner than you
thought.
Brian Wood
Ebenezer Enterprises