By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,312 Members | 1,254 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,312 IT Pros & Developers. It's quick & easy.

loading DLL's from single location

P: n/a
I have several programs in development that all use the same DLLS. Many of which will be the new enterprise library objects. While in development and initial launch I do not want to add these to the GAC of each machine. I want to make a single directory on each computer to hold the dlls and use a <probing> type element in the config file to find them. It appears that <probing> is only for a subfolder off the root of the current application. How can I do something similar without having to <codebase> each assembly?

my hierachy would look something like this...

root folder
application folder
application folder
DLL folder
--
--Eric Cathell, MCSA
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"ECathell" <ec******@nospam.mountaire.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
While in development and initial launch I do not want to add these to
the GAC of each machine. I want to make a single directory on each
computer to hold the dlls .. . . How can I do something similar without having to <codebase> each
assembly?


I don't believe you can. You /would/ have to codebase each assembly
separately, except in the case where one assembly, loaded from your
application, then loads another that can reside in the /same/ directory,
as in

ApplicationA, in directory dirA
loads AssemblyB, in directory B (using codebase), which then
loads AssemblyC, /also/ in directory B.

That said, you'll get performance gains putting assemblies into the
GAC; it just makes it /easier/ for the Framework to /find/ things.

Regards,
Phill W.
Nov 21 '05 #2

P: n/a
thanks for the answer Phil.

I am intending on putting it in the GAC once I am done with the major coding
parts...I was just looking for a temp quick fix, of course those are few and
far between. hehe.
--
--Eric Cathell, MCSA
"Phill. W" <P.A.Ward@o-p-e-n-.-a-c-.-u-k> wrote in message
news:d1**********@yarrow.open.ac.uk...

"ECathell" <ec******@nospam.mountaire.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
While in development and initial launch I do not want to add these to
the GAC of each machine. I want to make a single directory on each
computer to hold the dlls

. . .
How can I do something similar without having to <codebase> each
assembly?


I don't believe you can. You /would/ have to codebase each assembly
separately, except in the case where one assembly, loaded from your
application, then loads another that can reside in the /same/ directory,
as in

ApplicationA, in directory dirA
loads AssemblyB, in directory B (using codebase), which then
loads AssemblyC, /also/ in directory B.

That said, you'll get performance gains putting assemblies into the
GAC; it just makes it /easier/ for the Framework to /find/ things.

Regards,
Phill W.

Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.