One of the major (that should be MAJOR) differences in the .NET Framework is that your .NET application assembly is built using a specific version of ADOc DLLs (msado15.dll) and all of the other COM DLLs and components its references. In fact, these DLLs can be (should be?) copied from their common location to the assembly’s disk directory. This means you could have the ADO run-time DLLs installed any number of times on your disk—n copies of the same ADO DLLs or n different versions of the ADO DLLs. When you start a .NET application, the DLLs used and referenced at design/ test/debug/compile time are referenced at run time. This means your application behaves (or misbehaves) the same way it did when you wrote and tested it. Imagine that. If the version of ADO (or any other dependent DLL) gets updated (or deprecated) later, or you deploy to a system with different DLLs, your existing applications still install and load the “right” (older, newer, or the same) version of ADO and your other DLLs. This means that “DLL hell” as we know it has become a specter of the past—at least when all of your applications are based on .NET. I expect DLL hell applications will still be haunting us for decades to come—rattling their chains in the back corridors of our systems and playing evil tricks on unsuspecting tourists. I walk you through converting and accessing ADOc objects in the next chapter.

» Free PDF eBooks Download
» Tutorial Programming Visual Basic