I have been using asynchronous threading to handle the button actions
on my form (the ones that need to make database calls anyways). I am
curious if anyone has found a way to make the calls more generic? Is
it possible to structure the code so that you don't have to create the
delegate, BeginAction(), EndAction(), and ActionCallback() functions
for every single action that I want to handle? Especially since the
only thing different about them is the main calling method name.

Thanks,
Slavisa

Hi, Pug

You can consider to create one delegate, which will be passed parameter
defining function to perform. Then all event handlers will call same
delegate and delegate itself will decide what do to.

HTH
Alex

"Pug Fugly" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have been using asynchronous threading to handle the button actions
> on my form (the ones that need to make database calls anyways). I am
> curious if anyone has found a way to make the calls more generic? Is
> it possible to structure the code so that you don't have to create the
> delegate, BeginAction(), EndAction(), and ActionCallback() functions
> for every single action that I want to handle? Especially since the
> only thing different about them is the main calling method name.
>
> Thanks,
> Slavisa

In article <(E-Mail Removed)>, Pug Fugly wrote:
> I have been using asynchronous threading to handle the button actions
> on my form (the ones that need to make database calls anyways). I am
> curious if anyone has found a way to make the calls more generic? Is
> it possible to structure the code so that you don't have to create the
> delegate, BeginAction(), EndAction(), and ActionCallback() functions
> for every single action that I want to handle? Especially since the
> only thing different about them is the main calling method name.
>
> Thanks,
> Slavisa

You could build a class to encapsulate this. It could take a delegate
and invoke it asyncrounously, and then notify you when done via events.
Actually, in the next version of .NET there is a BackgroundWorker
component that basically does this for you - but it wouldn't be to
difficult to write a component that would handle this for you.

--
Tom Shelton [MVP]

Slavisa,
As Tom suggested, .NET 2.0 will include the BackgroundWorker class.

The following article discusses how this class works.

http://www.mikedub.net/windowsformsr...es/000009.html

The article also has links to a series of articles on multithreading that
may or may not help.

Hope this helps
Jay

"Pug Fugly" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have been using asynchronous threading to handle the button actions
> on my form (the ones that need to make database calls anyways). I am
> curious if anyone has found a way to make the calls more generic? Is
> it possible to structure the code so that you don't have to create the
> delegate, BeginAction(), EndAction(), and ActionCallback() functions
> for every single action that I want to handle? Especially since the
> only thing different about them is the main calling method name.
>
> Thanks,
> Slavisa