Tuesday, September 18, 2007
Posted on Tuesday, September 18, 2007 8:15:06 PM (Mountain Daylight Time, UTC-06:00)  Comments [2] | 
Categories: .NET | Visual Studio 2005

My system was acting kind of slow, so I popped up Task Manager to see this...

dev-env-memory

This is a new personal best in terms of memory use by Visual Studio 2005 (devenv.exe) - 900 Mb.

Granted, I have 26 projects open but this is out of hand.

sol-exp

When I've looked into this in the past I have not seen any info on memory leaks etc, but if that's not the issue, then how how how does this process expand to this size? I re-started Visual Studio and now I'm back at a much more manageable 400Mb. Sigh.

Thursday, September 20, 2007 12:00:15 PM (Mountain Daylight Time, UTC-06:00)
26 projects!!!!
That might explain it.
VBAHole22
Friday, September 21, 2007 11:45:32 AM (Mountain Daylight Time, UTC-06:00)
That's just the framework part of our project - there are another 5 or so projects which are the actual business logic. The whole thing behaves in our build process, but VS.NET seems to be choking. I will say that we are actively refactoring this code base down into fewer projects - just this week we have collapsed 4 solutions out of the mix.

Not that I'm much of a zealot either way, I will say that VB.NET's background compile on the fly seems to cause problems with this many projects - it has a hard time keeping up as I make changes, and too frequently the IDE dies during this process. I've heard that large C# projects don't suffer from this as much.

Dave
Comments are closed.