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,
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, ton...@tpg.com.au wrote:
Hi all,
Yes but everyone's Facebook status will have been updated during that outage
period so its not a total loss... ;)
-Original Message-
From: ozsilverlight-boun...@ozsilverlight.com
[mailto:ozsilverlight-boun...@ozsilverlight.com] On Behalf Of ton...@tpg.com.au
Sent: Friday, 23 July 2010
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
I might just point out, I'm running Windows 7 and get the errors. Kinda
agree on your perspective for keeping developers productive though :).
Chris
On 23 July 2010 10:52, Corneliu Tusnea corneliu.tus...@readify.net wrote:
Lol, I don't get it why people get stuck with XP in 32b edition and
Yea, I try that. We even clean it first, but it seems you are luckier than us
as it rarely works for us!
Could have something to do with all the extra stuff we have going on in our
systems. Having
Outlook open doesn't help. Having SQL Management Studio open also doesn't help.
We have both
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 steven.n...@readify.net wrote:
Yes but everyone's Facebook status will have been updated during that
outage period so its not a
Hi Tony,
This sounds like the same issue we are having on our major project (a
WPF/CAB project). Our Client solution has 66 project files in the
solution, and our middle tier has 77 project files. We are running on
Windows XP 32bit SP3. And yes, Visual Studio (2008) starts falling
apart
I have the same problem on my current client site with WPF / VS2008 /
XP 32bit. About 5+ times a day I get an out of memory error when
compiling. Only happens after editing in xaml text editor, it has
never happened after editing c# code. I have to restart VS and clean
the solution. If I
Tony,
To help with Carl's recommandations you can try to use this VS plugin:
Solution Load Manager:
http://visualstudiogallery.msdn.microsoft.com/en-us/66350dbe-ed01-4120-bea2-5564eff7b0b2
It allows you to select which projects to load when the solution starts and
delay load the ones you don't
That's the plan!
On Fri, Jul 23rd, 2010 at 11:02 AM, Corneliu Tusnea
corneliu.tus...@readify.net wrote:
Oh, just make sure you go for the x64 version of W7. (the packages you can
purchase they all have two DVDs in there one for 32b and one for 64b).
Trust me, you'll never look back! :)
11 matches
Mail list logo
