5 ms·
It looks like they are implementing the functionality from a lot of the plugins available for VS2010 and making them standard functionality. My biggest issue w
by dav-id 15y ago
It looks like they are implementing the functionality from a lot of the plugins available for VS2010 and making them standard functionality.
My biggest issue with VS2010 is the amount of memory it consumes. I hope they do something about that or some how let me disable functionality that I don’t need so I can reduce the footprint.
Some of the icons in the screenshots do in my mind look to be an improvement whilst others are so totally different that I am sure will frustrate the hell out of me until I have adjusted.
I know those screenshots are to show off as many widgets as possible but is it useful to show the tool with about 10% screen real estate dedicated to actual code.
- recoiledsnake 15y ago>My biggest issue with VS2010 is the amount of memory it consumes RAM is so cheap now that there is really no excuse for developers to skimp on it. I would rather hope that they work on improving the product in other areas than optimize it for 1GB. If there are leaks however, they need to be addressed.
- to3m 15y agoVS2010 is still a 32-bit app. This puts a limit on just how much RAM it can use. I for one might be a little less alarmed by (though probably no more happy about) its carefree attitude if it were a 64-bit app.
- kazing 15y agoI have not heard of a single VS instance taking over 4GB of RAM. The only time you'll get into trouble is with multiple VS instances - and there 40 bucks for another 4GB of RAM pay off instantly.
- silon3 15y agoI regularly get problems when reaching ~2GB ram on Windows Server 2008 32 bit (in vmware).
- brass9 15y agoWhile VS itself doesn't consume large amount of memory, Resharper is a voracious memory eater. I used to regularly encountered OOM exceptions - not due to insufficient memory, rather because of excessive .net memory fragmentation brought about the holy marriage of VS2010 & R#. IIRC, this type of memory problem did not occur in VS2008 too frequently. Recent versions of R# have ameliorated the problem to a large extent however.
- nefasti 15y agoVisual Studio: Why is there no 64 bit version? (yet) -http://blogs.msdn.com/b/ricom/archive/2009/06/10/visual-studio-why-is-there-no-64-bit-version.aspx http://blogs.msdn.com/b/ricom/archive/2009/06/10/visual-stud...