.NET 2.0 Interoperability Recipes: A Problem-Solution Approach

  • Hardcover: 632 pages
  • Publisher: Apress (March 31, 2006)
  • Language: English
  • ISBN-10: 1590596692Â

.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. The book

  • Explains new interop features in .NET 2.0 and VS .NET 2005
  • Covers PInvoke, COM, and COM+ (other books don’t cover all three areas)
  • Features most of its example code in C# and VB .NET, and also includes some managed C++/CLI
  • Is written by a working developer with first-hand experience

.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 you’ll use most often.

About the Author
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 first-hand 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 currently employed at Radiant Systems, Inc., in Alpharetta, Georgia, as a lead developer and architect in the centralized development group.