|
 |
aspx thread: Multi User Remote Debugging
Message #1 by "Harish" <harish@h...> on Fri, 21 Feb 2003 16:39:51 -0600
|
|
Hi,
Can multi users debug against different web projects simitaneously?
We have set up remote debugging in VS.NET successfully. But only one
developer from our team can debug at any time. If a second developer is
trying to debug when somebody else is already debugging then he gets this
error:
"Error while trying to run project: Unable to start debugging on the web
server. A debugger is already attached. Would you like to disable future
attempts to debug ASP.NET pages for this project?",
We get the same error even if the second developer tries to debug a
different project than the first developer.
Thanks.
Harish.
Message #2 by "Peter Lanoie" <planoie@n...> on Mon, 24 Feb 2003 13:34:33 -0500
|
|
Harish,
When you debug a server, you attach to the appropriate executable that's
processing the page. In the case of .Net you would be attaching to the
aspnet_wp.exe process. That's the "Worker Process" for ASP.Net. Regardless
of how many different web applications (virtual directories) you have on the
server, they are all going thru that same process, so anyone attach to it
will keep anyone else out, and subsequently also keep anything else from
happening on IIS to boot (right? Perhaps the .Net framework has changed how
it used to work). Not only would no one else be able to debug, but (to the
best of my limited .Net knowledge) no one would be able to BROWSE pages on
that server until the debugger has released the process, or at least
proceeded (back in regular running mode even with a debugger attached). I
would highly recommend against doing remote debugging on a server that is
shared. The best scenario is to use local mode for development and run
debugging locally. I realize this is a significant change requiring all dev
machines to be set up as servers and with everything that goes along with
that so it may not be a possibility for you for whatever
logistical/budgetary reasons (nothing like buying 20 copies of 2000 advanced
server and Universal MSDN subscriptions!).
Now, I'm not sure about this, and I highly doubt it's even a possibility but
here's an idea. (If someone is more familiar with this subject please
correct me and let us know.) You can set up virtual directory
"applications" to run in isolated memory space. This basically breaks off
the process to another instance of the page processor. I have done this in
classic ASP/IIS. You end up with a single inetinfo process (as per the
usual) but you then get a "ddlhost.exe" process for each of the isolated
applications. The verbose point I'm attempting to make is basically a
theoretical question/idea: If these applications are isolated to their own
processes, can the debugger attach to the correct process and therefore
allow you to debug simultaneously? I would venture a guess that it's not
possible. I would say, be blessed that you can get debugging working at
all. ;-)
Peter
-----Original Message-----
From: Harish [mailto:harish@h...]
Sent: Friday, February 21, 2003 17:40
To: ASP.NET
Subject: [aspx] Multi User Remote Debugging
Hi,
Can multi users debug against different web projects simitaneously?
We have set up remote debugging in VS.NET successfully. But only one
developer from our team can debug at any time. If a second developer is
trying to debug when somebody else is already debugging then he gets this
error:
"Error while trying to run project: Unable to start debugging on the web
server. A debugger is already attached. Would you like to disable future
attempts to debug ASP.NET pages for this project?",
We get the same error even if the second developer tries to debug a
different project than the first developer.
Thanks.
Harish.
|
|
 |