I’m actually quite surprised at how easy it was to upgrade Ideal BB.NET from ASP.NET 1.1 to 2.0.  It took me a few more hours today to complete the upgrade.  The biggest issue was a name space compatibility program between my IdealLogin library and the official .NET login library.  I tested out the web site briefly and most things seemed to work.  The AJAX stuff is partially broken but given that Microsoft provides a really great ASP.NET 2.0 AJAX library I’ll probably rewrite most of that stuff using those new routines.

I’ve got some customer reported bugs that I need to tackle tomorrow so I’ll focus on doing that and then get back to testing the 2.0 release.  I’m hoping to get it out the door soon so that customers can upgrade and take advantage of the new version.

I’m in the process of migrating Ideal BB.NET from .NET 1.1 to 2.0.  I don’t see any reason to keep the product in 1.1 when I could fairly easily migrate it to 2.0 and take advantage of the new Visual Studio as well as the features of .NET 2.0.

I will continue to support version 1.1 for users that cannot upgrade to 2.0 but new development (features etc..) will happen on the 2.0 product only.  I can’t see why companies wouldn’t want the 2.0 product if given a choice between the two.  (Now is the time to speak out if you have any qualms about upgrading to 2.0.)

When I get everything upgraded, I’ll release it as Ideal BB.NET 2.0.  Feature-wise, everything will remain pretty much the same.  I’ve got some new features for the 1.6 release so that will probably be the last .NET 1.1 feature release until Ideal BB.NET 2.0 is out.