Evolving a .NET Framework 2.0 Application to .NET Framework 3.5

I reader recently forwarded me an interesting case study that covers a very common scenario: Porting a .NET Framework 2.0 based application to .NET Framework 3.5. 

The paper does a nice job of providing resources to get started with, how to learn what is new in .NET 3.5, etc.  As well as details on why this project made decisions it did around using WPF, WCF, etc. 

I don't claim to agree with all the assertions made here, but all in all it is a very balanced, pragmatic view of what some of the common choices you will have.

The project uses client and server components and the paper talks about not only the design process but how to build AND test these.  They talk about ViewModel in WPF, IoC, NUnit and VSTS, etc




Evolving a .NET 3.5 Application

Comments (8)

  1. Guru Stop says:

    Although I hate to quote that often, but, this one is totally worth it: Brad Abrams recently wrote a

  2. Thanks for the link Brad; I wholly encourage people not to agree with all the assertions in the whitepaper! Not least because not all of the decisions we made at the time are right for all (if any) projects at all times.

    I’ve put up a blog post here (http://blogs.ythos.net) to encourage debate and discussion of the issues.

  3. brad abrams says:


  4. Very useful white paper.  I am sure others can appreciate this.

  5. Dave Hybrid says:

    Great post, really helped me understand, thanks!

  6. IT Support says:

    A really well explained article and has given me a nice idea for a project!

Skip to main content