Summary
Summary In this chapter, I compared .NET and COM using the analogy of a software bus. I compared their solutions to the software bus problems of naming, life cycle management, programming language independence, location transparency, extensibility, and versioning. You have seen that, although .NET and COM use very different approaches, they are solving many of the same problems. At their essence, both COM and .NET are about creating binary, programming language-independent software components that can be easily used across process and machine boundaries. .NET has more of an Internet focus whereas COM was designed more for LANs, but many of the technical problems in both environments are the same. Much of the knowledge that you have of COM will simply map to .NET. For instance, COM uses GUIDs for naming, and .NET uses cryptographic keys. However, the problem is the same: creating a unique name for a software component. Hopefully, this chapter has also allowed you to begin mapping the knowledge that you have of COM to .NET. In the next chapter, I take a closer look at a piece of technology in the .NET Framework that does not have an analogy in COM: the CLR.  |
| | |
Team-Fly  |
| Top |
EAN: 2147483647
Pages: 119