Is this really related to low memory? I heard before that VS.Net is memory hungry. I guess that you must have at least 1 gig of RAM on your computer so how much memory would really be needed for that monster to work well?

By the way not that I know anything about the .Net world... yet


>I get that occasionally, Einar. I usually just ignore it and it goes away eventually. <g> I've never lost anything. If it gets too persistent and doesn't go away after awhile, then I'll go ahead and close and restart VS.
>
>~~Bonnie
>
>
>>I have received the following error message from VS2003 today:
>>An error has occured which the C# compiler is unable to report due to low memory or possible heap corruption. It is recommended that you save all your files, close and restart Visual Studio.
>>
>>Has VS2003 ever told anyone else this?
>>This happends when I am hardcoding a byte array {byte[]) with 41K elements (just for some testing purposes). I've got a feeling it is related to intellisense issues.
>>
>>Einar