|
-
Nov 16th, 2007, 01:13 AM
#1
Thread Starter
Lively Member
Background Worker or New Thread?
Hi guys,
My application is making the user wait while printing documents due to the logon issues of Crystal Reports. I am not used to work with threads so I am asking you for advice. Should I use background worker or should I programmatically start a new thread? I don't know, maybe background worker starts a new thread itself. Thanks in advance!!
-
Nov 16th, 2007, 01:25 AM
#2
Re: Background Worker or New Thread?
-
Nov 16th, 2007, 01:31 AM
#3
Re: Background Worker or New Thread?
When you call the RunWorkerAsync method of a BackgroundWorker it raises its DoWork event on a thread pool thread.
-
Nov 16th, 2007, 01:35 AM
#4
Thread Starter
Lively Member
Re: Background Worker or New Thread?
-
Nov 16th, 2007, 03:24 AM
#5
Hyperactive Member
Re: Background Worker or New Thread?
Use the background worker, as that will handle all the delegates you need if you want to access the form to update some user interface items ect in the ProgressChanged event, there is also the work complete event. If you use a thread you will have to create delegates and invoke each control you want to access.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|