Yeah, I have this problem too. It's damn annoying. Have you tried just doing a rebuild of the solution instead of restarting VS though? That (often) works for me. Still, it would be better that it didn't exist as a problem.
Chris On 23 July 2010 10:20, <[email protected]> wrote: > 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
