T
T.G.
Let's say I have a (dotnet) application based on a main .exe file
referencing and using a number of other dotnet dlls. Normally these dlls
would live in the application directory or in some other subdirectory
relative to it. Is it possibile to specify in the application configuration
file or somewhere else an absolute path to the location of the dlls, a path
OUTSIDE the application directories. All the dlls are weakly named, and I
wouldn't want to register them in the GAC. The reason I want to this is to
centralize the deployment of the dlls on a sigle server running multiple
copies of the application from multiple application directories, using
different configuration files...
referencing and using a number of other dotnet dlls. Normally these dlls
would live in the application directory or in some other subdirectory
relative to it. Is it possibile to specify in the application configuration
file or somewhere else an absolute path to the location of the dlls, a path
OUTSIDE the application directories. All the dlls are weakly named, and I
wouldn't want to register them in the GAC. The reason I want to this is to
centralize the deployment of the dlls on a sigle server running multiple
copies of the application from multiple application directories, using
different configuration files...