In this paper, I’m going to outline some of the thought processes, decisions and issues we had to face when
evolving a Microsoft .NET application from 1.x/2.x to 3.x. I’ll look at how we helped our client to adopt the new
technology, and yet still maintained a release schedule acceptable to the business.
I will avoid details of the proprietary aspects of the system, and I’m not providing any source code for the
components we’ve built. On the other hand, I will cover in some depth the general architecture and design of
the system, particularly as it relates to .NET3.x. As a bonus, there are quite a few code snippets and tips we
picked up along the way.
I encourage comment, disagreement and debate on our blog.
Download
whitepaper