1 out of 1 rated this helpful - Rate this topic

Security Warnings

.NET Framework 2.0

Visual Studio 2012
Visual Studio 2010
Visual Studio 2008

Security warnings support safer libraries and applications. These warnings help prevent security flaws in your program. If you disable any of these warnings, you should clearly mark the reason in code and also inform the designated security officer for your development project.

In This Section

Aptca methods should only call aptca methods
Aptca types should only extend aptca base types
Array fields should not be read only
Call GC.KeepAlive when using native resources
Catch non-CLSCompliant exceptions in general handlers
Do not declare read only mutable reference types
Do not indirectly expose methods with link demands
Method security should be a superset of type
Override link demands should be identical to base
Pointers should not be visible
Review declarative security on value types
Review deny and permit only usage
Review imperative security
Review sql queries for security vulnerabilities
Review suppress unmanaged code security usage
Review visible event handlers
Seal methods that satisfy private interfaces
Secure asserts
Secure GetObjectData overrides
Secure serialization constructors
Secured types should not expose fields
Security transparent assemblies should not contain security critical code
Security transparent code should not assert
Security transparent methods should not call non-public members
Specify marshaling for pinvoke string arguments
Static constructors should be private
Type link demands require inheritance demands
Wrap vulnerable finally clauses in outer try

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD