Thank you for your time.
Cheers,
Bob
Are you sure you have enough HDD space as well as enough memory? Close all background applications before opening VS.NET and try to compile again.
When does this happen?
I'm working on a project in Visual Studio 2005 (VB.NET) and from time to time all developers on this project get this error;
Sometimes this same error is the cause for a complete shutdown of VS. Not only the compiler, but the whole thing is shutdown. More annoyance here...
Does anyone know how we can fix this issue? It's probably not a question of disk space, I've got plenty. Memory is also not the issue. Three developers are working on this solution and we all got this issue. I've tried searching online, but couldn't find the solution....
The solution itself contains about 921 files in 175 folders. It contains about 9 projects. We have some UserControls though, some of which are huge, alot of controls on those. Some day evrything goes allright, but sometimes it craches about every half an hour. We can't tell if it's any action we do that causes the crash. It it's even related to running the Build or Rebuild command. We're sometimes just working, typing and suddenly the error occures.
Please help me out here, thx!
Bob
Hi Bob,
Have you applied the latest service pack for Visual Studio 2005? If not, I suggest you to apply the latest service pack.
If you’re using Vista, please also make sure that Visual Studio 2005 Service Pack 1 Update for Windows Vista has been installed.
Thanks!
Thank you for your reply.
We are using Visual Studio 2005 (Team edition) with service pack 1 on XP machines. We have installed the service pack 1 for VS 2005. 
Bob
Bob Joziasse wrote:
Hi Feng Chen, Thank you for your reply.
We are using Visual Studio 2005 (Team edition) with service pack 1 on XP machines. We have installed the service pack 1 for VS 2005.Bob
Hi Bob,
Are you using XP 32 bit edition?
How much memory is on each XP machine?
With so many files in a solution I would recommend 2 Gb of memory if running on 32 bit windows or
4Gb of memory with the 64 bit version of XP.
What is the smallest amount of
free hard-drive
space you are dealing with please?
Is the solution held on a server PC?
If so the server PC might be struggling with lots of instances of this solution open at once ( I am guessing here ).
Regards,
S_DS
All developers are working on Windows XP professional 32 bit.
My free space is about 20 GB. My internal memory is 2 GB with 1,2 GB available at the moment.
I've started Visual Studio and the readings are; 1 GB memory free and devenv.eve uses 225.408 K of memory. HD space is the same.
I will collect information about the free memory and diskspace at the moment the error occurs. This should not take more than a day 
. Unfortunately we can not (yet) force the error to happen, also due to the fact that we don't know what's causing it.
Bob
Is the solution held on a server PC?
If so the server PC might be struggling with lots of instances of this solution open at once ( I am guessing here ).
Regards,
S_DS
Sorry, didn't answered your question here. What exactly do you mean with 'held'? If you mean if the solution is loaded on a server PC, no. If you mean if we use source safe then yes, the code is stored on a source safe database (Team Foundation Server).
We do 'Get latest version' and all code is copied locally. From here we debug and develop the code and then check the code back in.
Bob
What is the smallest amount of free hard-drive
space you are dealing with please?
Hi,
Some data we collected;
| Developer | Error | Doing what | Memory free | Total | HD space free |
| Me | Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. Error Visual Basic compiler is unable to recover from the following error: Not enough storage is available to complete this operation. | Coding in the IDE | 852100 K | 2096496 K | 16 GB |
| Me | Error Unable to sign assembly: Not enough storage is available to process this command. | Compiling | 1090996 K | 2096496 K | 15,9 GB |
| Me | Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. Error Visual Basic compiler is unable to recover from the following error: Not enough storage is available to complete this operation. | Opening a Form | 967540 K | 2096496 K | 15,9 GB |
| Me | Unable to sign assembly: Not enough storage is available to process this command. | Compiling | 791804 K | 2096496 K | 14,9 GB |
| 2 | Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. Error Visual Basic compiler is unable to recover from the following error: Not enough storage is available to complete this operation. | ? | 292584 K | 1037864 K | 21,5 GB |
| 2 | Unable to sign assembly: Not enough storage is available to process this command. | ? | 317560 K | 1037864 K | 21,5 GB |
Bob
Bob,
It appears that this error is usually caused by not enough memory, or rather a lack of available memory at the time.
Check out the Microsoft response at the bottom of this thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=971785&SiteID=1
You mentioned it is a large solution. Large solutions have had problems in Visual Studio in the past, and were supposedly fixed in SP1, though I still get issues from time to time. When you do a compile or first open the solution, keep an eye on your available memory. Sometimes it is better to break up a large solution and develop/compile it in chunks (Team Foundation Build can assist).
Also, it has been my experience as well that when either Visual Studio or a language compiler encounters an error, you will no longer have error checking and whatnot.
Hope this helps,
Steve - dotneticated.com
Thank you for your help. I have split up the solution and Ill test it during the comming week. I hope it does solve the problem, because it's hugely anoying.
Thank you all for your help. I will reply here and tell what my findings are.
Cheers
Bob
I've unloaded the projects that where not used that much. It did lower the rate of which the error occurs. For me it didn't occur anymore. For others the rate was reduced definately.
I will look at reducing the project size even more, but this will require some work. Thank you for the suggestion. Although it didn't solve the problem, it did reduce it so I can work from here 
. Thanks.
Cheers,
Bob
