Scenario:
I'm currently writing a layer to abstract 3 similar webservices into one useable class. Each webservice exposes a set of objects that share commonality. I have created a set of intermediary objects which exploit the commonality. However in my layer I need to convert between the web service objects and my objects.
I've used reflection to create the appropriate type at run time before I make the call to the web service like so:
public static object[] CreateProperties(Type type, IProperty[] properties)
{
//Empty so return null
if (properties==null || properties.Length == 0)
return null;
//Check the type is allowed
CheckPropertyTypes("CreateProperties(Type,IProperty[])",type);
//Convert the array of intermediary IProperty objects into
// the passed service type e.g. Service1.Property
object[] result = new object[properties.Length];
for (int i = 0; i < properties.Length; i++)
{
IProperty fromProp = properties[i];
object toProp = ReflectionUtility.CreateInstance(type, null);
ServiceUtils.CopyProperties(fromProp, toProp);
result[i] = toProp;
}
return result;
}
Here's my calling code, from one of my service implementations:
Property[] props = (Property[])ObjectFactory.CreateProperties(typeof(Property), properties);
_service.SetProperties(folderItem.Path, props);
So each service exposes a different "Property" object which I hide behind my own implementation of my IProperty interface.
The reflection code works in unit tests producing an array of objects whose elements are of the appropriate type. But the calling code fails:
System.InvalidCastException: Unable to cast object of type 'System.Object[]' to type 'MyProject.Property[]
Any ideas?
I was under the impression that any cast from Object will work as long as the contained object is convertable?
That's correct, but that doesn't mean that you can cast containers of type Object to containers of other types. An Object[] is not the same thing as an Object (though you, strangely, could cast Object[] to Object).
Basically, no. There are a few, limited, uses of array covariance, but it is better to simply know which type of array you want. There is a generic Array.ConvertAll that is easy enough (at least, it is easier with C# 3.0):
The C# 2.0 version (identical in meaning) is much less eyeball-friendly:
Or just create a new Property[] of the right size and copy manually (or via
Array.Copy
).As an example of the things you can do with array covariance:
Here, "asObj" is still a
Property[]
- it it simply accessible asobject[]
. In C# 2.0 and above, generics usually make a better option than array covariance.You can't convert an array like that - it's returning an array of objects, which is different from an object. Try Array.ConvertAll
in C# 2.0 you can do this using reflection, without using generics and without knowing the desired type at compile time.
You would want to replace all the Type.GetType("OutputData") calls and the GetProperty("PropertyName") with some code that reads from a config file.
I would also use a generic to dictate the creation of SomeComplexObject
But I said you didn't need to use generics.
No guarantees on performance/efficiency, but it does work.
As others have said, the array has to be of the right type to start with. The other answers have shown how to convert a genuine object[] after the fact, but you can create the right kind of array to start with using Array.CreateInstance:
Assuming
type
is a reference type, this should work - the array will be of the correct type, but you'll use it as anobject[]
just to populate it.Alternative answer: generics.
Then your calling code becomes:
Much cleaner :)