Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to stop ASP.NET from loading all assemblies from bin on first load

Tags:

asp.net

A native DotNet application will load all referenced assemblies (and their references) on first use. However, an ASP.NET will load all referenced assemblies (and their references) on first access.

  1. Is this understanding correct?

  2. Is there a way to force ASP.NET to load assemblies on demand (like local applications)?

  3. The specific scenario I am trying to resolve is:

    • The bin folder contains 2 files : A.dll and B.dll.
    • A.dll references B.dll.
    • B.dll references C.dll which is somewhere else on the system. In this case, C.dll is missing.
    • A.dll is loaded (using reflection) by the main application.
    • The error encountered (Could not load file or assembly...) relates to a missing dependency of B.dll.
    • We want the application to function as normal if C.dll is missing as this is an optional component of the main application.
    • We have no control over the contents of B.dll or C.dll.
like image 811
Iain Avatar asked Feb 03 '09 17:02

Iain


1 Answers

To answer point 3, the setting that causes all the assemblies in the bin folder to be loaded on first access can be found in the file C:\winnt\Microsoft.NET\Framework\v2.0.50727\CONFIG\web.config (depending on your environment). Cut-down extract from that file:

<system.web>
    <compilation>
        <assemblies>
            <add assembly="*" />
        </assemblies>
    </compilation>
</system.web>

All assemblies that match the wildcard are loaded as part of the initial compilation.

By modifying the web.config for the application (NOT the global DotNet one) to include the web service assembly and exclude the wildcard match, it appears that the application can function if the optional dependencies are missing:

<system.web>
    <compilation>
        <assemblies>
            <remove assembly="*" />
            <add assembly="Main.Application.WebService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=YOURKEYHERE" />
        </assemblies>
    </compilation>
</system.web>

We're still experimenting with this so not sure if this completely resolves the issue or has any unusual side-effects.

like image 135
Iain Avatar answered Oct 06 '22 06:10

Iain