.NET DLL load time is slow, causing the components to be slow to respond

When an internet connection is not available, the .NET DLL file takes a long time to load causing the components to be slow to respond.

Date Entered: 04/21/2010    Last Updated: 04/21/2010

What is likely happening is that the system is trying to contact a CRL (Certificate Revocation List) to verify the certificate used to sign our DLL. This check isn't performed by the library itself, but by the .NET Framework, when it checks the signature on the DLL that's being loaded. Unfortunately, we cannot change this in the DLL itself, but the machine administrator may be able to disable strong name verification to prevent this from occurring.

Please take a look at the following Microsoft news article that discusses it:
http://blogs.msdn.com/shawnfa/archive/2004/06/07/150378.aspx

It is also possible that Anti-Virus software may be checking the CRL.

Additionally when using the .NET Framework 3.5 or higher, you may be able to decrease load times by bypassing Authenticode verification. Details about how this is accomplished can be found on the following Microsoft news article under the "Optimize Authenticode" section:
http://msdn.microsoft.com/en-us/library/cc656914.aspx

We appreciate your feedback.  If you have any questions, comments, or suggestions about this entry please contact our support team at kb@nsoftware.com.