I saw a post at the winfx.avalon newsgroup about the lack of support for a BackgroundWorker in Avalon (at least for v1.0). Since I need something like this for calling the Web Services asynchronously and then updating the Graphical User Interface, I just created a very simple one.
Just pointing to a couple of great posts, compatible with and adding lots more to the views I expressed in the “Loose-coupling through the relaxation of endpoint assumptions” and “Comparing S-O and O-O as design principles and not as implementation technologies” posts:
made some very interesting comments on my “Loose-coupling through the relaxation of endpoint assumptions” post. Before going into the specifics of Michi‘s comments, please allow me to emphasize that nothing from what I have been arguing is about CORBA or DCOM or any other distributed objects
Michi Henning had some comments on my “Loose-coupling through the relaxation of endpoint assumptions” entry but pblog had trouble accepting them due to an ASP.NET safeguard (not accepting XML elements in a textbox from HTTP POST). I will fix this and will also allow formatting for comments so that…
In a meeting yesterday here in Newcastle, few of us (Santosh Shrivastava, Paul Watson, Mark Little, Stuart Wheater, Simon Woodman, and I) got together to discuss/understand the differences (if any) and similarities between service-orientation and object-orientation. You may notice that some of the people involved are…
And here’s the reason I wanted to have support for posting pictures on my blog… I wanted to brag about my first Avalon 3D application (completely written in XAML).
As I mentioned before, I want to move the 3D visualisation of the White Dwarfs application to Avalon. So, I…