How to find out why a .NET service is taking a long time to start?

A

AG152014-12-15 16:23:23

.NET

AG15, 2014-12-15 16:23:23

How can I investigate the startup process of a .NET service on Windows? Is there any way to see which internal service calls (.net app) took a long time? What tool to use for this?
The problem occurs only if the services are in Automatic (not Delayed Automatic) mode and when the system boots
Thanks in advance

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

M

mayorovp, 2014-12-15
@mayorovp

The 2012 studio has a built-in profiler hiding in the ANALYZE menu. From third-party - you can use dotTrace.
In any case, it's best to first rewrite the service so that it can run as a console process. If you also add the log output to the console, then many things can be seen visually.

A

AigizK, 2014-12-16
@AigizK

Write logs to the event log and find where the plug is