I know that SSMS (that's based on VS shell) checks the CRL (certificate revocation list) for the signed assemblies that it uses. If it can't get to the CRL, it times out after about 30 seconds.
Could well be the same thing. In VMs that have no external access, we often turn off CRL checking. It often makes a big difference to startup times. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Stephen Price Sent: Thursday, 19 March 2015 3:07 PM To: ozDotNet Subject: Re: Visual Studio startup delay Wait, what? 2014? Did I miss a release somehow? Sent from my iPhone > On 19 Mar 2015, at 11:09 am, Greg Keogh <g...@mira.net> wrote: > > Folks, sometime in the last couple of weeks I noticed that Visual Studio 2014 > was taking a long time to start, but only when I ran it as Administrator. > Launching it as my normal user account makes it come up in a second. The last > time this happened I used procmon to discover that thousands of small HTML > files were being written due to me accidentally leaving fuslog active, but > that's not happening this time. > > This time neither procmon or Fiddler show any unusual activity of any type > around the pause. VS simply stops for exactly 30 seconds while the CPU sits > at 0% busy, then it appears as normal. This exact 30 second delay has be > stumped. Any ideas anyone? > > Greg K
