CODEWITHSUNDEEP
c#backgroundworkerstartup
funerr
funerr

Reputation: 8156

What makes my program work with a delay on windows startup?

My program starts with windows startup,
But a background worker is supposed to work instantly after the program is opened.
But it starts with a delay and then even returns false signs(it returns if a site is up),
Only after about 15 seconds the background-worker continues to work normally and the program too. I think this is because of .net framework trying to load, or internet connection that is not up yet, or something that didn't load yet(windows startup).
What can solve this, and what is the probable cause? (WinForm C#)

Edit:
Here is something I thought of,
I don't think though that this is a good practice. Is there a better way?
(Load method): 

    while (!netConnection())
    {
    }
    if(netConnection())
    bwCheck.RunWorkerAsync();

Upvotes: 2

Views: 440

Answers (2)

Adam Tuliper
Adam Tuliper

Reputation: 30152

It is absolutely because of everything still starting up. Services can still be coming online long after you log in, the quick login dialog you see was an optimization in windows to let you log in while everything else still starts up.

Take note of How to detect working internet connection in C#? specifically a technique that avoids the loopback adapter:

System.Net.NetworkInformation.NetworkInterface.GetIsNetworkAvailable()

Upvotes: 0

Ed Swangren
Ed Swangren

Reputation: 124642

I think this is because of .net framework trying to load

Nope. If that were the case your program wouldn't run.

or internet connection that is not up yet, or

Yup. The network card/interface/connection/whatever is not initialized and connected to the internet yet. You can't expect a PC to be connected to the internet immediately at startup. Even more, what if your customer is on a domain using network authentication? What if they delay network communications until some task is complete (this was actually the problem in my case below. Seriously.)

It may take even longer to get it up and running in that case (read: don't add a Thread.Sleep() in a vain attempt to 'fix' the issue.

I had to fix a problem like this once in a systems design where we communicated to a motion control board via the ethernet bus in a PC. I ended up adding some code to monitor the status of the network connection and, only when it was established, started talking to the device via the network card.

EDIT: As SLaks pointed out in the comments, this is pretty simple in C#: The NetworkAvailabilityChanged event for your programming pleasure.

Upvotes: 5

Related Questions