Wish I was using VB
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
Happens to me all the time. I don't think it has anything to do with the language (though, I can't be certain of that). More likely, it's the specific version of Visual Studio and/or the project you are working with.
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
rriegel wrote:
I had red "underlines" everywhere in my C#
You often find this when updating some code and the source file has not been saved, so the background compilation is working on the uncorrected code. It's usually the fault of the developer rather than anything inherent in C#.
Veni, vidi, abiit domum
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
I am doing VB.Net now and wish I was using C#, well all sorts I suppose... :rolleyes:
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
There's something very wrong in your setup - it works perfectly for most of us. C++ intellisense, by contrast, is a dog. I blame the language though - its incredibly hard to parse 1000's of lines of code (from headers) of a language that isn't context-free and update the intelli-suggestions in real-time.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
-
All this is true of C# too, there is no difference between the languages when it comes to background compiling
There is nothing to see here, move along
no. (at least not up until VS2010, can't tell about VS2012+) If you add an additional parameter to a method in vb.net every place in all the projects of the solution where this method is used pops up instantly in the error window and notify you about the error. In c# you have to run the build process manually to get those messages to appear. If you have made a few changes you're not unlikely to rebuild the solution for multiple times (which can consume quite an amount of time for solutions with many projects and lots of code) making fixing errors more tedious.
-
I am the only one that thinks the C# intellisense is terrible? I remember back when I did VB.NET and intellisence was great. Visual Studio needs to step up and get this crap fixed. I had red "underlines" everywhere in my C# project and couldn't figure out why. I recompiled the code, they all went away and everything was good. So in order to get rid of errors you have to compile? I love C# but the intellisence and errors it detects pisses me off :)
-
no. (at least not up until VS2010, can't tell about VS2012+) If you add an additional parameter to a method in vb.net every place in all the projects of the solution where this method is used pops up instantly in the error window and notify you about the error. In c# you have to run the build process manually to get those messages to appear. If you have made a few changes you're not unlikely to rebuild the solution for multiple times (which can consume quite an amount of time for solutions with many projects and lots of code) making fixing errors more tedious.