Thursday, November 29, 2007

Ten Tips for a Happy Upgrade to Visual Studio 2008 (Release)


The blog post, Ten Tips for a Happy Upgrade to Visual Studio 2008 (Release) from Jon Galloway has some great recommendations and suggestions for upgrading from Beta 2 of VS 2008 to the Release version. If you are getting ready to make that jump, check this out to make sure it goes as smoothly as possible.

Tuesday, November 27, 2007

Patterns: MVC, MVP & PAC - Explained


Our group is currently looking at MVP and MVC as we move our application towards an object model design and this article is a great read on the differences between the patterns. I have found it is difficult to understand (and explain) the differences between the patterns, but this post, Ctrl-Shift-B: Interactive Application Architecture Patterns does a great job of explaining all of that! I highly recommend reading this article.

Tuesday, November 20, 2007

Visual Studio 2008 and .NET 3.5 Released - ScottGu's Blog

Please see the post below from Scott Guthrie for details about the release of Visual Studio 2008 and the .NET 3.5 Framework. Please note that if you are doing any Silverlight 1.1 development or using the Web Deployment Project add in, you will need to stick with the Beta 2 bits until these two components have been  updated for use with the release version of VS2008.

Visual Studio 2008 and .NET 3.5 Released

Thursday, November 15, 2007

Minesweeper with Silverlight 1.1

The Minesweeper Game Done in Silverlight 1.1 is a very cool example by some of the folks over at Telerik that displays some of the power and flexibility of Silverlight 1.1. They have been gracious enough to make the source code for this app available as well. Go check it out!

Writing Testable Code Is About Managing Complexity


Writing Testable Code Is About Managing Complexity is a recent blog post by Phil Haack. He provides some good insight into the benefits of writing testable code. My group is getting ready to kick off a project using Agile practices and writing testable code is going to be key to our success, so this was very timely information for me. Phil summarizes with the results (or side effects) below. Please check out his article for more details.

  1. A nice suite of regression tests.
  2. Well separated code that helps manage complexity.
  3. Well separated code that helps enable concurrent development.