Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Windows Forms / WinForm General / March 2006

Tip: Looking for answers? Try searching our database.

BackgroundWorker and Business Logic Coupling

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
pearsons_11114 - 28 Mar 2006 23:48 GMT
All of the BackgroundWorker examples I've seen so far are toy in the sense
that  the worker logic is embedded in the form. Normally business logic is
decoupled from presentation. However, I can't see any direct way to implement
the business logic without out a dependency on BackgroundWorker.  It would be
fairly simple to write an adapter for whatever events are published by the
business logic component; you'd be duplicating about half the logic of
BackgroundWorker but I think it would be worth it from a safety and
consistency point of view.  But I'm wondering what the design intent is here,
since it doesn't seem to documented anywhere. Anyone using this compenent in
the real world? Thx.
Otis Mukinfus - 29 Mar 2006 13:39 GMT
>All of the BackgroundWorker examples I've seen so far are toy in the sense
>that  the worker logic is embedded in the form. Normally business logic is
[quoted text clipped - 6 lines]
>since it doesn't seem to documented anywhere. Anyone using this compenent in
>the real world? Thx.
BackgroundWorker is a component, but it doesn't have to reside on a form.  It
can also reside on a component, so if you business logic is in a component you
can just drop the background worker on the component.
Good luck with your project,

Otis Mukinfus
http://www.arltex.com
http://www.tomchilders.com
pearsons_11114 - 31 Mar 2006 00:25 GMT
> BackgroundWorker is a component, but it doesn't have to reside on a form.  It
> can also reside on a component, so if you business logic is in a component you
> can just drop the background worker on the component.
> Good luck with your project,

Right, but you still have the dependency. Not everything is an IComponent.
For example a DTS package. I think what I hear you saying is implement the
adapter by implementing IComponent. That makes perfect sense, but still
wondering what the designers had in mind as the standard approach to a fairly
standard case. Thx.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.