Intellisense
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
Intellisense causes problems for me about once every five years. That is roughly our schedule for VS updates, and the problem mentioned is to find out where the **** MS hid the deactivate option this time :confused: I prefer VisualAssist. It doesn't get in the way, it doesn't block the UI, and it offers a much higher level of intelligent support. :rose:
-
Intellisense in Visual Studio 2003 has impressive smartness: it runs a Nefarious Mode able to keep sleeping for days or weeks and then pops up all of a sudden to freeze the entire IDE. Need to kill the process and loose all recent work. From then on, it keeps crashing every time you dare to type in similar code, or just hover over some devil-possessed word. Just enough to ruin your day. Besides that anecdotic annoyance, I find that Intellisense under C++ is much less helpful than under C#, as it does not anticipate right-hand side of assignments based on type compatibility. In addition, it seems to stop working as soon as the slightest syntax error occurs in the text before, even though local inference remains possible.
Why do you bother? When I started at my current occupation it took me half an hour to get my boss purchase VisualAssist: 10 minutes to download and install the demo, 10 minutes to figure out what to present, and another 10 to demonstrate it to my boss and colleagues. No more Intellisense problems ever since... Interesting to hear that Intellisense may actually be useful for C#, we only do C++. But then, this shouldn't be surprising: after all C# is from MS. If they didn't know how to best use their own language, who would?
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
One thing that bothers me is SQL Intellisense. It's so random it doesn't work sometimes, then other times it springs up. Even Ctrl+space doesn't even work. C# Intellisense works quite well though, I only use minimal system usage for it though.
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
-
It's surprising when I see these occasional posts about Intellisense, I think I'm one of the lucky few to have never experienced any problems with it!
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|===
Same here, although I've only used it as far as Visual Studio 2008. I've found my typing has changed to take advantage of Intellisense when I'm writing C#. <rant> OTOH, Intellisense is the area where you see how important C++ and native mode development is to Microsoft. The consistently poor quality of Intellisense support reeks of contempt for C++ developers. </rant>
Software Zen:
delete this; -
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
I really like Intellisense and find it is very productive for me. Only occasionally have I seen the waiting for background message to appear but since I usually have multiple activities occurring in parallel I can just shift focus onto another task until this is ready. Bottom line is that I find Intellisense very useful.
-
It's surprising when I see these occasional posts about Intellisense, I think I'm one of the lucky few to have never experienced any problems with it!
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|===
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
I'm guessing you're [somewhat] new to the sport of programming. Intellisense is a gift. I go back to the days before monochrome monitors ... makes ya appreciate things. These days, with things like intellisense, compiler errors are few and far between not to mention no need for a reference hard-cover on the desk.
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
I've never had much of a problem with Intellisense in VS. Seems as if sometimes it helps when I don't want it to, but I can't think of an example immediately. Intellisense in SSMS, however, is another story. Inside a standard function? Oops, can't help you complete the column name. Any typos anywhere in the query? We've lost all sense of database objects until you go back and fix that. Pretty minor complaints, but it seems as if VS still provides object naming support even if you've made a syntax error.
-
I think they invented the "beating a dead horse" expression for this kind of post. I think it is clear that the advantages of Intellisense far outweigh any little problem that somebody may have in his(her) particular environment.
giuchici
giuchici wrote:
I think it is clear that the advantages of Intellisense far outweigh any little problem that somebody may have in his(her) particular environment
That's a pretty far-reaching comment :) In a previous life, Intellisense would sometimes lock up VS for hours (e.g. all afternoon). Its hard to see the advantage in that, although I do agree that when it wasn't hindering my work, it was very helpful.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Question: Why don't they do it in the BACKGROUND, so that it doesn't block the UI? It is SUPPOSED to be a background operation, but M$ decided to block the UI anyways. :mad:
Gryphons Are Awesome! Gryphons Are Awesome!
-
It is useful, but is sometimes can be a little annoying, with the 'Waiting for a background operation to complete' message, which is usually caused (in my experience) by a FUBARed intellisense parser thread (I have been getting errors in the Windows Event Log related to that, with the 'helpful' message 'Intellisense FUBAR - oops.' or even no message. [Don't have any right now, so no screenshot]) The VS2012 Update 1 seemed to remove those 'messages', but the problem remains. I could go on and on about intellisense's quirks, but that would be heavy reading (not to mention long), so I will leave it at this. My new term for Intellisense is 'Intellinonsense'.
Gryphons Are Awesome! Gryphons Are Awesome!
My intellisense goes walkabout whenever I use the object browser. Other than that, no issues - but I don't deal with massive libraries.
-
giuchici wrote:
I think it is clear that the advantages of Intellisense far outweigh any little problem that somebody may have in his(her) particular environment
That's a pretty far-reaching comment :) In a previous life, Intellisense would sometimes lock up VS for hours (e.g. all afternoon). Its hard to see the advantage in that, although I do agree that when it wasn't hindering my work, it was very helpful.
We can program with only 1's, but if all you've got are zeros, you've got nothing.