Take the tour ×  Our applications use lot of custom built and
third party libraries and right now each application has a
private reference to these assemblies which means that the bin
folder of each of these applications has the referenced
assemblies copied. For e.g. Application A references
log4net.dll, CustomLibA.dll, CustomLibB.dll and Application B
also references log4net.dll, CustomLibA.dll, CustomLibB.dll and
these assemblies are stored in the following structured.
D:\Inetpub\wwwroot\ApplicationA\bin
D:\Inetpub\wwwroot\ApplicationB\bin  I have the following
questions about this arrangement:    1. I think this will create
performance issues as the number of applications and the
references grows, because, every application will load all these
assemblies which will result in virtual address fragmentation.
Is my assumption right?    2. Can I organize the applications
such that all these applications reference the assemblies from a
common folder and doesn't have a private copy in the bin folder?
For e.g. th