H COM Integration H.1 Introduction Initially, applications created (Michigan web site)
H COM Integration H.1 Introduction Initially, applications created for Windows or DOS were designed as single monolithic executables i.e., complete applications packaged as single executable files. However, as software became more complex, developers began to experience difficulties constructing all the necessary components of an application. Furthermore, as the size of applications increased, it became impractical to redistribute an entire application to accommodate each application upgrade or bug fix. To address these problems, Microsoft incorporated shared libraries into Windows, enabling developers to reuse and modularize code. A shared library, or dynamic link library (DLL) in Windows, is a file that contains compiled code that an application loads at execution time. The fact that these libraries are loaded at runtime allows developers to modify specific libraries and test the results without rebuilding an entire application. Multiple applications can use a single shared library, which reduces the overall memory requirements for running those applications. The partitioning of programs into small pieces also makes it easier to distribute application upgrades, because only the modified DLLs must be redistributed. The introduction of shared libraries solved many problems that previously had restricted modularity and code reusability. However, the libraries also raised new concerns. Monolithic applications rarely created version conflicts if an application vendor fixed a bug in one piece of software, it was unlikely that the upgrade would affect any other software on the system. With the establishment of system-wide shared libraries, a vendor s upgrade or modification of a library could break software that used an older version of that library. Often, developers packaged DLLs with their applications to ensure software compatibility. However, the packaged DLLs could overwrite preexisting libraries on users systems, possibly affecting previously installed software. Problems introduced by shared libraries were so difficult to locate and fix that their effects became known as DLL hell. Microsoft developed the Component Object Model (COM) in an attempt to expand DLL functionality and correct DLL problems. COM is a specification that controls library versions
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.