What are the most time consuming checks performed by .NET when executing a managed appplication?

I've developed a .NET based Windows service that uses part managed (C#) and unmanaged code (C/C++ libraries).

In some domain environments (e.g. Win 2k3 32bit server inside domain abc.com) sometimes the service takes more than 30 seconds to start (especially on OS restart), thus failing to start the service. I suspect that it has something to do with enterprise level security but I do not know for sure.

http://msdn.microsoft.com/en-us/library/aa720255%28VS.71%29.aspx

I've tried the following without success: - delay loading references by moving the using directives as far as possible from the servicebase implementation (especially the xml namespace - know to cause delays in loading) - delay loading and configuring log4net - precompiling the code by using ngen - delaying the start of the worker thread - add/remove manifest + decencies set inside - sign/unsign the binaries - use the configuration settings (there are a lot of settings and the scope level for all is set to application ) as later as possible - add all dependencies to GAC

I didn't tried yet to add security demands for the class that has the Main method implemented. I didn't tries to implement my own configuration loader because after inspecting the autogenerated code, I've noticed that the setting class is a singletone and it gets its instance on call.

By completely removing the log4net dependency it worked, but this is not an option.

When the network card is disabled the service starts immediately.

Any suggestions/comments/solution you have would be most welcomed.

I've implemented in such way as to make it work as a simple console application and used WinDbg. After looking at the windbg output I've noticed that one of the dependencies - a C++ library is loaded after the application starts, and the configuration and xml namespace do get loaded and it takes 59 seconds to load the next ones - culture..ModLoad: MyDependencyDll.dll.C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System.Xml\5913d3f81e77194ec833991b1047a532\System.Xml.ni.dll(d18.afc): CLR exception - code e0434f4d (first chance).C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\culture.dll

ltorje 2010-01-28 06:57:44

Well, use Process Monitor.

Hans Passant 2010-01-28 07:30:13

Thank you nobugz

ltorje 2010-01-29 12:15:59

After looking with procxp I've found an interested thread that uses WinHTTP - QueryDNS and another one waiting for the first one cryptography related. Note: all my binaries are digitally signed with a valid VeriSign certificate. After I've removed the DNS entry from the network connection the service worked like a charm (same if the binaries were not signed). I presume that it tries to check if the certificate is valid and even try to resolve the name from the certificate, which it can't (no internet connection). How could I prevent it from doing that?

ltorje 2010-02-03 08:31:23

@ltorje - yup, now it really yells CRL. I updated my answer to show how to turn it off.

Hans Passant 2010-02-03 11:49:10

I've forgot to mention that I've did made the steps from http://weblogs.sqlteam.com/tarad/archive/2006/10/05/13676.aspx but without any success- disable CRLI've even tried to add the certificate to the trusted publishers.Note: the certificate used to sign the code is based on a VeriSign Class 3 Code Signing 2009-2 CAhttp://www.amug.org/~glguerin/opinion/revocation.html

ltorje 2010-02-09 09:39:32

Setting crl.microsoft.com to 127.0.0.1 in hosts does not do the trick either

ltorje 2010-02-09 09:50:14

fix from Microsoft http://support.microsoft.com/default.aspx/kb/936707

ltorje 2010-02-09 10:09:26

ansaurus

tags:

views:

answers:

What are the most time consuming checks performed by .NET when executing a managed appplication?

related questions