|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
absolute assembly search pathLet'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... You can use a <codebase> element in your configuration file, but unless the
assembly is strong-named (not a big deal), the assemblies must be located in or under the application root directory. See: http://msdn2.microsoft.com/en-us/library/2h3sywsc(vs.71).aspx -- Show quoteHTH, Kevin Spencer Chicken Salad Surgeon Microsoft MVP "T.G." <tiber***@hotmail.com> wrote in message news:bJ_Xi.165138$U01.1168318@twister1.libero.it... > 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... > |
|||||||||||||||||||||||