Product Manager
Intent
Provide a framework to which to migrate unmanaged code. Help isolate clients from semantically different technologies. Control “unmanaged” code in a more managed fashion.
Problem
When building a business services framework in .NET, unless you are lucky, you will have to support some form of legacy services (e.g., DLLs, COM components, or any unmanaged code). It is strange having to refer to existing COM components as legacy. This is especially true because COM+ is still used with .NET. However, when dealing with unmanaged pieces of code, more care should be given. Whether it is an existing framework that you are migrating from or some other third-party application that you must integrate, this issue will be there. The trick ...
Get .NET Patterns: Architecture, Design, and Process now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
