Exception classes should be declared as public
Custom exception classes offer finer details than standard exceptions, but catching code must have access to the exception class to use them.
How to fix
Declare custom exception classes public, catchable in every context.
CQLinq source
This rule is written in CQLinq, C# LINQ over the NDepend code model. It ships with every new NDepend project: you can read it, adapt it, or use it as a starting point for your own custom rules.
// <Name>Exception classes should be declared as public</Name>
// <Id>ND1810:ExceptionClassesShouldBeDeclaredAsPublic</Id>
warnif count > 0
from t in JustMyCode.Types
where t.IsExceptionClass &&
!t.IsNested &&
!t.IsPublic
select new {
t,
Debt = 2.ToMinutes().ToDebt(),
Severity = Severity.Medium
}
//<Expl>
// The exception {0} should be declared as public.
//</Expl>
//<Desc>
// Custom exception classes offer finer details than standard exceptions,
// but catching code must have access to the exception class to use them.
//</Desc>
//<HowToFix>
// Declare custom exception classes public, catchable in every context.
//</HowToFix>
Open in the interactive Rules Explorer · All default rules
Visibility: all 12 items
- Methods that could have a lower visibility ND1800
- Types that could have a lower visibility ND1801
- Fields that could have a lower visibility ND1802
- Types that could be declared as private, nested in a parent type ND1803
- Avoid publicly visible constant fields ND1804
- Fields should be declared as private or protected ND1805
- Constructors of abstract classes should be declared as protected or private ND1806
- Avoid public methods not publicly visible ND1807
- Event handler methods should be declared as private or protected ND1808
- Wrong usage of CannotDecreaseVisibilityAttribute ND1809
- Exception classes should be declared as public ND1810
- Methods that should be declared as 'public' in C#, 'Public' in VB.NET