.NET 2.0 Interoperability Recipes

1. Front Matter

   Pages i-xix

   PDF

2. Using C-Style APIs

   Pages 1-86

3. C-Style APIs: Structures, Classes, and Arrays

   Pages 87-140

4. Win32 API

   Pages 141-189

5. Using C++ Interop

   Pages 191-233

6. Using COM

   Pages 235-326

7. Exposing Managed Code to COM

   Pages 327-378

8. Marshaling to COM Clients

   Pages 379-440

9. COM+ Enterprise Services

   Pages 441-502

10. COM+ Enterprise Services Transactions

    Pages 503-582

11. Back Matter

    Pages 583-608

    PDF

.NET represents a new and improved way of developing software for the Windows platform. Given the chance, you'd probably rewrite all of your existing code in the newer managed code environment that .NET provides. But it is difficult or impossible to throw out all existing legacy code and start over when a new technology arrives. Instead, you need to find a way to move forward with new .NET development while reusing existing pieces of tested, working code. You need a way to interoperate with the existing code until you have a chance to finally rewrite all of it in .NET.

The only recipe-style book on the subject, .NET 2.0 Interoperability Recipes: A Problem-Solution Approach guides Windows developers who are transitioning from native Windows code to .NET managed code.

.NET tools will allow you to interoperate with existing code. But finding the appropriate tool for the task at hand can sometimes be a frustrating experience. So this book will guide you past myriad infrequently used interop options to focus on those youll use most often.

• .NET
• C++ programming language
• Windows
• development
• software

Bruce Bukovics has been a working developer for over 25 years. During this time, he has designed and developed applications in such widely varying areas as banking, corporate finance, credit card processing, payroll processing, and retail automation. He has firsthand developer experience with C, C++, Delphi, VB, C#, and Java, and he rode the waves of technology as they drifted from mainframe to client/server to n-Tier, from COM to COM+, and from Web Services to .NET Remoting and beyond. He considers himself a pragmatic programmer. He doesn't stand on formality and doesn't do things just because they have always been done that way. He's willing to look at alternate or unorthodox solutions to a problem if that's what it takes. He is employed at Radiant Systems, Inc., in Alpharetta, Georgia, as a lead developer and architect in the centralized development group.

Policies and ethics