1 out of 11 rated this helpful - Rate this topic

Design Warnings

.NET Framework 2.0

Other Versions

Visual Studio 2012
Visual Studio 2010

Design warnings support adherence to the .NET Framework Design Guidelines.

In This Section

Abstract types should not have constructors
Assemblies should have valid strong names
Avoid empty interfaces
Avoid excessive parameters on generic types
Avoid namespaces with few types
Avoid out parameters
Collections should implement generic interface
Consider passing base types as parameters
Declare event handlers correctly
Declare types in namespaces
Default parameters should not be used
Define accessors for attribute arguments
Do not catch general exception types
Do not declare protected members in sealed types
Do not declare static members on generic types
Do not declare virtual members in sealed types
Do not declare visible instance fields
Do not expose generic lists
Do not hide base class methods
Do not nest generic types in member signatures
Do not overload operator equals on reference types
Do not pass types by reference
Enum Storage should be Int32
Enumerators should be strongly typed
Enums should have zero value
Generic methods should provide type parameter
ICollection implementations have strongly typed members
Implement IDisposable Correctly
Implement standard exception constructors
Indexers should not be multidimensional
Interface methods should be callable by child types
Lists are strongly typed
Mark assemblies with assembly version
Mark assemblies with CLSCompliant
Mark assemblies with ComVisible
Mark attributes with AttributeUsageAttribute
Mark enums with FlagsAttribute
Members should not expose certain concrete types
Move pinvokes to native methods class
Nested types should not be visible
Override methods on comparable types
Override operator equals on overloading add and subtract
Properties should not be write only
Provide ObsoleteAttribute message
Replace repetitive arguments with params array
Static holder types should be sealed
Static holder types should not have constructors
String uri overloads call system uri overloads
Types should not extend certain base types
Types that own disposable fields should be disposable
Types that own native resources should be disposable
Uri parameters should not be strings
Uri properties should not be strings
Uri return values should not be strings
Use events where appropriate
Use generic event handler instances
Use generics where appropriate
Use integral or string argument for indexers
Use properties where appropriate

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD