If the text of this article is true:
then every time our .NET applications are started up by an end user, Microsoft Windows does a "Phone Home" to check if we are trusted code publishers or not ? Firstly I find this outrageous from a privacy point of view, and secondly, its slowing down our code at startup...
I first found this blog a while back when Sql server Management Studio was slow to start up, and sure enough applying the Internet Explorer options change speeded up the startup time considerably.
I was just testing my rather large and complex ASP.NET + VB.NET application on two servers, one a VM and one not, and found that the application was considerably slower at startup than my development machine. Now I just applied the same "Check publisher's certificate revocation" change to these machines and the application does seem considerably faster.
So, does anyone have a deeper understanding of this "phone home" - does it always happen ?? , and is there a way to stop it happening for a particular application without changing the "Check publisher's certificate revocation" flag in IE7 which obviously affects the whole computer.