> I've never experienced an out-of-memory with VS, so that whole argument is moot. Second-hand knowledge here- I heard that VS 2010 was delayed because it woul

> I've never experienced an out-of-memory with VS, so that whole argument is moot. Second-hand knowledge here- I heard that VS 2010 was delayed because it would crash out of memory under many common scenarios- like load WinForms designer, TFS and one other module and boom. So every team had to go on a serious diet. The only reason you haven't gotten an out of memory is that the VS team has been fighting like mad to support common scenarios in the 32-bit address space.