Use of threadpool

Question

3.00/5 (1 vote)

See more:

I am working on a .NET winform app. Once the application starts I display a splash page. While the splash page is displayed I run through a series of actions. For instance: I want to make sure they are connected to the internet, make sure they are dialed into the company VPN, make sure specific files exist on their laptop, etc. If everything is ok, I want to move to the login screen. If not, I want to go to an error screen which will describe the issues.

My question: what is the best way to handle the entire process above? I would assume that multi-threading would be a good strategy to separate the background actions from the splash ui. Maybe use a threadpool? Should I possible use a timer too... so I can trigger an error if one of the actions gets hung-up? Just looking for some best practices...

Posted 10-Dec-10 7:54am

atlquaker

Add a Solution

3 solutions

Solution 3

You can display consecutive forms, allowing each one to live as long as it's needed and then close itself. I wrote a tip/trick about it:

Multiple Subsequent "Main" Forms in C# Apps[^]

Posted 10-Dec-10 8:43am

#realJSOP

Solution 1

All of the practices you described are most recommended. Also provide status or indication in your spalsh screen that something is going on.

Posted 10-Dec-10 8:28am

HimanshuJoshi

Comments

atlquaker 10-Dec-10 14:30pm

Good idea. What is the best way to pass each status update to the splash screen?

HimanshuJoshi 10-Dec-10 14:56pm

The BackGroundWorker in Mark Nischalke's answer is best for this.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Not Active · Accepted Answer · 2010-12-10T08:30:00

Solution 2

A BackgroundWorker[^] would be the thing to use IMO

Posted 10-Dec-10 8:30am

Not Active

Comments

Dr.Walt Fair, PE 10-Dec-10 18:57pm

That's how I would do it, but JSOP's method below is a little more elegant.