Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
So it looks like I finally have some good news to report on the annoying Intellisense problem I’ve been fighting with for some time in Visual Studio. In short, the problem is that in ASP.NET pages Intellisense has not been working correctly and required explicitly going into the Visual Design View in order to get Intellisense on any controls on the page to work. Needless to say this has been really annoying especially for complex forms that contain lots of code where I would rarely touch the UI form interface. In general I try to avoid the visual designer as much as possible since it’s so slow to load content and Html Source view wasn’t enough to trigger the Intellisense ‘activation’.
In any case, it looks like the problem is – nVidia video drivers on Vista. I’ve been running with the stock Microsoft nVidia drivers (I have a nVidia go7800 in this laptop) that installed with Vista and these drivers have been otherwise working fine. Usually I get updated drivers, but the feedback on LapTop Video Forums has been so bad on some of the updated drivers from nVidia that I had put this off.
Today I was screwing around trying to get CamTasia to work here (ironically to send a small video of the issue to Microsoft) and couldn’t so I downloaded the latest nVidia drivers from here:
http://www.laptopvideo2go.com/forum/index.php?showtopic=12185
and to my surprise when I went into VS.NET to double check the problem my Intellisense is now working properly. Yay! I’m stoked... this has really been a pain in the ass and I’m so glad this is resolved now (I hope).
The new drivers also finally have the nVidia control panel to adjust screen color and brightness settings which had been missing in previous drivers. The default has been Ok but the default contrast was lacking which is now fixed. Also looks like the driver now properly goes into sleep mode after some idle time which just wasn’t happening with the old one.
Unfortunately I had no luck getting CamTasia to record the screen in any way – I just keep getting a garbled signal (colored lines) even when running with Aero off... <shrug>. Oddly CamTasia used to work in RC1 of Vista with old nVidia drivers. I don’t envy those guys trying to get CamTasia working in the new Vista video environment. Thankfully SnagIt works properly – that I really can’t live without. <s>
What’s really odd about this episode is that I had these problems on several machines. But in retrospect all of the machines also use nVidia video cards although they are different types of cards of various different generations. I still find it really odd that so few people ran into this issue – assuming it’s the nVidia drivers it would seem that this would catch a lot of people. <shrug>
Now the question is - what the heck is Intellisense doing to get confused by the video driver? And why only in ASP.NET pages when trying to get the generated control definitions?
Other Posts you might also like
- Map Physical Paths with an HttpContext.MapPath() Extension Method in ASP.NET
- Getting the Client IP Address in ASP.NET Core
- Adding minimal OWIN Identity Authentication to an Existing ASP.NET MVC Application
- Resolving Paths To Server Relative Paths in .NET Code
- Getting the ASP.NET Core Server Hosting Urls at Startup and in Requests
The Voices of Reason
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
Check this out this blog post about recording Vista with Camtasia Studio. It can be done with a few tweaks. http://www.techsmith.com/community/blogcomments.asp?thread=267
Also, we do offer free tech support. Or, just drop me a line...Thanks for using SnagIt and Camtasia!
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
The latest drivers from nVidia sorted that out, but still have to go into design view in ASPX pages to get the intellisense to work in code behind.
BTW - Merry Xmas Rick. Spare a thought for those of us freezing away here in Blighty!
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
Whatever timing mechanism is used by VS.NET to handle this appears to get thrown off by something running in my system. But it makes no sense that should happen JUST WITH THE DAMN ASP.NET control definitions that get auto-generated. All other Intellisense works just fine...
<sigh>
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
There's more info here:
http://www.west-wind.com/weblog/posts/9932.aspx
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
I have the same problem and have been waiting patiently for a fix...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
<% @Page Language="VB" Explicit="True" %>
disabled my intellisense.
Chaging it to:
<%@ Page Language="VB" Explicit="True" %>
solved the problem....
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
VS2005 + SP1
Windows XP SP3
Logitech MX518 mouse using only windows generic drivers
ATI Radeon 2400 pro
hitting ENTER after the /HTML tag did the trick...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
<%@ Register TagPrefix="wssuc" TagName="ButtonSection" Src="~/_controltemplates/ButtonSection.ascx" %>
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
I get no joy when trying any of the above. I have altered the /html line, changed the spacing around the @Page declaration, and changed the Tools, Options, Text Editor, All Languages, Hide advanced members checkbox. None of the above work.
I don't get any intellisense in the .ASPX file snippet shown below:
<%@ Page Language="VB" Debug="true" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <script runat="server" type="text/VB" language="vbscript"> Dim sSubPageName as string, sSectionName as string, sLinkName as string dim s as Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load If IsPostBack Then ' statusMessage.Text &= "hi" end if statusMessage.Text &= sSectionName end sub </script> <html> ... </html>
# re: Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...
>> Normally parser runs on idle and parses incrementall. As you have noticed though, switching between views forces complete HTML parser pass. There is a trick as well: placing caret below </html> and hitting ENTER should cause full parse. Also, deleting/undoing <html> or </html> causes full document parse as well.
Apparently the problem is that the old video driver was not allowing enough idle time to let VS start parsing the page on its own. This might also explain why I had additional problems in combination with SlickRun when Cursor Lock was active. It might also explain why my machine wasn't shutting down automatically when 'idle'.
I wish I had known about this latter trick a while ago - that would have saved me a lot of grief <s>...