I have an application (not my code) that suffers a slow start on servers that are not connected to the Internet.
From earlier experience, I know about generatePublisherEvidence in the configuration file and tried it here (after detecting some TCP connections with timeouts in the monitor process).
However, in this case, the application is .Net 4.5.1 and the generatePublisherEvidence documentation page:
In the .NET Framework 4 and later, this item does not affect assembly load time.
To my surprise, boot time was reduced and the TCP connection disappeared from the log.
At first I thought it was a coincidence, but now I checked the same behavior on other servers.
Can anyone explain this?
I tried to follow the links on the msdn page, but could not find any information on how the assembly certificates are verified and why it differs between CLR2 and CLR4.
The only thing I can come up with is that the application loads some old CLR2 assemblies and is affected by the generatePublisherEveidence function.
source
share