There is a patch out for VS 2008 IDE in regards to the XML documentation and Intellisense.  This was something that was causing us a lot of issues and the patch helped a lot!  You might contact Microsoft and tell them about your symtoms and they may give you that same patch.  I would post it but I am not sure if we are allowed to do that and I don't want Microsoft on my back

Hi Trent,

Thanks for this. I have spent about a week working with my AV on and off. Not really much difference between the 2 states to be honest. The interesting thing is, I don't get the memoryexception with VS2005. I also don't get the memoryexception in my application. It's always just in the VS2008 IDE.

Thanks for the ideas anyhow.

best

Geoff.

The errors that it seems to be giving you though are out of memory exceptions.  Memory exceptions don't just come from not having enough memory.  You can blow the stack or even have memory that is corrupt or incompatible with the mother board and run into things like this.

Now I am not saying that this is your issue, just something to look at.  VS is always good about holding onto things in the AppDomain at certain times producing an error liek you are running into.  But one major culprit of memory exceptions is real-time virus software.  If you have any type of real-time virus software running...kill it!  Real-time virus software scans every file that is touched and everyting that is opened into memory, which VS has MASSIVE memory management through the design-time environment.  It also uses a stub file called the vshost (if you are allowing the vshost to run, which by default it does).  Those are all of the places I would start looking.

Trent,

I don't know if this is related, as this is the first time I have noticed the IDE actually 'blaming something' for the exception.

I do use this control on pretty much every form I have.

thanks

Geoff.

Hi Trent,

Sometimes, if I try and open a form, I get the nice coloured VS2008 form that shows that a system.outofmemoryexception was thrown.

Other times, I just get a plain old dialog showing the same exception, like it can't be bothered showing me the 'nice' screen.

This is only occurring in the IDE. Also, I can pretty much guarantee that it will happen, immediately after a build, especially of the business layer.

thanks

Geoff.

What exception are you getting?

Guys,

Have you any experience of the above exception occurring in the above configuration? I get this numerous times a day, and the only way out is to quit VS and restart.

It usually happens if I have a particular form open, just after a build. The application continues to run. I have 4GB ram in this system and I know it's not running out of memory. However as it seems to happen after a while, there is something somewhere that isn't releasing all it should. It only happens in the IDE, my app is fine.

It's just annoying.

thanks in advance for any ideas.

Geoff