Interoperability vs. Migration


To migrate unmanaged applications to .NET, you need to decide which parts to migrate and which parts to leave unmanaged. The COM interoperability features of .NET Framework allow you to continue using existing code without migrating it to managed code. Interoperability saves the time, cost, and effort invested while developing code for unmanaged applications.

In some cases, migration can be the better choice for applications. You need to consider factors such as performance to strike a balance between migration and interoperability.

You must account for the overhead of calling unmanaged code from managed code through COM interoperability when deciding to choose interoperability instead of migration. If the methods of the COM component perform substantial tasks, such as accessing the database, the overhead of the interoperability is negligible compared to the overall method call time. However, if the methods perform small tasks, such as setting the value of a property, the overhead of the interoperability may be a significant portion of the method call. In this case, you should choose migration over interoperability.

In addition, you can use the new features that .NET Framework provides, consider migration. For example, migrating Web applications to ASP.NET allows you to use advanced data binding, caching, security, and improved configuration and deployment features.




Migrating Unmanaged Applications to. NET
Migrating Unmanaged Applications to. NET
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 31

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