Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm also experiencing extremely slow responses generally from VS2010. I can type in a phrase, sit back and watch it typed out onto the screen a couple of seconds later. Using it's internal web server is extremely slow even when not debugging. It's unusable.</p> <p>Running it on Win7 Professional x32, with a web project built on .NET 4.0, converted from .NET 3.5 on VS2008 which ran fine but was when I was using W2k3 as my development machine to keep the speed up.</p> <p>All these are run as virtual machines using the latest version of VirtualBox (currently V3.2.8 r64453) on Linux Ubuntu 10.4 x64 on a massive machine. 2 x Intel i7 2.8GHz (8 virtual cores), 12GB RAM, NVidia 9600 GPU with 512MB RAM.</p> <p>VM is set up to give 2 cores to Win7 and 4GB RAM and 96MB Video RAM. VT-x, 2D &amp; 3D Acceleration and Nested Pages are enabled.</p> <p>VS2010 has been tried with and without Hardware Acceleration (as it uses WPF to display it's text editor! [why???]). With, you lose the text editor and menu bars; without, you get a barely usable system. I also have Reflection and Visual SVN installed. The machine is used for nothing else. Anti-Virus is run manually to keep the load down!</p> <p>[Rant Warning:] VS2010 runs like a dog and if it wasn't for the fact I've spent 11 months on this project for a client I've been working for for 7 years, I'd be redeveloping in PHP on responsive tools. I left M$ OS's for my business OS 2 years ago precisely because of freezes, slow downs and inexplicable changes taking weeks out of my productivity. Cost wasn't the issue, it was service. [Rant Over]</p> <p>I'm aware there are 3 items to this, VirtualBox, Win7 &amp; VS2010. It may be best for me to set up a Win2008 server VM and install VS2010 on that, I don't know at this point.</p> <p>If anyone has any clues how to get VS2010 to respond in a timely fashion I'd love to hear them.</p> <p>Craig</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload