Devlico.Us
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @devlicious

Christopher Bennage

Our WPF book is now available!

April 2007 - Posts

  • Silverlight: Looking Back to 1996

    Everyone is talking about the name change of WPF/E to Silverlight.  If you don't know anything about it, then you've probably have been under a rock.

    Anyway, I thought some historical reflection might prove insightful.  As we all know, Silverlight is Microsoft's answer to Flash.  The first version of Flash was released in the spring of 1996, and was originally named FutureSplash.

    If Microsoft's new product follows the same trend of shedding excess syllables, will the second release be called Slight?

  • MVC, Desktop Clients, & WPF

    I've spent the majority of my career as a Web developer, and I've only recently (with the discovery of MonoRail) really felt good about it.  I mean to say, that a true MVC framework facilitates simple and elegant Web development, whereas in the past (with classic ASP and WebForms) I always felt that something was amiss; that it was more complicated than it needed to be. Lately, I'm satisfied with Web development.

    That's great, but what about desktop applications?

    Kevin Hoffman has recently made a couple of posts about his experiences with MVC in Cocoa and the lack of built-in support for it in WPF.  Very timely for me as my company is preparing to undertake a moderately sized project utilizing WPF. Part of the elegance of a framework like MonoRail is how well it handles the stateless nature of the Web.  Windows applications are obviously different.

    There are a lot of variations on MVC.  It's sort of like a BBQ sauce, everyone has their own special recipe. I'm sure some are more fit for desktop clients than others, which leads me to my question: What are the best patterns/approaches for developing desktop applications (with WPF)?

    My priority is to "Make it correct, make it clear, make it concise, make it fast. In that order."

    Of course, that priority is facilitated by TDD/BDD, SRP, and all things ALT.NET. (Sorry, I couldn't resist building the hype.)

    I plan to experiment with WPF over the next month in this regard,but I am curious to know what other people might think.

  • An Introduction to Mocking

    Ayende has published an excellent sceencast introduction to Rhino Mocks. If you are at least somewhat familiar with Test Driven Development (TDD), then I highly recommend that you watch it. 

    Rhino Mocks is a mock object framework for TDD, and in case you don't know (I'll assume nothing), mock objects are a tool that enables you to test just one thing at time.  In other words, it helps keep the unit your unit tests.

    Additionally, Ayende is a magician with ReSharper. I learned a lot about my under-utilization of ReSharper and I was already an enthusiast!

    He does move fast and makes a couple of comments that might pass over your head if you don't know a little bit about mocking already (e.g., the explicit record and play model vs. implicit; something he talks about here.)
     

More Posts

Our Sponsors

Red-Gate!