Geeks With Blogs



Add to Technorati Favorites

An Archived Managed World This blog has moved to

Hello all. I wanted to let you know that I wrote an article on the threading model in Avalon (more specifically, multithreaded UI development in Avalon vs WinForms). You can find it on my blog here. Or you can just view the new article category I started on the left, Longhorn Articles.

I would like to give a quick thanks to Chris Sells for being willing to edit this article and help me get it into shape. Thanks Chris!

Posted on Thursday, April 8, 2004 10:33 PM Windows Client | Back to top

Comments on this post: An Avalon Threading Story

# re: An Avalon Threading Story
Requesting Gravatar...
I'm assuming Enter/Exit are performing some context lock so that you can work with the element in question. What happens when the calls aren't matched and does C# have a method (aka using) that allows you to make sure you exit a context that you've entered?
Left by Justin Rogers on Apr 08, 2004 11:13 PM

# re: An Avalon Threading Story
Requesting Gravatar...
Yes - it's important to match any Enter() call with a corresponding Exit() call, otherwise you'll lock up your UI!

C# doesn't have any new explicit support for handling this, but it doesn't need it - you can use the existing using statement in conjunction with the UIContext.Access() method. See here for details:
Left by Ian Griffiths on Apr 09, 2004 3:25 AM

# re: An Avalon Threading Story
Requesting Gravatar...
Yeah, using Context.Access() can be a better way to go. To answer your other question Justin, I believe that if the calls aren't matched (like calling Exit without a corresponding Enter), a UIContextAccessException exception is thrown.
Left by Jason Olson on Apr 09, 2004 11:23 AM

Your comment:
 (will show your gravatar)

Copyright © Jason Olson | Powered by: