I need to fetch all the properties of an anonymous type which can be written to.
eg:
var person = new {Name = "Person's Name", Age = 25};
Type anonymousType = person.GetType();
var properties = anonymousType.GetProperties(BindingFlags.Public | BindingFlags.Instance);
The problem is that all the properties have their CanWrite
property false
. This is returned as true for non anonymous types.
I have also tried making a call to PropertyInfo.GetSetMethod()
which returns null
.
How can I check whether the property can be written to?
Edit: Perhaps it would suffice to know if a type is anonymous or not. How do I find out if a type is anonymous using reflection?
Anonymous types generated from C# are always immutable, so the set of writable properties is empty. In VB it's optional: each property defaults to being mutable, but if you prefix it with
Key
it's immutable; only properties declared usingKey
count for equality and hash code generation. Personally I prefer C#'s approach.CanWrite
isn't always returned as true for properties in non-anonymous types - only for writable ones. Properties can be read-only, write-only, or read-write. For example:There is no reliable way to determine if a type is anonymous as the .NET 2.0 runtime didn't support anonymous types. Relying on the format of the "compiler generated name" is not a safe fix as this is likely to change with different versions of the compiler.
It sounds like you answered your own question regarding "How can I check whether the property can be written to" with the statements above: CanWrite is false and GetSetMethod(true) returns null. Those are two signs that you can't write to the property.
Since we're on the .NET 2.0 runtime, there is not an "IsAnonymous" property on System.Type so you don't really have any reliable method to identify an anonymous type.
I think you can check if the type has the
CompilerGenerated
attributeJust use this code.
Properties of anonymous types cannot be assigned to, so reflection reports correctly.
If you were to look at the compiled IL, you'll notice that though the C# code looks like it is using a normal initializer, it is rewritten by the compiler to be a constructor call, which allows the properties to be non-writable outside of the class.