On Friday, 9 October 2015 at 21:24:52 UTC, Jonathan M Davis wrote:
>> vs starts is usable in about 2 second for me also.  Try using a computer from the modern era with an SSD.
>
> LOL. I _do_ use a computer with an SSD.

On my machine vs2013 starts in 3 seconds: core i5 3470, 8gb RAM (3gb in use, 3gb cached), HDD 7200 rpm.

Also antivirus scans all processes on start or so my colleague reports, I didn't confirm it myself.

On Monday, 12 October 2015 at 10:25:49 UTC, Kagamin wrote:
> On Friday, 9 October 2015 at 21:24:52 UTC, Jonathan M Davis wrote:
>>> vs starts is usable in about 2 second for me also.  Try using a computer from the modern era with an SSD.
>>
>> LOL. I _do_ use a computer with an SSD.
>
> On my machine vs2013 starts in 3 seconds: core i5 3470, 8gb RAM (3gb in use, 3gb cached), HDD 7200 rpm.

It may have something to do with the projects that we have, but regardless of the reason, VS is incredibly slow to start and has been on every machine that I've used at my current job. Obviously, YMMV given that some of the folks here are saying that it's incredibly slow, whereas others are saying that it's quite fast.

- Jonathan M Davis

On Monday, 12 October 2015 at 12:10:15 UTC, Jonathan M Davis wrote:
> It may have something to do with the projects that we have, but regardless of the reason, VS is incredibly slow to start and has been on every machine that I've used at my current job. Obviously, YMMV given that some of the folks here are saying that it's incredibly slow, whereas others are saying that it's quite fast.

Well, loading a solution depends on its size, it's like databases. VS loads the solution quickly, then loads projects asynchronously. While they are loading you can press F6 to build the solution, use source control explorer etc.

On Monday, 12 October 2015 at 12:41:53 UTC, Kagamin wrote:
> On Monday, 12 October 2015 at 12:10:15 UTC, Jonathan M Davis wrote:
>> It may have something to do with the projects that we have, but regardless of the reason, VS is incredibly slow to start and has been on every machine that I've used at my current job. Obviously, YMMV given that some of the folks here are saying that it's incredibly slow, whereas others are saying that it's quite fast.
>
> Well, loading a solution depends on its size, it's like databases. VS loads the solution quickly, then loads projects asynchronously. While they are loading you can press F6 to build the solution, use source control explorer etc.

VS outright freezes with Windows saying that it's "not responding" for a couple of when I start it up. So, whatever it's up to, I can't do _anything_ with it for a couple of minutes. The rest of the box is usable while that happens, but not VS.

- Jonathan M Davis

Asynchronous loading was implemented in vs2013 (or 2012). vs2010 loads projects synchronously and freezes until it's all done.

On Wednesday, 14 October 2015 at 09:16:14 UTC, Kagamin wrote:
> Asynchronous loading was implemented in vs2013 (or 2012). vs2010 loads projects synchronously and freezes until it's all done.

That's curious. I'm using VS 2013, but the solution and most of the projects are 2010. Maybe it retains the old behavior for older solutions/projects, and that's why it's freezing.

Regardless, it does seem kind of pathetic for it to take VS a couple of minutes to load some text files into memory and get things set up (whether it's synchronous or not). I'd be very surprised if it could not be improved, though the async load that I don't seem to be getting would certainly help.

- Jonathan M Davis