Chapter 23: Migration and Interoperability

Overview

Wouldn't it be great if, when a new version of a development product was released, you could forget about all your existing projects using old versions of the software? Unfortunately, for the majority of people, existing applications take up a good deal of their time and rightly so. If you restarted development with every new version of a product, then you'd never get anything finished. Organizations have a duty to their staff and shareholders, so throwing away existing investment (in both products and expertise) is not something that can be done lightly. Therefore new developments may have to work alongside and in cooperation with existing products.

This chapter is about how to manage getting .NET to work with the pre -.NET world. In particular you will look at:

• Migrating ASP applications to ASP.NET

• Changing from VBScript to their Visual Basic .NET

• Using existing COM components from .NET

• Using .NET components from COM

Despite the fact that ASP.NET is such a radical change from ASP, there's an excellent migration path , as well as great support for working alongside existing applications.

Note

Migration from ASP.NET 1.0 to 1.1 is covered in Appendix C.