Microsoft KB Archive/813833

= PRB: &quot;Access Denied&quot; Error Messages When You Do Not Put Strong-Named Assemblies in the Global Assembly Cache =

Article ID: 813833

Article Last Modified on 5/21/2007

-

APPLIES TO


 * Microsoft Web Services Enhancements for Microsoft .NET 1.1
 * Microsoft Web Services Enhancements for Microsoft .NET 2.0

-





SYMPTOMS
If you do not put strong-named assemblies (or private strong-named assemblies) in the global assembly cache, and then you use these assemblies in your ASP.NET application, Indexing Service may experience &quot;Access Denied&quot; errors for these strong-named assemblies.



CAUSE
Strong-named assemblies are loaded as domain neutral for ASP.NET applications. Because these assemblies are not unloaded until the process is unloaded, the file may remain locked. Therefore, when Indexing Service monitors the temporary ASP.NET folder and the Web root folders, you may receive &quot;Access Denied&quot; error messages for strong-named assemblies that are not in the global assembly cache.



RESOLUTION

 * Because strong-named assemblies are loaded as domain neutral for ASP.NET applications, do not put strong-named assemblies in the Bin folder of your ASP.NET application. Strong-named assemblies are only supported in the global assembly cache for ASP.NET.
 * Private strong-named assemblies (strong-named assemblies that are located in the Bin folder of an ASP.NET application) are not supported.
 * If you want to use a private assembly, do not make this assembly a strong-named assembly for ASP.NET applications.



STATUS
This behavior is by design.



MORE INFORMATION
Microsoft recommends that you do not configure Indexing Service or antivirus applications to monitor the ASP.NET temporary folder or the Web application folders, regardless of whether your ASP.NET applications use strong-named assemblies.

