> On 1/24/06, Frans Bouma <[EMAIL PROTECTED]> wrote:
> > > Don't listen to Frans, it's not your fault for having
> betas installed.
> > You can then babble that people shouldn't listen to me, but what I
> > have to say is at least helpful, instead of :
> >
> > > VS2005 is a memory hog, plain and simple. And worse yet,
> it appears
> > > to behave itself on some peoples' machines, which is why
> you get the
> > > occasional "it works fine on my box" junk.
>
> But it is a memory hog, plain and simple. 20 minutes working
> with C# and it uses ~250 MB. Couple of points:
that's not my experience, and I have 2-3 devstudio's open at once, with
large projects. But then again, I don't do design
time stuff at the moment and don't use class diagrams or other design crap.
> To Frans: Microsoft *can* and *should* do better, so you
> don't really have to defend them (unless you've become a
> Microsoftee :) - the more we complain, the better they do (hopefully).
Funny, I recently got feedback I whine too much about Microsoft
products and should be more positive ;).
> To Stano: Memory is very cheap these days, so get 2 GB and VS
> won't look like a memory hog. It works for me :)
I don't think that solves his problem, as he uses 1.5GB of swap with a
project that shouldn't eat more than 200MB of ram
tops.
Apparently no VB.NET users on this list. Perhaps Stano can post on
vb.net forums and ask there again to see if other vb.net
users have the same problem.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
