Comments on: A Type-safe BackgroundWorker Wrapper http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/ Just another WordPress weblog Tue, 06 Jan 2009 22:19:23 +0000 http://wordpress.org/?v=2.6.3 By: Quantum Bit Designs » Blog Archive » DelegateMarshaler - Replace Control.InvokeRequired and Control.Invoke http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/#comment-90 Quantum Bit Designs » Blog Archive » DelegateMarshaler - Replace Control.InvokeRequired and Control.Invoke Wed, 25 Jun 2008 03:04:34 +0000 http://thevalerios.net/matt/?p=18#comment-90 [...] Linkshttp://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/ http://weblogs.asp.net/justin_rogers/articles/126345.aspx [...] [...] Linkshttp://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/ http://weblogs.asp.net/justin_rogers/articles/126345.aspx [...]

]]> By: valerio.net » Blog Archive » Multithreading and Concurrency in .NET http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/#comment-56 valerio.net » Blog Archive » Multithreading and Concurrency in .NET Sat, 14 Jun 2008 19:55:07 +0000 http://thevalerios.net/matt/?p=18#comment-56 [...] A common scenario usually encountered when creating responsive user interfaces (e.g. WinForms applications) is to let a long-running piece of code execute on a background thread and then update the user interface when it completes.  The catch is that the user interface update at the end must be completed on the UI thread.  Thankfully .NET Framework shipped with a BackgroundWorker created explicitly for this task which handles the marshalling between background thread and UI thread automatically.   It even supports cancellation and can report progress back to the UI thread in addition to notifying the UI thread that it has completed.  This is also discussed in the "Threading in C#" book mentioned above.  In addition, only slight modifications to the BackgroundWorker are needed to use anonymous types as well. [...] [...] A common scenario usually encountered when creating responsive user interfaces (e.g. WinForms applications) is to let a long-running piece of code execute on a background thread and then update the user interface when it completes.  The catch is that the user interface update at the end must be completed on the UI thread.  Thankfully .NET Framework shipped with a BackgroundWorker created explicitly for this task which handles the marshalling between background thread and UI thread automatically.   It even supports cancellation and can report progress back to the UI thread in addition to notifying the UI thread that it has completed.  This is also discussed in the "Threading in C#" book mentioned above.  In addition, only slight modifications to the BackgroundWorker are needed to use anonymous types as well. [...]

]]> By: valerio.net » Blog Archive » A Queued BackgroundWorker Using Anonymous Delegates http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/#comment-20 valerio.net » Blog Archive » A Queued BackgroundWorker Using Anonymous Delegates Tue, 20 May 2008 01:49:25 +0000 http://thevalerios.net/matt/?p=18#comment-20 [...] A Type-safe BackgroundWorker Wrapper [...] [...] A Type-safe BackgroundWorker Wrapper [...]

]]> By: valerio.net » Blog Archive » Use ThreadPool.QueueUserWorkItem With Anonymous Types http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/#comment-19 valerio.net » Blog Archive » Use ThreadPool.QueueUserWorkItem With Anonymous Types Mon, 19 May 2008 21:56:29 +0000 http://thevalerios.net/matt/?p=18#comment-19 [...] A Type-safe BackgroundWorker Wrapper [...] [...] A Type-safe BackgroundWorker Wrapper [...]

]]> By: Michael Giagnocavo http://thevalerios.net/matt/2008/05/a-type-safe-backgroundworker-wrapper/#comment-8 Michael Giagnocavo Fri, 16 May 2008 20:12:35 +0000 http://thevalerios.net/matt/?p=18#comment-8 Yes, functional programming excels at user interfaces. It's also great for showing blocking UI while perfoming actions. A lot of our UI code has stuff like this: ProgressDialog.ShowAction(pd => { // long running code pd.Close(); }); This ends up getting nested in a few layers of async stuff, dispatching, error handling and so on. But it's so much easier than the alternatives. Yes, functional programming excels at user interfaces. It’s also great for showing blocking UI while perfoming actions. A lot of our UI code has stuff like this:

ProgressDialog.ShowAction(pd => {
// long running code
pd.Close();
});

This ends up getting nested in a few layers of async stuff, dispatching, error handling and so on. But it’s so much easier than the alternatives.

]]>