Wait, what? 2014?
Did I miss a release somehow?
Oops! Calm down folks, it was a Freudian slip, actually 2013 - *GK*
P.S. I have VS2014 running in a VM and I fiddled with it a few weeks ago
and I can't remember what I noticed that might have been interesting at the
time.
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.
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
That sounds like a network delay, due to attempting to access, say, a
shared drive that is not actually available.
--
Regards,
Mark Hurd, B.Sc.(Ma.)(Hons.)
On 19 March 2015 at 13:39, Greg Keogh g...@mira.net wrote:
Folks, sometime in the last couple of weeks I noticed that Visual Studio
2014
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.
