Visual Studio IDE editor/Intellesense Bug?

Posted By: sc00ter | Dec 2nd, 2006 @ 4:06 PM
page 1 of 1
Comments: 3 | Views: 3957
#Dec 2nd, 2006 @ 4:06 PM
sc00ter
sc00ter
Always in motion the future is..
I've just filed my "FIRST" bug ever over @ connect.ms. Hopefully its a real bug.  Nothing big, maybe someone here can verify it?

Open up any file/new or old.. (I used VB.Net Express)
type this in

const BLAH as integer = 5
#const blah = 4

#if blah then
  any code here

#end if

Now move the mouse over the blah in #if blah.. This "Should" show 4 right?  For me it shows 5. 

If const BLAH as integer = 5 is commented out, #if blah  doesn't show anything when the mouse is over it. hmm. I didn't put that in the bug report.  Need to edit that.  [Done]

Can anyone here confirm this? here or in the actual bug report?

The link: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=242845

If I've done something wrong, or should have explained things better, please let me know.  As I said before it was my first bug report. Smiley
#Dec 3rd, 2006 @ 2:05 PM
littleguru
littleguru
<3 Seattle
It's a bug. I have tried it in VS 2005 Pro. It's also showing the wrong thing. If you rename the #Const blah to blah1 and try to hover again, nothing is shown!
#Dec 7th, 2006 @ 4:54 PM
sc00ter
sc00ter
Always in motion the future is..
Just an update to whats going on with this lil bug.  They've replied to my bug report..

--
Thanks for reporting the issue. Unfortunately we won't be able to address it at this time.

VB Team

Posted by Microsoft on 12/7/2006 at 3:25 PM
--

Well, at least now they know about it.  I guess thats all that matters.  Doesn't break the program or anything like that, nothing serious so.. Who knows when it'll get fixed.


#Dec 9th, 2006 @ 12:25 PM
CannotResolveSymbol
CannotResolveSymbol
{insert caption here}
sc00ter wrote:
Just an update to whats going on with this lil bug.  They've replied to my bug report..

--
Thanks for reporting the issue. Unfortunately we won't be able to address it at this time.

VB Team

Posted by Microsoft on 12/7/2006 at 3:25 PM
--

Well, at least now they know about it.  I guess thats all that matters.  Doesn't break the program or anything like that, nothing serious so.. Who knows when it'll get fixed.




I can understand why.  It's not a major issue that keeps you from working with the program, but a proper fix for it (recognizing that the variable is in a preprocessor directive) would probably require a substantial reworking of Intellisense, so it wouldn't be worth the effort.
page 1 of 1
Comments: 3 | Views: 3957
Microsoft Communities