Do signed assemblies/dlls require net connection for validation at startup
My company provides Windows based software products to clients in the form of DLLs and exes (both managed/.NET and unmanaged). Some of our clients run our products on machines that have no internet/network connection in isolated environments. We're wondering if we should sign (i.e., using Symantec Code Signing) our exes/dlls as we've seen posts of long dll load times as validation occurs at startup that requires internet connection? Is this a concern?
1) Does a signed DLL/EXE attempt to validate its signing/certificate at startup to the point that a network/internet connection is required or optimal?
2) Do things work differently for the above based on whether managed or unmanaged DLLs?
3) Does the Generatepublishevidence property setting influence the above?