Lazycoder

K. Scott Allen : The Great Migration: “The problem is, you don’t get all the new features for free. 1.x programmers need to unlearn a few concepts, and migrate their existing code. “

We’re starting to try to migrate our project, Caisis, to ASP.NET 2.0. The biz, DAL, and Controller projects migrating with no problems. A few warnings about deprecated XML transform methods. No problem. The UI, the actual ASP part of ASP.NET, can not easily be migrated. At least, not by the built in wizard. The wizard left artifacts all over the place. Moved some code to the app_code directory, then the compiler complains that it can’t find the code. Lots of problems with the .ascx files finding their respective code-behind classes. Most of those were fixed by adding a page tag, I forget which one. Oh, the reference tag.

The biggest problem with migrating from 1.0/1.1 to 2.0 is that you don’t get the benefits for free. The migration wizard doesn’t really make it any easier for you to add master pages to your project.

I think instead of migrating the project, we’d be better off re-writing the UI under 2.0. Why go through all that pain just to gut the application and start from scratch? Might as well start from plain HTML pages in the first place.