It seems that setting shadowCopyBinAssemblies="false" in your web.config does not have the desired effect, and the shadow copying feature is still being applied. This can happen due to several reasons, particularly in IIS and how ASP.NET manages assemblies during runtime.

Here are a few things to check or try:

IIS Application Pool Settings:

Make sure that the application pool is set to use No Managed Code if you don't need .NET runtime to load assemblies. Sometimes, even if this is set to .NET, IIS might still shadow copy assemblies for certain configurations.

Ensure that the application pool is using Integrated mode instead of Classic mode.

ShadowCopying Behavior in IIS:

Even if you set shadowCopyBinAssemblies="false" in web.config, IIS might still shadow copy assemblies for the first request to make sure that the web application loads and initializes properly.

To fully control shadow copying behavior, you might need to adjust the ASP.NET settings through the registry or through IIS settings, particularly if you're using IIS to host your application.

Test with Debugging Mode Off:

In production, debugging is often enabled (debug="true"), which may cause the shadow copying to remain enabled. Ensure you have debug="false" for production environments.

Temporary ASP.NET Files Location:

Even with shadowCopyBinAssemblies="false", ASP.NET might still cache assemblies in the Temporary ASP.NET Files directory (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files). This is normal behavior if the application needs to handle certain runtime operations or if the assemblies are not explicitly precompiled.

Check IIS and ASP.NET Configuration:

Make sure that the IIS server is properly restarted after changes in web.config. Sometimes, changes don't take effect until IIS is fully restarted, especially in production environments.

Ensure that shadowCopyBinAssemblies is correctly set within the hostingEnvironment section in web.config (as you've already done).

Deployment Considerations:

If you're deploying the application on a production server, double-check that you are indeed using the correct **web.config **file (not an older version or one that got cached during deployment).

Review Assembly Binding Log:

You can enable assembly binding logs to check if any assembly is being loaded or shadow-copied, which might help identify if something unexpected is happening.

If none of these solutions work, consider researching deeper into IIS configuration and ASP.NET runtime behavior for shadow copying, or review logs to see if there are any clues indicating why shadow copying persists despite the setting.