/highentropyva[+|-] Enable high-entropy ASLR
/optimize[+|-] Enable optimizations (Short form: /o)
Unable to load Analyzer assembly
reading Win32 resources -- {0}
reading ruleset file {0} - {1}
!Error opening response file '{0}'
%Error building Win32 resources -- {0}
%Error reading resource '{0}' -- '{1}'
)Error reading debug information for '{0}'
*Unable to load Analyzer assembly {0} : {1}
,Error opening Win32 manifest file {0} -- {1}
0An error occurred while writing the output file.
0Error opening Win32 resource file '{0}' -- '{1}'
0Error reading Win32 manifest file '{0}' -- '{1}'
1End tag '{0}' does not match the start tag '{1}'.
1There is an error in a referenced assembly '{0}'.
3Unexpected error writing debug information -- '{0}'
9Unable to include XML fragment '{1}' of file '{0}' -- {2}
Error signing output with public key from file '{0}' -- {1}
@Error signing output with public key from container '{0}' -- {1}
An assembly with the same simple name '{0}' has already been imported. Try removing one of the references (e.g. '{1}') or sign them to enable side-by-side.
BError reading file '{0}' specified for the named argument '{1}' for PermissionSet attribute: '{2}'
DUnable to resolve file path '{0}' specified for the named argument '{1}' for PermissionSet attribute
LIndexing an array with a negative index (array indices always start at zero)
NYou must specify the CLSCompliant attribute on the assembly, not the module, to enable CLS compliance checking
The compiler emits this warning when it overrides an error with a warning. For information about the problem, search for the error code mentioned.
This error occurs if you have an overloaded method that takes a jagged array and the only difference between the method signatures is the element type of the array. To avoid this error, consider using a rectangular array rather than a jagged array
use an additional parameter to disambiguate the function call
rename one or more of the overloaded methods
or, if CLS Compliance is not needed, remove the CLSCompliantAttribute attribute.
This error occurs when a predefined system type such as System.Int32 is found in two assemblies. One way this can happen is if you are referencing mscorlib or System.Runtime.dll from two different places, such as trying to run two versions of the .NET Framework side-by-side.
Unable to include XML fragment
{0}. See also error CS{1}.