Share on Twitter

Although I hate to quote that often, but, this one is totally worth it:

Brad Abrams recently wrote a reference to this great "Evolving a .NET 3.5 Application" white paper, about the common scenario of migrating a .NEt 2.0 project to .NET 3.5.

The white paper is available in PDF format here (direct link).

About which I quote Brad’s words:

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

Enjoy!

 

Yeah, Enjoy :).

Share on Twitter

Related posts:

  1. [Link List]Microsoft Application Architecture Guide, 2nd Edition is now complete (Ebook, Print)
    . Microsoft has released a final version of its book...
  2. Link List 20080617
    ยท Everything You Wanted To Know About MVC and MVP...
  3. [Link List] jQuery, Agile, WCF REST, WF, OpenXML, Live Messenger Anniversary, Wallpapers
    Yet another internal .NET Team email in my current company,...
, , ,
Trackback

no comment untill now

Sorry, comments closed.