Question

If I have a dynamic parameter the compiler seems to ditch the return type and think it’s dynamic.

For example:

public MethodResult IsValid(object userLogin)
{     
  return new MethodResult();
}

You would think that:

var isValidResult = IsValid(someObject());

Should read as

dynamic -> MethodResult 

But it thinks that it is:

dynamic -> dynamic

Does adding a dynamic parameter to the signature completely stop the compiler from knowing what the return should be despite the return being strongly typed?

Answer 1

Yes, dynamic stops the compiler from knowing the type on any parameters, properties, or method return types. Add an explicit cast like:

(MethodResult)IsValid(someObject));

The reason here is that once you enter the dynamic world in C# you are going into late binding. The compiler can’t verify this code because it can no longer use any static type analysis. So it defers until later. You can help overcome this by providing static casts as a guide for the compiler.