MaximumASP
Packet Sniffer


Visual Studio 2005 IntelliSense in ASP.NET pages issue resolved...

Posted by: Rick Strahls WebLog, on 18 Dec 2006 | View original

So it looks like I finally have some good news to report on the annoying Intellisense problem Ive 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...

Advertisement
Category: #Visual Studio | Other Posts: View all posts by this blogger | Login to add this post to your profile favorites Report as irrelevant | View bloggers stats

Similar Posts

  • Avoid IISRESET in ASP.NET applications (added bonus: ASPRESET) more
  • Software Development Conference 2006 more
  • Debugger Visualizer for BizTalk 2006: MessageContext more
  • Tips for writing Debugger Visualizers in VS.NET 2005 more
  • More Debugger Visualizer Goodness more
  • Client-Centric Approach of Atlas more
  • The Top 7 Things Microsoft Blew in VS 2005/ASP.NET 2.0 more
  • My Top 10 Favorite Features of the Visual Studio 2005 IDE more
  • Circular File References and Other ASP.NET 2.0 / VS 2005 Conversion Issues more
  • Interesting bug in Saxon.NET/Mono/OSX usage more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD