I was getting the following error during compiles: Not enough storage is available to process command
Read some articles that suggest I remove uneeded references... I remvoed about 7 Infragestic references that I wasn't using and the compile problem went away... I wasn't actually expecting it to work, now that it has... If there an easy way to determine which Infragestic DLL's I'm actually using?
If you want to see what DLLs you have loaded, at run-time you can look at the Debug -> Windows -> Modules window. I haven't seen the compile error before, though, but perhaps you are out of hard-drive space and you have Copy Local set to true, meaning that when you build, Visual Studio will create copies of the DLLs.
-Matt
Google search shows alot of posts with a similar problem and the common thread is that it is a problem with the infragestic DLL's. Your project upgrade tools appears to add all of your DLL's. I removed half of them and I am compiling fine. The problem is not disk space, I have 300 gigs free. Rather, the compilation runs out of memory.
We see this same issue of compile time "Not enough storage space..." quite often. Have to quit the IDE and reload. It's definitely some sort of memory leak and it's triggered when viewing forms in designer mode with Infragistics controls. It could be the size of the project, who knows. But I can trigger it after opening and closing a few forms. I've just gotten used to closing the IDE and re-opening. And it has nothing to do with disk space. Les
The project upgrade tool should definitely not add any DLLs to the project that weren't already there. I have never seen this behavior, but if it is occuring then it is a bug and needs to be fixed. I have compiled multiple projects that reference every DLL on my machine too and haven't hit this error before. The only possible issue I can think of is that Visual Studio can sometimes behave oddly when the CopyLocal property is set to true, but usually this just affects the design-time view of forms.
You may want to submit this issue, and the PUU issue, to Developer Support.