Conclusion

I l @ ve RuBoard

The subject of native and COM interop is almost overwhelming in its scope. You'll notice that I've barely touched on the topics of PInvoke and COM interop. Instead, I've attempted to cover the basics and point you down the right road. The path you choose is up to you.

As time goes on, you should have to do less and less interop with native code and COM. Microsoft is certainly making a huge commitment that all new Windows APIs will support a managed interface. As more of the Win32 API functionality makes its way into the .NET Framework classes and other managed assemblies, the less work you'll need to do to take advantage of those features.

Of course, you'll have your own legacy issues to contend with. Corporations are notorious for keeping around old code that no one has the time, expertise, or inclination to upgrade. (Sometimes the original source code no longer exists.) System integration issues will always pose challenges that will ensure a solid future for the likes of PInvoke and COM interop.

I l @ ve RuBoard


Designing Enterprise Applications with Microsoft Visual Basic .NET
Designing Enterprise Applications with Microsoft Visual Basic .NET (Pro-Developer)
ISBN: 073561721X
EAN: 2147483647
Year: 2002
Pages: 103

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