Debugger Already attached, help

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I’ve just discovered that our development server can only have one active
debugger at a time. Why? How is it MS thinks that only one developer is only
going to debug at one time? If you have a team of developers working on
multiple projects on a central development server, how you expect them to do
their job? Person debugging app (A) can't do anything if another person is
debugging app (B).

Running the debugger on the developers personal machine doesn’t work, b/c
that means if there are problems and that person is not in the office that
day, other developers would need to login to that personal PC.

Can you run multiple instances of the debugger based on user? If you run the
debugger as a client app instead of a local service, it shows the individual
login in the trace.

Is they a way around this without having each developer debug a local copy?
Our developers work on multiple projects and share tasks within the same
project. Running on local machines does not work for us.

If there is no way around this, MS please for all that is holy, change this
ASAP.


Response appreciated
 
Give each developer their own instance on the server ... they can each debug
their own instance.

It won't let multiple people debug concurrently because theyw ould interfere
with each other ..

Cheers,

Greg
 
Hope Im not sounding too dumb with this question, but how do I do this?
--
JP
..NET Software Developer


Greg Young said:
Give each developer their own instance on the server ... they can each debug
their own instance.

It won't let multiple people debug concurrently because theyw ould interfere
with each other ..

Cheers,

Greg
Click to expand...
 
Ops, hit send by mistake.

I mean, if the debugger modules are installed under the framework folder
when you run the reg_iis.exe or whatever. how do i set it up under multiple
user accounts for the instances?
--
JP
..NET Software Developer


Greg Young said:
Give each developer their own instance on the server ... they can each debug
their own instance.

It won't let multiple people debug concurrently because theyw ould interfere
with each other ..

Cheers,

Greg
Click to expand...
 
Each just needs their own application.If you debug on your local machine you
can quickly see that you can concurrently debug multiple IIS applications
concurrently, this also applies on the server .. if each has their own
application they deal with they can debug without stepping on each others
toes.

Cheers,

Greg
JP said:
Ops, hit send by mistake.

I mean, if the debugger modules are installed under the framework folder
when you run the reg_iis.exe or whatever. how do i set it up under
multiple
user accounts for the instances?
Click to expand...
 
nice english Greg :)

Pick either usage of concurrently and ignore the other.

Cheers,

Greg
 
Perhaps I’m still missing something. I’m still confused, or I’m just not
being clear. Ill try to be clearer in hopes that we can get on the same page.

For example:
• We have development web sever with IIS6 on it.
• The server contains at least 25 website sites
• They access these projects via VS 2005 on their local PC. They connect via
UNC path to the project folder on the server to load the solution file

Any of our developers are allowed to connect to these projects. We wont have
two developers work on the same project at the same time, but they still need
access to connect to the most current version of the project on the
development server should the primary developer for that project be out of
the office.

Let me clarify, that they are not running multiple copies of VS 2005 off of
the development server. This is about:

• Developer A connecting to DEV from his PC to work on Project A
• Developer B connecting to DEV from her PC to work on Project B

And not being able to connect to the DEV debugger at the same time for two
separate projects that physically reside within the same IIS instance.

Each developer does have domain account access to the development IIS via
Remote Desktop. How can I setup multiple instances of the debugger so that
all of them can debug on the development box via connecting from their local
machines?

I hope I clarified it a little more

Thx for all your help in advance

JP
..NET Software Developer
 
Perhaps I’m still missing something. I’m still confused, or I’m just not
being clear. Ill try to be clearer in hopes that we can get on the same page.

For example:
• We have development web sever with IIS6 on it.
• The server contains at least 25 website sites
• They access these projects via VS 2005 on their local PC. They connect via
UNC path to the project folder on the server to load the solution file

Any of our developers are allowed to connect to these projects. We wont have
two developers work on the same project at the same time, but they still need
access to connect to the most current version of the project on the
development server should the primary developer for that project be out of
the office.

Let me clarify, that they are not running multiple copies of VS 2005 off of
the development server. This is about:

• Developer A connecting to DEV from his PC to work on Project A
• Developer B connecting to DEV from her PC to work on Project B

And not being able to connect to the DEV debugger at the same time for two
separate projects that physically reside within the same IIS instance.

Each developer does have domain account access to the development IIS via
Remote Desktop. How can I setup multiple instances of the debugger so that
all of them can debug on the development box via connecting from their local
machines?

I hope I clarified it a little more

Thx for all your help in advance
 
You are misunderstanding me ...

having 2 developers connect with a debugger to the same process would never
work .. if you want them to be able to debug concurrently you need multiple
applications.

i.e.

DEV 1 connects to application foo
DEV 2 cannot connect as DEV1 is already debugging it ...


if you however make 2 instances of foo .. foo1 and foo2 ...

DEV1 connects to application foo1
DEV2 connects to application foo2

since they are debugging different processes they will not be stepping on
each other's feet, they have seperation.

IMHO it would be impossible to do a system where 2 developers could just
effectively debug in the same process space as they could in seperate spaces
as they would be continuously doing things that hurt the other developer. As
an example imagine that I am using SOS at a break point to try to look at
the heap. You try to step through your code which creates a new object and
causes garbage collection .. the results I am looking at are now completely
invalid as you have changed the state of the process.

There is no good way of handling this which is why you must break it apart
on process boundaries.

I think the big problem you are running into is relying on the project to
handle connecting to the process .. as soon as you simply attach to a
process instead of forcing visual studio to do it based on the project this
all becomes much easier.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
 
Ok, i think got it now. In our case Foo1 and Foo2 are seperate apps with
seperate developers, but both apps need to use the same debugger and it just
wont happen. Well looks like we are up the creek then. Make sense that the
heap would then be a combination of Foo1 and Foo2 thus the debugger couldnt
distinguish between what belonged to who.

I wonder if MS will ever address this
 
You are not understanding ..

the application is foo ...

I am saying to create two instances of foo ... foo1 and foo2 .. (i.e. to
create multiple compies of the same website). They can then each debug
seperately in their own copy of the web application.

Cheers,

Greg
 
LOL. I did understood that part. Each site folder in the IIS could point to
its copy of Foo (Foo1 and Foo2). We dont need two developers working on
copies of the same project at the same time. Your right in that it would
allow them to do so if needed.

What I was trying to say that there is already completely two seperate
projects on the same IIS:

Application Foo
Application Moo.

Developer A wants to debug Foo
Developer B wants to debug Moo

But both cant debug their respective apps at the same time, even though the
two apps have no relatrionship to each other whatsoever other other then the
fact they are being served by the same IIS.

LOL

I guess weve beat this horse huh :o)




Its not that we need two developers to work on multiple co
 
yes. Since the development server contains both Framework 1.1 and 2.0
aplications, there is a seperate Pool for each version of the framework.

In this case Foo and Moo are running in the same Pool
 
Back
Top