Hi there!

One of our customers experiences a big delay on the start of our
WinForms application. By adding additional tracing I identified that
there are actually two places where delay occurs.
The first delay is exactly 30 seconds. It happens after the method
Application.Run is called and before execution of the first line of
the main form's constructor. It takes another 61 seconds to execute
code in the main form's constructor. Here is the code and trace
output:

static void Main() {
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(fals e);
Logger.Write("Entering Application.Run");
Application.Run(new MainForm());
}

public MainForm() {
Logger.Write("Entered MainForm constructor");
InitializeComponent();
/* some simple property assignments were ommited for
clarity */
Logger.Write("Exited MainForm constructor");
}

11/13/2007 7:45:41 AM App: ATMManager.exe Category: Message: Entering
Application.Run}
11/13/2007 7:46:11 AM App: ATMManager.exe Category: Message: Entered
MainForm constructor}
11/13/2007 7:47:12 AM App: ATMManager.exe Category: Message: Exited
MainForm constructor}

The environment is WinXP SP2 box with dual core processor and 4Gigs of
Ram. .Net Framework version is 2.0.50727.

The following was attempted in order to resolve the problem

1) Re-installing of .Net framework 2.0 and applying all updates to
Windows itself
2) Compiling to native image using ngen.

Delays still persist. The duration of delays is consistent and is
always 30 and 61 seconds.

Any ideas?

I believe this has something to do with validating autorization on
Domain controllers.
One of the guys from SysInternals once wrote something on this topic.
Check this out: http://blogs.technet.com/markrussino...31/453100.aspx

Thanks for the hint. The delays were indeed caused by unproper network
configuration.