tag:blogger.com,1999:blog-6822536077160579260.post7545324032090200183..comments2023-06-05T14:25:52.227+01:00Comments on Sound Code: Don't Repeat Your Threading CodeAnonymoushttp://www.blogger.com/profile/17900587357903273800noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6822536077160579260.post-85979720485514107492008-10-06T18:23:00.000+01:002008-10-06T18:23:00.000+01:00That is somewhat of a limitation, but it does work...That is somewhat of a limitation, but it does work as a base class and I've used it that way before. It's pretty clean like that. I'm all for isolating code too and was pretty pleased by the results.Arian Khttps://www.blogger.com/profile/05229597156082993185noreply@blogger.comtag:blogger.com,1999:blog-6822536077160579260.post-34055115815170541582008-10-06T18:21:00.000+01:002008-10-06T18:21:00.000+01:00Hi arian, I guess I dismissed the BackgroundWorker...Hi arian, I guess I dismissed the BackgroundWorker quite quickly because it seems to encourage putting all the code right there in the code behind of the GUI. I want to separate out the concerns - the GUI, the threading code, and the actual work to be done. But I did just have a fresh look in MSDN at the BackgroundWorker code and you are right, it is quite full featured. I guess it might give the separation I want if I can use it as a base class.Anonymoushttps://www.blogger.com/profile/17900587357903273800noreply@blogger.comtag:blogger.com,1999:blog-6822536077160579260.post-45656117176415883252008-10-06T18:12:00.000+01:002008-10-06T18:12:00.000+01:00This is some good looking code, but I'm wondering ...This is some good looking code, but I'm wondering why you didn't go with the BackgroundWorker class? This seems to encompass what you need, and even supports progress notifications. Nice work either way though!Arian Khttps://www.blogger.com/profile/05229597156082993185noreply@blogger.com