Strange IDE behavior of c# compared to IDE of VB.NET...

[Wokawidget]

I had a private var called Woof as this, as most of you are aware, is one of my favourite words :D

I then changed this to keyList.

However, after a further 10 mins developing I noticed a squiggley line under the var name keyList...and here's the IDE msg attached to this doc.

Why on earth hasn't the IDE realised that I have changed the var name???

Woka

[Mike Hildner]

I guess the IDE likes "Woof" as much as you do :)

Seems like there are a few "hangover" type things like this that building the project (Shift-Ctrl-B) clears up.

Mike

[Wokawidget]

if I build the project it fixes it. but I should have to.

things like this are making me hate c# even more :(

However, I am using the bugged and crappy 2004 VS and not 2005, maybe all these idiotic bugs have been fixed.

Woka

[Mike Hildner]

things like this are making me hate c# even more

It has nothing to do with C#, it's the IDE. You can use Notepad instead, if you'd like :)

Little things like that don't bother me. I didn't know there was a VS2004. I'm using VS2005 and there's still some wierd things like that.

Mike

[Wokawidget]

hahaha. I know it's the IDE, but it's irritating.
Sry I meant 2003 :D

woka

[jmcilhinney]

VB.NET uses incremental compilation, which means the IDE compiles your code as you type it. The C# IDE doesn't do that, for whatever reason. The IDE will detect syntax errors as you type but compilation errors must wait until you compile. That's actually more of a great feature of the VB.NET IDE than a deficiency in the C# IDE. Particularly in the 2005 version, the C# IDE gets a few cool features that the VB version lacks. They are created by different teams after all, so they're bound to be a bit different.