Made thread of foreach loop

Question

3.00/5 (1 vote)

See more:

I am writing an application that runs through 8chracter words(starting randomly) and stops if a word had been found that complies with the PasswordPolicy, now how do I make this multithreaded?

foreach (string word in GetWords(8))
{
  if (CheckPasswordPolicy(word))
   {
    MessageBox.Show(word);
     return;
   }
}

Greets,
Wim.

Posted 20-Jan-10 23:54pm

Wim @ Equazion

Add a Solution

2 solutions

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)

#realJSOP · Answer 1 · 2010-01-21T00:07:00

Solution 1

Look into using a BackgroundWorker object. I would give you specific code, but there are plenty of examples on the internet. Just use google to find them.

Posted 21-Jan-10 0:07am

#realJSOP

Wim @ Equazion · Answer 2 · 2010-01-21T02:13:00

How can I use let's say 10 threads and stop everything if 1 thread finds my word?

From JSOP: It would be fairly pointless to run multiple threads to search through the same list. In fact, using a thread to do this at all seems like a questionable design decision, because I assume that you're running through the list in response to the user entering a password. You probably don't want him to proceed until the password has been checked against the list, so why create all that overhead and work by putting it in a thread?