Migrating to .NET
NewArchitect | at | by Mike
Microsoft's .Net initiative is widely regarded as the "next big thing" for distributed application development. The promise for Web development is clear: faster development, less custom coding, and increased stability. But what is required to migrate current applications to the new platform? Is your application ".Net-ready"?
To get your first indication of how easy your application will be to upgrade, start by doing a design inventory. For example, unstructured or truncated documentation is an obvious sign of an ad hoc development process and a low-quality application. Other indications of poor maintenance include unused and outdated source files, text files and SQL scripts; commented-out (dead) code; poor inline documentation; and inconsistent comment blocks.