Mike Temporale
12-17-2004, 03:00 PM
<div class='os_post_top_link'><a href='http://msdn.microsoft.com/library/?url=/library/en-us/dntake/html/yctiwy_multithreadingandui.asp' target='_blank'>http://msdn.microsoft.com/library/?url=/library/en-us/dntake/html/yctiwy_multithreadingandui.asp</a><br /><br /></div><i>"Those of you who work on both the .NET Compact Framework and the .NET Framework are well aware that despite the tremendous commonality between the two, because of processing power or size reasons, some features are omitted. Although most of these areas aren't problematic, a few are significant enough to create a challenge. In the conversations I've had with enterprise developers at the conferences, it seems that when developers who use the .NET Framework move to the .NET Compact Framework, they commonly encounter problems in two areas. The first problem is interacting with the user interface (UI) from background threads. The other problem is managing sophisticated deployments, especially those involving the Global Assembly Cache and version forwarding. Both problems are very important and somewhat involved, so I'm going to spread the discussion over two editions of this column. This month's column will focus on overcoming the limitations of the .NET Compact Framework when you interact with the UI from background threads. Next month's column will be dedicated to deployment, the Global Assembly Cache, and version forwarding."</i><br /><br />Jim Wilson has written a really good article on how to correctly implement multitasking while interacting with the User Interface (UI) of your application. His article is well worth the read for all you developers out there that would like to implement multitasking and increase the responsiveness of your application.