13 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Victor Zakharov commented  ·  August 22, 2012 1:07 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  VS 2010 is slow to load and unload, even on my Vertex 2 SSD, 16GB of memory and i7-2600. And yes, for this kind of hardware 5 seconds is considered slow.

• gast128 commented  ·  July 23, 2012 1:11 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Yes on my work with a DELL T3500 4 core Xeon with 6 GB and Windows 7 it takes more than 30 seconds to load VS2010. VS2003 on same machine loads under 5 seconds...

• Dev10 commented  ·  May 14, 2012 6:35 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The hard-disk takes a massive beating with starting up VS 2010 until Windows caches some of it. Running an ASP.Net app in debug can also thrash the disk. This is a terrible trend in MS products (SQL Server 2012 just hammers the disk when loading reports, or the management studio).

• Floele commented  ·  April 5, 2012 3:50 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @Benjol: Not a funny request, at my work place we have a lot of smaller projects that we open and close (and use at the same time) many times a day. So it does actually matter how fast VS loads. I'm happy to see that VS11 has improved quite a lot on that.

• Oather commented  ·  March 28, 2012 5:48 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  > why in the world would there be such a drastic difference betweem VS 2010 load time and VS 2008?

  .net

• Alon commented  ·  February 5, 2012 12:19 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Adding to the progress bar issue: Currently there is a progress bar indicating the progress of opening every project separately. What would be much better (in addition) is to have an overall solution opening progress bar.

• David Rathbone commented  ·  January 22, 2012 11:30 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Look at this Microsoft, You have uses that think VS2010 is slow to start... How about you guys being abit faster to fix it in a service pak!!!!!!!!!!!!!!!!

• Ümit Yıldız commented  ·  January 22, 2012 11:00 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I also think that this should be solved.

• Dean Jackson commented  ·  January 22, 2012 10:22 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  To those who might think this is a silly request: why in the world would there be such a drastic difference betweem VS 2010 load time and VS 2008?? If you think it doesn't matter, then I say what in the world could they have done to make it over twice as slow???

• Benjol commented  ·  October 18, 2011 12:01 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is a funny request, because *rationally* speaking, in most use cases (my usage anyway), the startup time is a tiny fraction of the time that I actually spend using VS. But *psychologically* it seems like forever because I'm "sitting there doing nothing"...

• ROCHE commented  ·  September 20, 2011 1:23 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It seems that VS search for the server during a long time before opening a solution, even if this one has been marked as off line. In my opinion, it is just a bug, if the solution is offline, please, don't search for an inaccessible server with a one minute long time-out. If you open several solutions, it is quite boring.

• drweb86 commented  ·  September 19, 2011 11:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Could you please ngen all .net applications automatically especially for limited user accounts ? So user compiles application, and when binaries changes, it ngens and executes?

• Justin Chase commented  ·  September 19, 2011 5:54 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  100% agree with this. Makes debugging VS extensions a true pain in the neck.