So I did it.  I went out and bought an iPad a week ago after playing around with one at a local Apple store.  The guy at the Apple store didn’t help my decision with his “stuffy” attitude but I’m going to give him the benefit of the doubt since there were a ton of people trying to get his attention that day.

I’m a big fan of LINQ and use it wherever I can to minimize code and make applications easier to maintain overall. I was going through a code file today refactoring it based on suggestions provided by Resharper and came across the following method:

Microsoft’s been hard at work on a new distributed data framework now called WCF RIA Services.  I recently finished up a new article for Dr. Dobbs and Information Week that provides an overview of WCF RIA Services including the following topics:

UPDATE: Thanks to everyone who voted! It looks like I'll be presenting on Syncing Audio, Video and Animations in Silverlight Applications at MIX10.

The subject of Dependency Injection (DI) and Inversion of Control (IoC) containers has received a lot of attention over the last few years.  Building applications that are loosely coupled has become more and more popular (and for good reason) especially in applications that have a lot of dependencies that could break over time or need to handle the addition of new modules seamlessly.  From a personal standpoint I fall somewhere in the middle of the overall DI argument.  I definitely feel that DI has its place and personally use the general pattern in applications but also feel that some use DI in ways that seem to make applications overly complex and more difficult to maintain in the future.   My opinion on the subject really doesn’t matter here though since this post is about using an IoC container framework in Silverlight applications.