Is there Remote Debugging in Vs.Net 2003 Pro

[Oleg]

HI, all....

I am testing Vs.Net 2003 Pro for use in our company (from the 60 day
trial disk). Currently we are using 2002 Enterprise. In Vs.Net 2002
Enterprise I have the ability (under Debug|Processes) to select
another machine from our network and attach to processes running on
it. In the evaluation version of 2003 Pro I don't have the ability to
select another machine AT ALL.

So, I was wondering if that is a limitation of Professional version of
VS 2003? Or is that a limitation of 60 day trial version?

Basically, questions is: Using Vs.Net 2003 Professional can I debug
processes on a remote machine (or is it only possible in Enterprise)?

Thank you in advance,
Sincerely,
Oleg

[Klaus H. Probst]

Maybe remote debugging is not installed in your case? That's certainly
supported under 2003.

--
Klaus H. Probst, MVP
http://www.vbbox.com/
"Oleg" <mo*****@yahoo.com> wrote in message
news:90**************************@posting.google.c om...

HI, all....

I am testing Vs.Net 2003 Pro for use in our company (from the 60 day
trial disk). Currently we are using 2002 Enterprise. In Vs.Net 2002
Enterprise I have the ability (under Debug|Processes) to select
another machine from our network and attach to processes running on
it. In the evaluation version of 2003 Pro I don't have the ability to
select another machine AT ALL.

So, I was wondering if that is a limitation of Professional version of
VS 2003? Or is that a limitation of 60 day trial version?

Basically, questions is: Using Vs.Net 2003 Professional can I debug
processes on a remote machine (or is it only possible in Enterprise)?

Thank you in advance,
Sincerely,
Oleg

[Oleg Sobol]

I understand that Remote Debugging is supported in VS.Net 2003.

What I am asking is wheither it is enabled (for use) in Professional
version, or only in Enterprise version? Or, if it should be installed
separately (which wasn't the case for Vs.Net 2002 Enterprise) how do I
install it in Professional 2003(meaning not remote debugging components
for the server, but on the developer machine)?
Sincerely,
Oleg
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

[Klaus H. Probst]

Ahh, true. I see what you're asking. Well, this matrix:
http://msdn.microsoft.com/vstudio/ho.../choosing.aspx

says Pro also has it. I've only installed the EA version, but as far as I
remember it's selected by default for installation. I could be wrong of
course.

If this is a make it or break it deal for you I'd suggest just calling
Microsoft and asking them.

--
Klaus H. Probst, MVP
http://www.vbbox.com/
"Oleg Sobol" <mo*****@yahoo.com> wrote in message
news:eJ**************@tk2msftngp13.phx.gbl...

I understand that Remote Debugging is supported in VS.Net 2003.

What I am asking is wheither it is enabled (for use) in Professional
version, or only in Enterprise version? Or, if it should be installed
separately (which wasn't the case for Vs.Net 2002 Enterprise) how do I
install it in Professional 2003(meaning not remote debugging components
for the server, but on the developer machine)?
Sincerely,
Oleg
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

[Niki Estner]

I'm using the pro version, and remote debugging works fine.

Niki

"Oleg" <mo*****@yahoo.com> wrote in
news:90**************************@posting.google.c om...

HI, all....

I am testing Vs.Net 2003 Pro for use in our company (from the 60 day
trial disk). Currently we are using 2002 Enterprise. In Vs.Net 2002
Enterprise I have the ability (under Debug|Processes) to select
another machine from our network and attach to processes running on
it. In the evaluation version of 2003 Pro I don't have the ability to
select another machine AT ALL.

So, I was wondering if that is a limitation of Professional version of
VS 2003? Or is that a limitation of 60 day trial version?

Basically, questions is: Using Vs.Net 2003 Professional can I debug
processes on a remote machine (or is it only possible in Enterprise)?

Thank you in advance,
Sincerely,
Oleg

[Oleg]

R u sure you have VS.Net 2003 Professional (not enterprise)? And you
have the choice to select another computer in the options screen for
attaching to a process?
If you do, let me know... that should be proof enough (maybe I just
have some cut trial version)...

Sincerely,
Oleg


"Niki Estner" <ni*********@cube.net> wrote in message news:<eR*************@TK2MSFTNGP12.phx.gbl>...

I'm using the pro version, and remote debugging works fine.

Niki

"Oleg" <mo*****@yahoo.com> wrote in
news:90**************************@posting.google.c om...

HI, all....

I am testing Vs.Net 2003 Pro for use in our company (from the 60 day
trial disk). Currently we are using 2002 Enterprise. In Vs.Net 2002
Enterprise I have the ability (under Debug|Processes) to select
another machine from our network and attach to processes running on
it. In the evaluation version of 2003 Pro I don't have the ability to
select another machine AT ALL.

So, I was wondering if that is a limitation of Professional version of
VS 2003? Or is that a limitation of 60 day trial version?

Basically, questions is: Using Vs.Net 2003 Professional can I debug
processes on a remote machine (or is it only possible in Enterprise)?

Thank you in advance,
Sincerely,
Oleg