Re: Remote debugging
- From: peter <apvx95@xxxxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 18:30:03 +0100
In our experience, this scenario hardly ever works. Even if you get to the stage where everyone can debug on the server, only one person can debug at a time (as I recall), and the system slows to an absolute crawl making it impossible for other developers to work. We gave up on this about 2 years ago.
We now develop everything locally on developers' machines and deploy to the development servers (split by application tier) for a recognised build. The only exception to this is where we have completed middle tier components that are (obviously) working satisfactorily. These are deployed to the development application server and are used in code being developed 'as is'. Obviously there is no way of debugging these components in this scenario and developers have to treat them as black boxes - which are guaranteed to "just work".
All code is held in VSS and developers must check their code in (working or not) before they leave each day - so the VSS version is always the latest.
It works for us.
HTH
Peter
EDom wrote:
Hi, I have a common scenario where all the developers will debug the code from one central server which is hosting the asp.net project. I shared the wwwroot$ and can open the project in different development machines but when I run the debugger to execute the code it stops after compiling with a message "Read the ASP.NET and ATL server debugging....." and sometimes it says "Access denied.. I need to add user to the local debugger group of the host machine etc...."
Please anyone can suggest the process to setup the debugging for multiple users on remote machine.
Regards,
.
- References:
- Remote debugging
- From: EDom
- Remote debugging
- Prev by Date: Re: Problem when hosted by a Windows Service
- Next by Date: Serialization Problem
- Previous by thread: Remote debugging
- Next by thread: Generating proxies to a singleton
- Index(es):
Relevant Pages
|