some things in the Immediate window arent working

uhh I'm puzzled. I cant think of the other stuff, but a lot of things dont work when I'm debugging my app. IE this doesnt work with any string anymore. I have a string called CONTENT and I try this in the immediate window
?content.IndexOf("hello")

I get this error error: 'content.IndexOf' does not exist

I've tried accessign array items as well. I have a string[] and I try to access one element of it and I get this error:
error: 'links' is not an array or pointer. Indexing is not available
I get the same error when trying to access an item of any type of array (even arrayList) through the immediate window

wth is going on?!! :confused:

• Is this in one solution?
• Have you tried the same thing in another solution?
• Have you tried moving the solution to a different computer?

Dan

Quote:

---

Originally Posted by dipique

• Is this in one solution?
• Have you tried the same thing in another solution?
• Have you tried moving the solution to a different computer?

Dan

---

who cares about the solution man... immediate window is a part of visual studio so it's VS that isnt working right :mad: it might possibily get resolved if I reinstalled it, but I hate reinstalling VS with a passion.
Yeah so regardless of the project, that doesnt work correctly when I'm using C#... havent tried it in VB projects:D

It's bugger-all use in VB.net too. That's the only reason that I keep VB6 on my machine, so I can use the decent immediate window to test stuff out and quickly access old constants.

VB Code:

?vbSrcCopy
&HCC0020

:D

The immediate window is of course case sensitive - so make sure that's always correct. Of course, the command window itself can be run in command mode or immediate mode:

http://msdn.microsoft.com/library/de...mandWindow.asp

To switch to immediate mode, simply type immed.

You can then use intellisense as you would in the programming window. And lastly, to switch back to command mode, enter >cmd. Also, intellisense and most commands only work when you have stopped at a debug point.

I know about the case sensitivity nemaroller... I think wossname is right though, it's just that VS is buggie:D


edit: confound it!

I don't know... I don't have any problem with it. I'm using Vs 2003 Enterprise Architect.. and it works just fine.

Quote:

---

Originally Posted by nemaroller

I don't know... I don't have any problem with it. I'm using Vs 2003 Enterprise Architect.. and it works just fine.

---

I'm using VS.NET 2003 Enterprise Architect too, BUT I have a lot of problems with it :D
ah regardless
lets just hope that VS.NET 2005 would be a lil less buggy