Everyone knows, VS2005 is a memory pig.  The project I work on is made up of over 50 projects in a single solution. Add to that Team Foundation Server and you've got a memory usage footprint that routinely is over half a gig just opening the solution.

Try this:

1. Open up task manager.
2. Open up the DNN Source project (or whatever large solution you're working on).
3. Note the memory usage in task manager.
4. Now, simply minimize Visual Studio.
5. Again, note the memory usage in task manager.
6. Restore VS from the tray to full view.
7. Now look at where memory usage is at in task manager.

Just to show some numbers, here is my scenario:

1. Once solution is open - 422,888 K memory usage.
2. Minimize VS2005 - 9,932 K memory usage.
3. Restore/Maximize VS2005 - 15,752 K memory usage.

Granted, memory usage will start to creep up while you're using it, but won't approach the original number. Even after a full build of all 54 projects, it's memory usage never gets above 144,168 K memory usage.

Pretty damn silly isn't it?

So next time your VS2005 starts to feel a little sluggish or slow responding, minimize it to the task area and then restore it.

Cathal,

Thanks for that link, it was a good read.