Compiler Value Type Resolution and Hardcoded “0” Integer Values

Question

First, a bit of background. Read the question and accepted answer posted here for a specific scenario for my question. I\'m not sure if other, similar cases exist but this

Answer 1

This is caused by the fact that the integer literal 0 has an implicit conversion to any enum type. The C# specification states:

6.1.3 Implicit enumeration conversions

An implicit enumeration conversion permits the decimal-integer-literal 0 to be converted to any enum-type and to any nullable-type whose underlying type is an enum-type. In the latter case the conversion is evaluated by converting to the underlying enum-type and wrapping the result.

As a result, the most specific overload in this case is SqlParameter(string, DbType).

This does not apply for other int values, so the SqlParameter(string, object) constructor is the most specific.