The path variable (PATH)in the autoexec.bat (Win 98) or enviroment tab (NT) lists the folders to search in for an executable.
The registry entry on the other hand according to MSDN are -
'Whenever an application creates an instance of a COM component, the registry is consulted to resolve either the CLSID or ProgID of the component into the pathname of the server DLL or EXE that contains it'.
So from what I understand the registry entry should tell the client application where the DLL/EXE is present. However if the DLL/EXE is present in a folder not specified in PATH - the client application gives an error saying that it could not fine the DLL/EXE in the paths. Why does it not read the path from the registry? How does this work in DCOM? The client application cannot give the path of the DLL/EXE in its path variable?
The registry entry on the other hand according to MSDN are -
'Whenever an application creates an instance of a COM component, the registry is consulted to resolve either the CLSID or ProgID of the component into the pathname of the server DLL or EXE that contains it'.
So from what I understand the registry entry should tell the client application where the DLL/EXE is present. However if the DLL/EXE is present in a folder not specified in PATH - the client application gives an error saying that it could not fine the DLL/EXE in the paths. Why does it not read the path from the registry? How does this work in DCOM? The client application cannot give the path of the DLL/EXE in its path variable?