Microsoft recently released Silverlight 2.0 to the public. After the Olympic games, Silverlight ended up on a LOT of people's computers, but Silverlight 2 has more importance to application developers in the future. I discuss that in this post
Recently a Microsoft developer posted a blog entry detailing a very negative experience he had with the iPhone SDK, Cocoa, and Xcode. MS developers allowing their first impression to taint their view of Mac programming is common, but easily corrected
In this blog post I show you how to create your own continuous aggregates that extend CLINQ with domain-specific functionality like VWAP (Volume Weighted Average Price).
I'm just about ready to start upgrading the demo suite to be compatible with some of the new code I'm writing for CLINQ 1.1 and thought I'd post a preview of Continuous Aggregation
This blog post contains an explanation of a demo I wrote for the initial release of CLINQ. It uses a WCF Peer Mesh to distribute messages which are then continuously filtered via CLINQ queries
A very common task in data-driven applications is to render lists of data in ledger-style with alternating row background styles/colors. Unfortunately, a lot of the samples for this are wrong and only apply to limited cases.
I first encountered the delegate design pattern when learning Cocoa, but I have found that its use has actually made some Windows Vista (WPF) programming tasks easier as well!
Microsoft's WPF/E, which is now called Silverlight, is a cross-platform, cross-browser platform for RIA (Rich Interactive Application). Question is: will anyone use it??
In a previous article I explored a comparison between VS 2005 and the Xcode/Interface Builder IDEs. In this article, I explore implementing the MVC pattern in WPF applications
This blog entry contains a summary of some of my experiences in using state machine workflows to control the flow and logic of a complex WPF application
While continuing my learning of Objective-C and Cocoa programming, I am also continuing to compare and contrast and hopefully become a better programming. Today I compare the NIB file vs the XAML file
I don't intend to declare a "winner" or say which one I like best, I merely want to compare and contrast for my own edification and to illustrate the differences (and similarities) to Cocoa newbs like me
Recently I published a blog post about the monostate pattern and how it can dramatically simplify the life of a WPF developer of real-world applications. I've actually got some issues with monostate now after some experimentation.
I've been expanding on the basic network framework for the Ulysses Agenda game and I've got a working authentication service up and running - and uses the "SOA on an ESB" pattern
Some of you may have noticed a similarity between UA's network design and ESB implementations that embrace SOA concepts. This post illustrates how the design and implementation of Ulysses Agenda is simple, yet extremely extensible. Thanks to ESB/SOA
I was recently interviewed by Mary J Foley where she asked me some questions about how Ulysses Agenda was making use of the new .NET Framework 3.0 technologies
So many of the data binding examples that I've seen have been overly simplistic, some even use the constructor of the bound object to populate the source items. This doesn't work in the real world and I've got a solution
So the other day I was thinking about how I was going to design the schema for the Ulysses Agenda game's server-side database, and then I had a revalation! I wanted pizza! But after I had that revalation, something else dawned on me!