This project has moved. For the latest updates, please go here.

This project has been moved to GitHub.
For the latest documentation please follow this link:
https://github.com/realvizu/NsDepCop


 Diagnostics Reference

NSDEPCOP01

Title Illegal namespace reference.
Severity Warning (default, determined by CodeIssueKind attribute in the config file)
Explanation The designated symbol in the source code implies a namespace reference which is not allowed by the current namespace dependency configuration. That is, the symbol is used in a type in namespace A and references a type in namespace B but A->B dependency is not allowed.
To do Change the namespace dependency configuration (in config.nsdepcop file) or change your code/design to avoid this namespace reference.

NSDEPCOP02

Title Too many issues, analysis was stopped.
Severity Warning
Explanation The analysis stops after reporting 100 issues to avoid flooding your build log.
To do Correct the reported issues and run the build again.
Comment This diagnostic works at build time only (not in Visual Studio code editor).

NSDEPCOP03

Title No config file found, analysis skipped.
Severity Info
Explanation If there's no config.nsdepcop file next to the csproj file then NsDepCop does not perform analysis.
To do None, this is just an informational message.
Comment This diagnostic works at build time only (not in Visual Studio code editor).

NSDEPCOP04

Title Analysis is disabled in the nsdepcop config file.
Severity Info
Explanation There is a config.nsdepcop file next to the csproj file, but it contains IsEnabled="False".
To do None, this is just an informational message.
Comment This diagnostic works at build time only (not in Visual Studio code editor).

NSDEPCOP05

Title Error loading NsDepCop config.
Severity Error
Explanation There was an error while loading the config.nsdepcop file. Some possible reasons: malformed content, file permission or locking problem. The diagnostic contains the actual exception message.
To do Make sure that the file can be read by the user running the build or Visual Studio and make sure that its content is correct.

Last edited Mar 26 at 11:12 AM by vizu, version 13

Comments

No comments yet.