I have to give up on converting dasBlog to .NET 2.0 for now. The ASP.NET model has
changed significantly from 1.1 to 2.0, breaking every single page in the application.
In other words, many of the techniques developers used for making pages do interesting
things in 1.1 simply don't work in 2.0, because the system doesn't work the same
way. I may have missed something simple—but I don't think so at the moment.
So I think all of the pages in the application need to be changed in order to make
it work. In fact, I think the whole application needs to change, to take advantage
of the new features in ASP.NET 2.0. I figure fixing the current pages will take
about 8-12 hours, which I can't spare until Thanksgiving. I'll just have to live
with a few annoyances for now. Redesigning the application isn't going to happen.
Tuesday I'll take a look at it in Visual Studio 2003, so I can at least see how
it works step-by-step, and possibly see if some of these annoyances will take a
lot of time to fix.
The glimmer of light in all this is that only the Web application needs to change. All of the supporting assemblies compile without any major problems. So instead of changing hundreds of classes, I think I only have to change a few dozen.