I am getting an error that says:
'object' does not contain a definition for 'Title'
all the code is also on github
I have a ConsoleApplication1 that looks like this
namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{
Movie m = new Movie();
var o = new { Title = "Ghostbusters", Rating = "PG" };
Console.WriteLine(m.PrintMovie(o));
}
}
}
and Movie.cs
public class Movie : DynamicObject
{
public string PrintMovie(dynamic o)
{
return string.Format("Title={0} Rating={1}", o.Title, o.Rating);
}
}
it works fine from the SAME project, but if I add ConsoleApplication2 with a reference to ConsoleApplication1 and add the Exact same code
namespace ConsoleApplication2
{
class Program
{
static void Main(string[] args)
{
Movie m = new Movie();
var o = new { Title = "Ghostbusters", Rating = "PG" };
Console.WriteLine(m.PrintMovie(o));
}
}
}
I get an error:
'object' does not contain a definition for 'Title'**
even though it is in the dynamic object.
Here is a screen shot:
I am doing something like this and trying to call the movie function from a test project.
Jahamal's answer doesn't say why you get the error. The reason is that the anonymous class is internal
to the assembly. Keyword dynamic
doesn't allow you to bypass member visibility.
The solution is to replace the anonymous class with named public class.
Here's another good example explaining the reason and another possible solution.
The reason the call to
data2.Person
fails is that the type information ofdata2
is not available at runtime. The reason it's not available is because anonymous types are not public. When the method is returning an instance of that anonymous type, it's returning aSystem.Objec
t which references an instance of an anonymous type - a type whose info isn't available to the main program. The dynamic runtime tries to find a property calledPerson
on the object, but can't resolve it from the type information it has. As such, it throws an exception. The call todata.Name
works fine sincePerson
is a public class, that information is available and can be easily resolved.
This can affect you in any of the following cases (if not more):
- You're returning a non-public, non-internal type using
System.Object
. 2. You're returning a non-public, non-internal derived type via a public base type and accessing a property in the derived type that's not in the base type. 3. You're returning anything wrapped inside an anonymous type from a different assembly.