Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This section is a reference of the error messages that are generated by the managed code analysis tool. To get help for a specific error message, type the error number in the Look for box in the Index.
In This Section
An exception was raised within managed code analysis tool that does not indicate an expected error condition. |
|
No rules were selected. |
|
No targets were selected to analyze. |
|
Rule assembly could not be loaded. |
|
A custom rule assembly has invalid XML resources. |
|
Could not load file:<path> |
|
A project file has an incorrect version of the analysis tool. |
|
Violations cannot be mapped to the current set of targets and rules. |
|
Unable to load assemblies referenced. |
|
Command line switch error. |
|
Unable to load assemblies referenced indirectly. |
|
The rule 'RuleId' could not be found. |
|
The rule 'RuleId' referenced in rule set 'RuleSetName' could not be found. |
|
Failed to load rule set file or one of its dependent rule set files. |
|
No analysis was performed because the specified rule set did not contain any FxCop rules. |
|
Unsupported metadata construct: Type 'TypeName' contains both a property and a field with the same name 'PropertyFieldName' |
|
The value 'VersionID' provided to the /targetframeworkversion is not a recognized version. |
|
Directory not found. |
|
Debug information could not be found for target assembly 'AssemblyName'. |
|
Using Alternate Platform. FrameworkVersion1 could not be found. Using FrameworkVersion2 instead. For best analysis results please ensure that the correct .NET Framework is installed. |
|
Cannot load assembly or type due to security permissions. |
|
Unable to read output report. |
|
Unsupported language. |
|
The property is deprectated. Use the superceding property |
|
Rule directory was ignored because it does not exist |
|
The property is deprectated. Use the superceding property |
|
Managed code analysis errors. |
|
Code analysis check in policy errors. |
Related Sections
Guidelines for Writing Secure Code
Analyzing Managed Code Quality by Using Code Analysis
Resources for Troubleshooting Errors in Application Lifecycle Management Tools