Lol, I don't get it why people get stuck with XP in 32b edition and all it's limitations. It's an OS designed 14 years ago!!! 14!! And released 12 years ago.
Do any of your guys drive a car 14 years old? Next thing you should do to yourself: - remove source control and do manual merges: cost $2000 - replace your locks from the doors with a dodgy one that takes 15 minutes to open: cost $500 and so on :) Sorry, I have to be a bit sarcastic on this :) How about: $1600 = 9 W7 Pro Licences if you buy them in a 3 licence pack (http://www.myshopping.com.au/PR--335070_Windows_7_Professional) $2000 = 8Gb of memory for almost all your 7 developers (http://www.staticice.com.au/cgi-bin/search.cgi?q=8gb+ddr2&spos=1) $1000 = 7200rpm HDDs for all your developers http://www.staticice.com.au/cgi-bin/search.cgi?q=7200rpm+500gb+hdd&spos=1 And you'll never see those problems again. 3 days of "lost" productivity and cost and your are done. You'll start being productive and remove all your frustrations. Corneliu. ________________________________________ From: ozsilverlight-boun...@ozsilverlight.com [ozsilverlight-boun...@ozsilverlight.com] On Behalf Of ton...@tpg.com.au [ton...@tpg.com.au] Sent: Friday, 23 July 2010 10:20 AM To: ozsilverlight@ozsilverlight.com 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 ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight _______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
