
11.11.2002
318274 - PRB: "Compiler Error Message: CS1595" Error Message When You Use the C# Compiler to Compile an ASP.NET Resource
When you get System.Collections.ArrayList' is defined in multiple places; using definition from 'c:\winnt\microsoft.net\framework\v1.0.3705\mscorlib.dll'
or CompilerGlobalScopeAttribute is defined in mulitple places
Problem - C# compiler does not have permissions to access the folders in the path to the mscorlib.dll assembly.
Fix #1 - add /nostdlib option to c# compiler options in machine.config
Fix #2 - Grant list permissions to the ASPNET account. (can also grant "list folder/read data" permissions to one of the following accounts: ASPNET, group that includes ASPNET, process identity that is being used to run ASP.NET worker process for every folder in the path to mscorlib.dll assembly
more notes:
we removed Everyone from the root of that drive, and it started to cause the above problem. After making sure that the ASPNET account had access to those directories, it still wasn't working. So until we figure out what else needs access to certain directories, we've put the Everyone account back on the root of the drive. Lame.
When you get System.Collections.ArrayList' is defined in multiple places; using definition from 'c:\winnt\microsoft.net\framework\v1.0.3705\mscorlib.dll'
or CompilerGlobalScopeAttribute is defined in mulitple places
Problem - C# compiler does not have permissions to access the folders in the path to the mscorlib.dll assembly.
Fix #1 - add /nostdlib option to c# compiler options in machine.config
Fix #2 - Grant list permissions to the ASPNET account. (can also grant "list folder/read data" permissions to one of the following accounts: ASPNET, group that includes ASPNET, process identity that is being used to run ASP.NET worker process for every folder in the path to mscorlib.dll assembly
more notes:
we removed Everyone from the root of that drive, and it started to cause the above problem. After making sure that the ASPNET account had access to those directories, it still wasn't working. So until we figure out what else needs access to certain directories, we've put the Everyone account back on the root of the drive. Lame.