Article ID: 813833 - View products that this article applies to.
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 "Access Denied" errors for these strong-named assemblies.
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 "Access Denied" error messages for strong-named assemblies that are not in the global assembly cache.
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.
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/302340/EN-US/ )HOW TO: Create an Assembly with a Strong Name in .NET Framework SDK
(http://support.microsoft.com/kb/815808/ )HOW TO: Install an Assembly into the Global Assembly Cache in Visual C# .NET
820983For more information about the global assembly cache, visit the following Microsoft Web sites:
(http://support.microsoft.com/kb/820983/ )HOW TO: Use an ASP.NET Application to Query an Indexing Service Catalog by Using Visual C# .NET
Installing an Assembly into the Global Assembly Cache
Global Assembly Cache
Global Assembly Cache Tool (Gacutil.exe)
Article ID: 813833 - Last Review: May 21, 2007 - Revision: 4.4
Contact us for more help
Connect with Answer Desk for expert help.