You may not know what is meant by the term moniker, so let's take a quick look at what a moniker entails. Basically, a moniker is the name of an instantiated component. In most cases, a component that can be called through a moniker is persistent. It is explicitly stated that the component is instantiated, which implies that each instantiation of the same component has its own unique moniker. The moniker is an indirect way of calling the component, since there is a process that needs to bind the actual component instance based on the moniker. The advantage is that you do not need to know what kind of class type the component is; this is handled by the binding process. There are different types of monikers; for example, file and URL. Another advantage of a moniker is that the component does not has to be on the local machine, as is mandatory with calling registered components.
A little further on you will see an example of a moniker, and in Figure 7.25 you see that the moniker of a Windows Script component is the path and filename of the script.
Was this article helpful?