The ideal situation is to have the app on dev machines for debugging and
only use a centralized dev server for integration testing. One of the
primary reasons is the .NET debugger can only attach to one process at a
time, which means only one person can debug and every developer will cause
the debug to hit break points if they start even looking at the app. This is
true whether you use IIS 5 or IIS 6, and has to do with the fact that the
debugger is attaching to the application in question.

I am not certain about what happens if you make multiple apps (same app
copied). It might be possible, if you have different apps in isolated
processes (which can be set up in IIS5 an 6, although 6 has much better
options). If you can get a web server on the dev machines and debug locally,
using code control (SourceSafe) to sync up developer code changes, it is the
best option.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

************************************************** **************************
****
Think Outside the Box!
************************************************** **************************
****
"Bruno Rodrigues" <brunosantosrodri@uol.com.br> wrote in message
news:876e01c34554$2cf837e0$a401280a@phx.gbl...
> Hi,
>
> Our project is on a server, and we realized we cannot
> debug together, neither creating an Web Application to
> each one.
>
> It is possible to do with IIS 5, or requires IIS 6 and
> Win.net??
>
> Thanks