How to debug in VS.NET

jdang67 · April 29th, 2005, 04:20 PM

I have a simple question about debugging in VS.NET and I think you may know how to do this.
In Visual Studio 6 and earlier, in command window I can debug my code on fly without any problem. Now, in VS.net, in the command window, I can check the value of any properties but cannot call any method.

For example, I have a string variable called tmp and the value is "This is a test";

string tmp = "This is a test";

In my command window, I can type tmp.Length and it return 14.
Then I try to call a method tmp.ToUpper(), it throws error "ToUpper' does not exist". Do you know to to fix the problem?

Regards,

John

Hal Levy · April 29th, 2005, 04:58 PM

Please do not post the same question in multiple places

http://p2p.wrox.com/topic.asp?TOPIC_ID=29928

Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.

planoie · May 2nd, 2005, 10:32 PM

In VS.NET the "Command" and "Immediate" toolbox windows are shared. You have to switch from one to the other.
For the Immediate view: Debug -> Windows -> Immediate
For Command: View -> Other Windows -> Command Window

-Peter

jdang67 · May 7th, 2005, 03:16 PM

After go to Command window then do what? the problem is in Command window editor, you cannot do much with a method of any object. In old Visual Studio 6 everything working. Have you ever used the debugger in VS.net?

John

Hal Levy · May 7th, 2005, 08:57 PM

I use the debugger in VS.net all the time...

I have not run into a case where I could not run in the command window.. are you using the ? nomenclature as such: ? tmp.ToUpper()

Also, you don't mention if this is C# or not, if it's C#- remember it's case sensitive....

Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.

jdang67 · May 11th, 2005, 11:22 AM

Are you sure it's working? I have tried at work, at home and at my co-worker machines and all of them were not working at all. I am a software developer since 1997 and using Dotnet since 2002. If you have time, please verify if the debugging on fly is working on your machine and show me how to make it works.

John

gabrieldcr2 · November 24th, 2005, 11:27 AM

Hi, I'm having a problem with the command windows, too. In my case a can evaluate expressions in the command windows, but the intelligence sense doesn't work, well sometimes when a put a dot it shows me the list of available properties for an object, but in other ocasions it doesn't, I don't know why, Is the any key a have to set?, thanks

Hal Levy · November 26th, 2005, 12:13 PM

Please start new questions in new threads.

InteliSense doesn't always work for me either when in the command window. I have not discovered why that's the case.

I actaully never even looked for a pattern as to perhaps certain types have problems that others do not.

I will say that In 2005 debuging was an area they worked on.. tho I have not used it anywhere near as extensively as I would have liked- since I do not have a copy of the GM for it.

Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.

Ankur_Verma · November 27th, 2005, 03:05 PM

I'm rather late to join this discussion, but just wanted to put in my two cents on the actual topic of this thread.

John, you are right. But so is Hal.

? ss.ToUpper() should work and it does work in VS.NET 2005 so Hal is right, but it doesnt work in earlier versions, so you are right too.

Interesting thing you've pointed out though.

Ankur

Hal Levy · November 28th, 2005, 11:54 AM

Ankur- When VS.Net came out... Microsoft said there would be debugger issues.. and that things people were used to in the old VS would not be possible...

In 2005 they have remidied that.. and I can't wait to start using it in production.

Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.