Hi,
Could someone please point me in the right direction regarding this error message that we seem to get all too often.
It says that I'm out of memory, but I fail to see how. The machine is equiped with 3GB of mem, according to task manager there is approx. 1,2GB still free (and about 6GB of virt.mem) and devenv.exe is sitting at about 750MB of allocated mem.
RestartingVisual Studiosolves the problem, but it just takes a few hours then we are back at the same point. Its not just me having this problem, its the whole dev.team.
Something inside VS seems to be eating up the memory.
The version of VS is: Microsoft Visual Studio 2005 Professional Version 8.0.50727.762 (SP.050727-7600) with SP1
Thankful all hints regarding this.
The "ResolveAssemblyReference" task failed unexpectedly.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Microsoft.Build.Shared.ExceptionHandling.RethrowUnlessFileIO(Exception e)
at Microsoft.Build.Tasks.ReferenceTable.SetPrimaryFileItem(ITaskItem referenceAssemblyFile)
at Microsoft.Build.Tasks.ReferenceTable.SetPrimaryItems(ITaskItem[] referenceAssemblyFiles, ITaskItem[] referenceAssemblyNames, ArrayList exceptions)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute(FileExists fileExists, DirectoryExists directoryExists, GetDirectories getDirectories, GetAssemblyName getAssemblyName, GetAssemblyMetadata getAssemblyMetadata, GetRegistrySubKeyNames getRegistrySubKeyNames, GetRegistrySubKeyDefaultValue getRegistrySubKeyDefaultValue, GetLastWriteTime getLastWriteTime)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)
Regards,
Mikael | | nbismlm | Does it always crash at the same place, or is this just an example callstack?
Is there anything special about the solution?
Can you narrow down what causes memory to go up -- for example, a clean build makes memory jump in task manager. | | DanMoseley - MSFT | Thanks for replying.
The solution consists of 21 VB.NET projects of various sizes including one Web Project. The solution is converted from VS2003.
One of the projects contains more than 500 DataSet-files (.xsd) with with generated files from the MSDataSetGenerator.
Doing a rebuild of the whole solution gives 4 failed projects with the exact same error message as mentioned earlier. The rest of the projects either succeeds being compiled or fails due to being depending on the others that failed. The 4 failed projects are the biggest ones. But not really that big at all.
I have about 700MB of free physical memory when doing this.
After restarting VS2005 and loading the project devenv.exe is allocating about 622MB of memory.
After making a rebuild of the solutions its allocating about 650MB of memory, and everything went fine.
Before the restart of VS2005 it was allocating 890MB.
Building and rebuilding doesn't change the memory usage by much.
I cant really find an action that takes memory without giving it back again.
People editing many files seems to get this error quicker than those just changing a few files, and those working with the Web app, gets it even quicker. But maybe I'm just guessing the wrong thing here.
If there is any other info that you need to help us solve this problem, then I would be more than happy to supply it to you.
Thanks,
Mikael | | nbismlm | My team also has this problem.
It is painful, to say the least.
As of yet I have not been able to narrow it down to any specific cause.
For a time I thought it might be related to using the resharper plugin.
This does tend to add more to memory usage but is not solely responsible. I have these issues even without resharper.
The vs ide gradually becomes slower, chewing up more and more resources, until finally it does any one or combination of the following:
-- Displays out of memory exceptions in the ide where controls shoudl be or when trying to change a control's property.
-- Silently crashes and disappears
-- Becomes completely unresponsive
I welcome any ideas, suggestions, info, etc.
| | Anonymous4638 |
I also have a Memory Problemwith the german Version of VS2005 SP1:
System.OutOfMemoryException: Eine Ausnahme vom Typ System.OutOfMemoryException wurde ausgelöst.
bei Microsoft.Build.Shared.ExceptionHandling.RethrowUnlessFileIO(Exception e)
bei Microsoft.Build.Tasks.ProcessResourceFiles.ProcessFile(String inFile, String outFile)
bei Microsoft.Build.Tasks.ProcessResourceFiles.Run(TaskLoggingHelper log, ITaskItem[] assemblyFilesList, ArrayList inputs, ArrayList outputs, Boolean sourcePath, String language,
String namespacename, String filename, String classname, Boolean publicClass)
bei Microsoft.Build.Tasks.GenerateResource.Execute()
bei Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup p
rojectPropertiesAvailableToTask, Boolean& taskClassWasFound) KMC
Visual Studio 2005 Professional Edition - DEU Service Pack 1
Windows2000
2048MByte Ram
Regards,
Christoph
| | CeVau | I am getting the same error . The build fails . Interestingly I used resharper ADD-In too . I assumed it was a resharper problem , but removing resharper hasnt solved the error either . | | JeyaPradeep | Have you tried running it from the command line? Open up a command prompt, and run msbuild <SolutionfileName.sln> . Does the crash happen then?
This should save you the 622mb memory that devenv takes. Let me know how it goes.
Thanks,
Jerel
| | Jerel Frauenheim - MSFT | Christoph:
This is different from the above crash, mostly because of the callstack information. Can you tell me a little bit about the project you are trying to build?
Thanks,
Jerel | | Jerel Frauenheim - MSFT | For me, it is not always compiling that causes the problem. Actually, I seldom have the problem when compiling. I most often have the issue when coding or using designer in the visual studio IDE. What happens is the ide becomes unresponsive... sometimes it silently crashes, sometimes i get the annoying Visual Studio Is Buys information bubble... sometimes when in the designer .. instead of displaying the controls that SHOULD be there on a given aspx.. while trying to render them in the designer... it renders them as a box that reads "Out of memory Exception"
any thoughts on this? | | Anonymous4638 | I just had the out of memory problem again, so I opened the command prompt (without closing VS) and run msbuild on my solution. Everything went fine, no errors. Switched back to VS and tried again, andI stillgot the out of memory error.
I have about 1,2GB of free physical memory left according to taskman. | | nbismlm | That's interesting. At least you do have a work around, with the command line build working.
Without having a full project tree this gets a little difficult to debug. I'll continue to look at it and let you know. Anyone, please let me know if the command line option isn't a work around for you.
Jerel | | Jerel Frauenheim - MSFT | Hi again, is it possible that Win2000 is the problem ?
It seems that we don't have this problem with the same project with WinXp.
Regards,
CeVau | | CeVau | We have the same problem here with a rather big solution made of 14 projects and several thousands of classes. This problems occures more and more often as the solution grows. VS is running on Windows XP andResharper was never used nor installed.
Is there a Registry Key or any other meanto configure VS to use more RAM in a similar way as Eclipse do?
A fix would definitely be a great releif for all our team.
Regards,
François | | François Bochatay | i have the similar problem,My OS is XP pro.here are the Exception:
Error1The "ResolveAssemblyReference" task failed unexpectedly.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Reflection.AssemblyName.nGetFileInformation(String s)
at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
at Microsoft.Build.Shared.AssemblyNameExtension.GetAssemblyNameEx(String path)
at Microsoft.Build.Tasks.SystemState.GetAssemblyName(String path)
at Microsoft.Build.Tasks.Resolver.FileMatchesAssemblyName(AssemblyNameExtension assemblyName, Boolean isPrimaryProjectReference, Boolean wantSpecificVersion, Boolean allowMismatchBetweenFusionNameAndFileName, String pathToCandidateAssembly, ResolutionSearchLocation searchLocation)
at Microsoft.Build.Tasks.Resolver.ResolveAsFile(String fullPath, AssemblyNameExtension assemblyName, Boolean isPrimaryProjectReference, Boolean wantSpecificVersion, Boolean allowMismatchBetweenFusionNameAndFileName, ArrayList assembliesConsideredAndRejected)
at Microsoft.Build.Tasks.Resolver.ResolveFromDirectory(AssemblyNameExtension assemblyName, Boolean isPrimaryProjectReference, Boolean wantSpecificVersion, String[] executableExtensions, String directory, ArrayList assembliesConsideredAndRejected)
at Microsoft.Build.Tasks.DirectoryResolver.Resolve(AssemblyNameExtension assemblyName, String rawFileNameCandidate, Boolean isPrimaryProjectReference, Boolean wantSpecificVersion, String[] executableExtensions, String hintPath, String assemblyFolderKey, ArrayList assembliesConsideredAndRejected, String& foundPath, Boolean& userRequestedSpecificFile)
at Microsoft.Build.Tasks.AssemblyResolution.ResolveReference(IEnumerable`1 jaggedResolvers, AssemblyNameExtension assemblyName, String rawFileNameCandidate, Boolean isPrimaryProjectReference, Boolean wantSpecificVersion, String[] executableExtensions, String hintPath, String assemblyFolderKey, ArrayList assembliesConsideredAndRejected, String& resolvedSearchPath, Boolean& userRequestedSpecificFile)
at Microsoft.Build.Tasks.ReferenceTable.ResolveReference(AssemblyNameExtension assemblyName, String rawFileNameCandidate, Reference reference)
at Microsoft.Build.Tasks.ReferenceTable.ResolveAssemblyFilenames()
at Microsoft.Build.Tasks.ReferenceTable.ComputeClosure()
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute(FileExists fileExists, DirectoryExists directoryExists, GetDirectories getDirectories, GetAssemblyName getAssemblyName, GetAssemblyMetadata getAssemblyMetadata, GetRegistrySubKeyNames getRegistrySubKeyNames, GetRegistrySubKeyDefaultValue getRegistrySubKeyDefaultValue, GetLastWriteTime getLastWriteTime)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)Symax.Mextra.BL
| | ChuanboZhang | I hadnt replied to your question . Yes the build succeeded from the command line . | | JeyaPradeep | We'll need projects/solutions we can reproduce this with in-house in order to investigate. If you can provide this, please open a bug with the instructions at the top of the forum.
I realize I often say "please open a bug" but frankly if there's a crash I haven't seen before, it is not possible to debug it in the forums.
Dan | | DanMoseley - MSFT | Ok, i see there are many persons affected by this problem.
We are the next guys who are exposing with this circumstance.
My suggestion is that we should joint together and create a such solution.
May it takes a long time, but we have something to show that guys.
How does it strike you?
Do you think that a diagnostic Protokoll out of Buildprocess with that Error may help?
I found this option todays afternoon  | | sunspeed | I have the same problem with a large project using crystal reports I have taken over from someone else. Visual studio takes a very long time to draw the form designer pages, and I get can not write metadata to file out of memory and I just today got an out of memory exception in the form designer. Its very annoying to constantly close and reopen visual studio 2005
I get unexpected error writing metadata to file somepath.dll not enough storage is available to complete operation but I have lots of every type of memory. I close visual studio and reopen it and it works a few times before I get the same message.
| | abcdefgqwerty2 |
This error is becoming a nightmare. I also can build from Command line but the OutofMemory nonsense how do we escalate and find a solution.
| | Richard Keller |
I'd like to figure out whether this callstack is causing the out of memory, by attempting to do some excessive allocation, or whether it is just the victim (albeit consistently) of excessive memory use elsewhere in VS.
Just before the build, are you short on memory or is plenty free?
Dan | | DanMoseley - MSFT | Nope. Lots of memory free. Command Line works great , build in development is still bombing out. This is not a user workstation problem as evidenced by the number of posters. | | Richard Keller | Whatever it is is local to VS2005 I installed VS2008 on my PC and upgraded problem solution and it worked fine without modification.
Richard
| | Richard Keller | Hi All, (excuse my english writing, I'm french) I'm using VS2008 RTM, and I have the same problem. My solution is quite heavy : 20 projects including a web site, and an assembly containing Crystal reports rpt files as embedded resources. I have .Net framework 3.5 installed, ASP.Net 3.5 extendsions, Crystal reports 11 server, fresh release of Telerik radcontrols for Asp.Net suite, Syncfusion's components last version. I'm detailing everything so that we can see if we share a common third party component that may be the culprit. Hope we'll be able to.... As I'm writing this post 'm rebooting my VS2008 for the 10th time today. This is no RAD anymore....  Bye Morgan | | Morgan Richard | Morgan, can you share your callstack too? Is it always the same callstack? Is there any way to reduce the system down to find some minimum scenario that reproduces it?
We can be contacted at msbuild@microsoft.com. (Which didn't work for a while late last year, but now that is fixed.)
Dan
| | DanMoseley - MSFT |
Got the same "out of memory" exception from VS 2005 when editing a webpage with lots of controls. I updated .NET framework 2.0to service pack 1 and the problem is gone! The IDE is so fast that it becomes productive again.
Regards | | Iczelion | Hi Dan, The only thing I can share is the build output as debugging doesn't seem to work for the scenario or maybe I'm missing something...(tell me how to debug if it's the case) Here's the output :
Code Snippet
------ Build started: Project: XXXXX.2008.3_5, Configuration: Debug Any CPU ------
C:\WINDOWS\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /unsafe- /checked- /nowarn:1701,1702 /nostdlib- /errorreport:prompt /warn:4 /baseaddress:285212672 /define:DEBUG /reference:"C:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.CrystalReports.Engine.dll" /reference:"C:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.ReportSource.dll" /reference:"C:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.Shared.dll" /reference:"C:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.Web.dll" /reference:"C:\Program Files\Microsoft Visual Studio 8\ReportViewer\Microsoft.ReportViewer.WinForms.dll"
........... (my own assemblies)
/reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /debug+ /debug:full /filealign:4096 /keyfile:..\..\..\XXX.snk /optimize- /out:obj\Debug\XXX.dll
fatal error CS0013: Unexpected error writing metadata to file 'C:\.....\obj\Debug\XXX.dll' -- 'Mémoire insuffisante pour cette opération. '
Compile complete -- 1 errors, 0 warnings
Une exception de type 'System.OutOfMemoryException' a été levée.
========== Build: 10 succeeded or up-to-date, 2 failed, 0 skipped ========== The output is allways the same. I don't have much time for the moment but I will create a sample project without my own assemblies and code and test it. The last thing which may be important is the size and type of embedded resources in XXX.dll -.jpeg images : 91Kb -.datsource files : 3 files, 1 Kb each, auto generated in Properties folder -.rpt files : total of 36 Mb for 6 files -.pdf files : total 1 Mb for 3 files Yes I agree with you this looks more like a repository than an assembly. I have at every moment at least 800Mb free memory. Hopes this helps Morgan | | Morgan Richard | Here is the stack trace I encouter since this morning (with no references changes) :
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(1315,9): error MSB4018:
The "ResolveAssemblyReference" task failed unexpectedly.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Microsoft.Build.Shared.ExceptionHandling.RethrowUnlessFileIO(Exception e)
at Microsoft.Build.Tasks.ReferenceTable.SetPrimaryFileItem(ITaskItem referenceAssemblyFile)
at Microsoft.Build.Tasks.ReferenceTable.SetPrimaryItems(ITaskItem[] referenceAssemblyFiles, ITaskItem[] referenceAssemblyNames, ArrayList exceptions)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute(FileExists fileExists, DirectoryExists directoryExists, GetDirectories getDirectories, GetAssemblyName getAssemblyName, GetAssemblyMetadata getAssemblyMetadata, GetRegistrySubKeyNames getRegistrySubKeyNames, GetRegistrySubKeyDefaultValue getRegistrySubKeyDefaultValue, GetLastWriteTime getLastWriteTime)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)
I've cleaned the solutions, restarted VS. The solution now compiles properly (4Gb ram, 600Mo taken by VS).
- Edited byThomas Bol Monday, June 16, 2008 1:20 PMDetails added
-
| | Thomas Bol | Hi
Has anyone come up with a fix for this devenv.exe memory error yet?
Thanks
| | itmorr | I have a different situation where I have couple of resource files that I need to include in the build and they are about 1.2GB in my project and when I compile the project in command line, it bombs out with the same error fatal error CS0013: Unexpected error writing metadata to file 'd:\res.exe' -- 'Not enough storage is available to complete this operation. '
Is there a limiation on the csc compiler on command line or is it the RAM memory itself is the cause?
Thanks.
Everyday learning something new like this one :) | | dbcuser | This is the exact error message:
ERROR: Could not find file '[filename.zip]' 'Insufficient system resources exist to complete the requested service.'
| | itmorr | Hi,
Three years developping with Visual Studio 2005 and I always had this message!
The only thing to dounfortunetely is to restart VSTO and continue, but of course this is upsetingdoing that every
one or two hours.
I recently change to VSTO 2008 and I hope this is going to be fixed! Please!
P.S.:
I had thefollowing messages during all my 3y experience with VSTO 2005:
when compliling an imported project from VSTO 2003: the Out of Memory message.
when opening a big Form or with a lot of controls: Out of memory, not enough space ressources to
continue with this operation.
when compiling and using some predefined Crystal Reports : Not enough memory to continue with
this operation.
For all this messages theonly workaround is restarting VSTO 2005 and continue. | | netomin | Hi, I'm using ReportViewer component on VS 2008 SP1, I'm getting a System out of memory exception. I'm building a large local report (rdlc) for a client. The application can be briefly described as follows: 1. User can decide what to see based on 3 combos (which will define the report parameters) 2. Datasources are xml files (there are 7 major sections on the report each one has one data source sizing from 1kb to 200Mb) 3. The xml files are added as binary resources 4. xml files are read using Memory Streams (1 Memory stream for each file) 5.DataSets are filled from the Memory Streams (1 DataSet per Memory Stream) MyDataSet.ReadXml(MyMemoryStream)
As soon as the dataSet is loaded the corresponding memory stream is freed
MyMemoryStream.Close();
MyMemoryStream.Dispose();
//But checking the memory usage from Task Manager shows no change, memory is not released
6. Report data sourcess are added
7. Show Report
this.MyReport.RefreshReport();
//after refreshing report the datasets are disposed
dsMyDataSet1.Dispose()
dsMyDataSet2.Dispose(), etc...
//But checking the memory usage from Task Manager shows no change, memory is not released
8. If user makes a different selection (using the comboboxes):
a. MyReport.Clear();
b. MyReport.LocalReport.DataSources.Clear();
c.MyReport.ProcessingMode dMicrosoft.Reporting.WinForms.ProcessingMode.Local;
d. MyReport.LocalReport.ReportEmbeddedResource = "MyReport.rdlc";
e. MyView1.Table = MyDataSet1.Tables[0];
f.MyView2.Table = MyDataSet2.Tables[0];
g.MyViewN.Table = MyDataSetN.Tables[0];
// for each dataSet or DataView
h. MyReport.LocalReport.DataSources.Add(new ReportDataSource("Ranking_r", MyDataView1));
i.this.MyReport.RefreshReport()
j. Again release datasets: MyDataSetN.Dispose()
Memory Usage never decreases (but it does increase... )until the App is closed. Task Manager shows a Mem Usage over 800,00K
Even building the application is becoming a nigthmare...
Some building errors:
The "GenerateResource" task failed unexpectedly .System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.at System.IO.MemoryStream.set_Capacity(Int32 value)
at System .IO.MemoryStream.EnsureCapacity(Int32 value)
at System .IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System .IO.BinaryWriter.Write(Byte[] buffer, Int32 index, Int32 count)
at System .Resources.ResourceWriter.WriteValue(ResourceTypeCode typeCode, Object value, BinaryWriter writer, IFormatter objFormatter)
at System .Resources.ResourceWriter.Generate()
at System .Resources.ResourceWriter.Dispose(Boolean disposing)
at System .Resources.ResourceWriter.Close()
at Microsoft .Build.Tasks.ProcessResourceFiles.WriteResources(IResourceWriter writer)
at Microsoft .Build.Tasks.ProcessResourceFiles.WriteResources(String filename)
at Microsoft .Build.Tasks.ProcessResourceFiles.ProcessFile(String inFile, String outFile)
at Microsoft .Build.Tasks.ProcessResourceFiles.Run(TaskLoggingHelper log, ITaskItem[] assemblyFilesList, ArrayList inputs, ArrayList outputs, Boolean sourcePath, String language, String namespacename, String resourcesNamespace, String filename, String classname, Boolean publicClass)
at Microsoft .Build.Tasks.GenerateResource.Execute()
at Microsoft .Build.BuildEngine.TaskEngine.ExecuteInstantiatedTask(EngineProxy engineProxy, ItemBucket bucket, TaskExecutionMode howToExecuteTask, ITask task, Boolean& taskResult)
Unexpected error writing metadata to file 'C:\Path' -- 'Not enough storage is available to complete this operation. '
Output file "C:\Path\obj\Debug\MyApp.Properties.Resources.resources" is possibly corrupt
Cannot write to the output file "C:\Path\obj\Debug\MyApp.Properties.Resources.resources". The process cannot access the file 'C:\Path\obj\Debug\MyApp.Properties.Resources.resources' because it is being used by another process
Thanks in advance for any help. This report must be delivered to client by Aug 25 :( | | Bruno Ramon | I wonder if there is a link between this error and the number of warnings. I upgraded a huge project from VS2003 to VS2005. This resulted in a lot of warnings. The project builds fine other than the annoying Out of memory every 10 minutes. Does anyone that is having the same error also have a lot of warnings? | | nate22405 | Almost certainly, given the various different callstacks, this is not a bug in MSBuild. AT this point we need a Connect issue opened if possible, with a reliable way for us to reproduce it. I will make sure it is routed to the most plausible owning team.
I'm sorry for the pain you're suffering with this problem.
Dan -- MSBuild
developer on msbuild | | DanMoseley - MSFT | I thought I mention that I am seeing a simiarerror when I attempt to save very large contents of the Output window. My debug output is over 200,000 lines.
It won't copy to the clipboard so I thought I'd do a save as. The message "The operation could not be completed. Not enough storage is available to complete this operation." I have plenty of hard disk space.
When attempting to copy to the clipboard I see "The selection is too large to copy to the clipboard. Please make a smaller selection and try again".
Since most people see a similar message during compiling I suspect that creatinga very large file using .NET compiler or linker may be an issue. A work around may be to break up the problem projects into smaller projects.
Again the common denominator maybe creating very large files.
This does not explain the appearently accumulative nature if the problem.
J.R. Heisey
Synaptics, Inc.
| | J.R. Heisey | Uninstall Resharper
Regards
Sai Saitish
Indian Servers
www.indianservers.com
| | Sai Satish | Are you by chance using a shared directory for references?
My team had this problem today, we were all pointing to a shared directory on a remote box for our reference .dlls.
This was the system with the problem, not our local machines. Apparently the remote box was too bogged down to copy the files back to us when our build was requesting them.
Just one more thing to try...
Good luck! | | GregTV |
|
index > MSBuild > MSB4018 Out of Memory Exception