To some degree, this is a design limitation of ASP.NET. Here are the
possible work arounds:
1. If you are using Windows Server 2003, you can setup a unique application
pool for each user.
2. Give each user their own web server. Visual Studio does not need to run
on this web server, you only need to install the remote debugging
3. You can use 'web matrix'
4. I haven't tried this, but you could probably run the web matrix web
server under the de *** . You would open the web matrix executable as a
project (File->Open->Project), and start IE outside of the de *** .
The next version of Visual Studio will have a better solution. See