i'd be interested in what you find out. We have tons of problems with it. The
most reproducible is that if i have the aspx and the aspx.cs page open at the
same time, intellisense disappears. So when we work we try never to have both
a page and the codebehind open at the same time. Not sure if it is any page
or just the page for that specific codebehind. One person here thought the
bug was in the GUI designer for ASP pages but i believe it happens even if we
open the page in HTML mode, which is now our standard
We assumed it was a bug with the HTML handler in Visual Studio. However, you
mentioned using Infragistics, which we're also doing. i wonder if it's
perhaps a bug in their controls. i suppose i could write some tests with and
without infragistics controls and see if that helps
-baylor
"Bill Talada" wrote:
Intellisense used to work beautifully. In the last couple months, I have to
rebuild about every minute to keep intellisense working in dozens of
different projects. I moved all imports statements from forms to the project
and it worked slightly better. I removed an unused dll reference and it
worked slightly better. The other developer codes very different from me and
has the same complaints. I suspect maybe Infragistics controls 2005 v2 has
botched up intellisense. Anyone have some ideas?
