It's probably worth bearing in mind that the licence is for a
developER not
"for development" (ie: a shared development server). The
intent is for the
Developer Edition to be installed on the local PC of the
developer.
I don't that this should be a problem. You don't need a
separate DB for
each developer, or even a separate DB login. Provided they
can make a
TCP/IP connection between their dev PC and the DB server,
they can all have
DSNs using the same DB credentials.
IIS is a bit more of a pain on adev type machine (which is
probably running
desktop rather than server software), because IIS is limited
to one website
at a time. It's moderately easy to get around this
restriction though, or
really not so hard to reconfigure the single website anyhow.
I would hope
it's not like your developers are working on all these
different website
simultaneously.
If poss, I'd be changing to Apache in this case, as it allows
as many
websites as one likes. I realise this is not always possible,
though.
Or, if you *must* have a centralised development server: you
need to buy
the appropriate licence, unfortunately.
--
Adam