tags:

views:

21

answers:

0

I have a web application (A) developed in .NET4 which references Ingrian - a third party assembly developed in .NET2 possibly with native code. This Web application is hosted on IIS7 using .NET4 runtime.

The problem is, sometimes this assembly does not get loaded (if you recycle the application pool), until you force IIS to reload the entire web application.

If i create another web application (B) which uses .NET2 runtime in the application pool, then i don't have a problem.

Also added the following into my web.config when it is configure to run in .NET4 mode.

  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>

Then i created a small .NET4 console app, references the same assemblies with the same set of codes, it works fine.

Note: I change the Process Identity to use a more power user id and this id is use by web application A and B.

What can i do to ensure the .NET2 assembly get loaded correctly in my web application running on .NET4 mode?