Chapter 14. Visual C .NET Migration Case Study

0-13-100962-1_ch14 Chapter 14. Visual C++ .NET Migration Case Study

Snoops

   

  
Migrating to .NET: A Pragmatic Path to Visual Basic .NET, Visual C++ .NET, and ASP.NET
By Dhananjay  Katre, Prashant  Halari, Narayana  Rao  Surapaneni, Manu  Gupta, Meghana  Deshpande

Table of Contents


Chapter 14. Visual C++ .NET Migration Case Study

In the previous chapters, you learned about various aspects of migrating Visual C++ code in the .NET environment. In the course of these chapters you must have realized that some aspects such as COM interoperability need to be explained with the sample code. Now it's time to apply the knowledge that you have gained from the previous chapters in some practical scenarios. This can be best accomplished by migrating a given system developed in Visual C++ to Visual C++ .NET to see the practical implementation of the theory that you have learned so far.

To accomplish this, we have created a PMS in Visual C++ using COM components and ISAPI DLLs. The detailed functional specifications of PMS are given in Visual Basic .NET section of Chapter 12. Now we will migrate the PMS developed in Visual C++ to Visual C++ .NET. To demonstrate the interoperability of managed and unmanaged code, we have kept the front end of the PMS as it is during migration. Our focus in this migration process is to show the interoperability of COM components with .NET and to demonstrate how ISAPI can be replaced with the Web services provided by the .NET Framework. For this, we are going to use the same COM components developed in Visual C++ in the .NET Framework.

PMS uses two ISAPI DLLs, one encapsulates the functionality required for the Administrative operations and the other encapsulates Customer functionality. These DLLs provide the wrapper over the COM components. These COM components are wrapped around the database and work as the Data Access Layer for the system. The actual business logic is spread in these COM components based upon the business functionality explained in the next section. During the migration, we will keep the ISAPI DLL for the Admin module as it is but will migrate and enhance the Customer ISAPI DLL to various Web services, such as Managed C++ Web services and the ATL server to show the various aspects of Visual C++ to Visual C++ .NET migration.


Snoops

   
Top


Migrating to. NET. A Pragmatic Path to Visual Basic. NET, Visual C++. NET, and ASP. NET
Migrating to. NET. A Pragmatic Path to Visual Basic. NET, Visual C++. NET, and ASP. NET
ISBN: 131009621
EAN: N/A
Year: 2001
Pages: 149

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net