Have you considered optimising your solution files? For example, have a couple of different solution files dedicated to the same set of projects but only containing a subset.
Eg. UI.sln -> Only contains the SL, shared proxy classes, Silverlight libraries and unit tests Services.sln -> Only contains the service layer projects, including the shared proxy classes Complete.sln -> The file that your continuous integration server uses to still ensure everyone is integrating. etc -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, 23 July 2010 10:58 AM To: ozSilverlight Subject: RE: Out of memory exceptions in VS2010 with Silverlight 4 Actually compile time and time to run takes a while anyway, so there is plenty of time to do other activities. T. On Fri, Jul 23rd, 2010 at 10:26 AM, Steven Nagy <[email protected]> wrote: > Yes but everyone's Facebook status will have been updated during that > outage period so its not a total loss... ;) > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Friday, 23 July 2010 10:21 AM > To: [email protected] > Subject: Out of memory exceptions in VS2010 with Silverlight 4 > > Hi all, > > It's Friday, so I thought I would let you know about one issue in our > team. > > Basically, we are running 32-bit Windows XP. The machines have > anywhere between 2 and 4GB RAM. Everyone in the team gets System Out > Of Memory Exceptions. When that happens, you have wasted the compile > time, and then you have to shut down VS2010, start it up, then open up > the solution. The solution has a significant number of projects in it. > Apparently this problem only happens in 32-bit windows. > > So for the whole restart process, we have assigned 10 minutes to this > procedure. > > Next we have logged the total crash time for our team of 7 developers > (some days people were away, but it ultimately doesn't matter). > > The times lost are as follows: > 14th 240 mins > 15th 100 mins > 18th 120 mins > 19th 60 mins > 20th 200 mins > 21st 100 mins > 22nd 140 mins > > we have assigned an arbitrary value against the times of $100/hour. So > the loss of productivity is > 16 hours @ $100/hour = $1600. > > Hopefully soon these figures will become a significant enough figure > to justify an upgrade! > > Regards, > Tony > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > > _______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight _______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
