Beside the regular culprits , an offline database will cause Intellisense to fail as well. Detaching or bringing the offending database online will resolve the problem.
It appears that our run of fairly benign VS SP’s is over… I've now installed the VS 2010 SP1 in a few simple test environments (x64) and all of them are having issues. Add-in failures, failed package loading, missing SQL Intellisense, XAML designer failure...
First and foremost, if you're using Office 2010, Paradox support has been removed ( http://technet.microsoft.com/en-us/library/cc179181.aspx ). You'll need Access 2007 or earlier. If you're reading this, then you've probably run in to a cryptic error...
I don’t know when it started or why, but I love Halloween (and autumn for that matter). So keeping the tradition of Halloween alive, I’ve decided to share some “horror” stories from the software/IT field over the next few weeks...