I spent a month there a year ago; the trains are the best. Anywhere my wife and I wanted to go, there were two trains an hour. We never worried about transportation on the far end; you can nearly always find a cab even in the sticks. TfL's London Transport Museum is off the beaten path, and has a fair amount of cool stuff.

Don't forget... if the one button mouse is too confusing you can always get a StupidaMouse from StupidaWorks: http://www.kissmyfloppy.com/pages/pictures.php?id= 160

Frameworks are doomed, and here's why:

You're trying to build a strategy to migrate from .NET 1.1 to .NET 2.0. In a couple of years time, MS will have introduced .NET 2.1, or .NET 3.0 or whatever, and you'll be back to square one, migrating your application into a new framework. You have to ask yourself, What business am I in? Are you in the business of delivering solutions to customer problems, or are you in the business of applying another vendor's solution to the problem they created?

All of the popular frameworks are immature. They'll be completely different in a couple of years, and if you're lucky -- I mean really lucky -- they'll incorporate some sort of backward compatibility to let you leverage your existing code base. I wouldn't count on that though.

Of course, all that being said, if your principle work product is billable hours, then by all means go with the latest and greatest framework. The customer gets some great whiz-bang that they can pay another chunk of big money to upgrade in a few years. I mean, have you tried to hire an entry-level ASP programmer lately?