+7  A: 

This doesn't work because the compiler will not insert an implicit conversion on both sides at once, and null requires an implicit conversion to become a nullable type.

Instead, you can write

task.ActualEndDate = TextBoxActualEndDate.Text != "" ? 
    DateTime.Parse(TextBoxActualEndDate.Text) : new DateTime?();

This only requires one implicit conversion (DateTime to DateTime?).

Alternatively, you can cast either left side:

task.ActualEndDate = TextBoxActualEndDate.Text != "" ? 
    (DateTime?)DateTime.Parse(TextBoxActualEndDate.Text) : null;

This also requires only one implicit conversion.

SLaks
You really should use a DateTime.TryParse(TextBoxActualEndDate.Text, out someDateVar) there. Never trust input to give you a parseable string.
Tomas
Yes, but it's not my code.
SLaks
Validation occurs in a couple places prior to this parse, and I would prefer an exception now rather than one when I attempt to insert DateTime.Min into the database.
Daniel Coffman
+3  A: 

The conditional operator doesn't look at what the value is being returned into. It only looks at the values it's being asked to choose between: a DateTime and null. It can't identify these as instances of the same type (because null isn't a valid DateTime), hence the error. You and I know that Nullable<DateTime> could do the job, but the conditional operator isn't allowed to introduce "larger" types: it's only allowed to look at the types of the two expressions it's choosing between. (Thanks to Aaronaught in comments for clarification of this point and a nice clarifying example.)

To work around this, give the operator a hint by casting the DateTime:

TextBoxActualEndDate.Text != "" ? (DateTime?)(DateTime.Parse(TextBoxActualEndDate.Text)) : null;
                                  ^^^^^^^^^^^
itowlson
Mostly correct (+1): `DateTime.Parse` returns a `DateTime` (not a `Nullable<DateTime>`), which is a value type and has no conversion to or from `null`. The compiler doesn't have the ability to introduce "larger" types into the equation when it tries to resolve the expression, it can only work with the types that are actually there. It's the same reason you can't write `Stream s = expr ? new MemoryStream() : new FileStream(...)`.
Aaronaught
Aaronaught: great explanation - I will fold that in.
itowlson
A: 

The reason is that null is of type object so you have to cast it to the correct type, like this:

task.ActualEndDate = TextBoxActualEndDate.Text != "" ? 
    DateTime.Parse(TextBoxActualEndDate.Text) : ((DateTime?) null);
Keltex
A: 

The most correct way (IMO) is to do this

task.ActualEndDate = TextBoxActualEndDate.Text != "" ? 
    (DateTime?)(DateTime.Parse(TextBoxActualEndDate.Text) : null);

I use the null collaescing operator frequently in this manner.

Chris Marisic
A: 

This is the error probably which you get in this situation:

error CS0173: Type of conditional expression cannot be determined because there is no implicit conversion between '' and 'int')

The compiler is is explaining that it does not know how convert null into a DateTime.


Fix:

you need to cast explicitly the expression which may return null to the nullable type. This will work

((DateTime?) null);
Asad Butt
+1  A: 

This is a duplicate of

http://stackoverflow.com/questions/858080/nullable-types-and-the-ternary-operator-why-wont-this-work/858557#858557

My answer to

http://stackoverflow.com/questions/2215745/conditional-operator-cannot-cast-implicitly/2215959#2215959

gives an analysis that is germane to this question.

I'll also be blogging about a similar issue with the conditional operator in April; watch the blog for details.

Eric Lippert
http://blogs.msdn.com/ericlippert/archive/2006/05/24/type-inference-woes-part-one.aspx was very informative. Thanks.
Daniel Coffman