In the last post in this series, I showed my second pass (or would you consider it a first pass since the original was more a factory pattern?) at an object to object mapper. It was rather basic and was missing a number of features which would make it really useable (type conversion, string formatting, etc.). Not to mention much of the code that I was working on needed to be moved into my utility library and cleaned up. Well now I'm back to give my third pass at it:
/// <summary>
/// Maps two objects together
/// </summary>
/// <typeparam name="Source">Source type</typeparam>
/// <typeparam name="Destination">Destination type</typeparam>
public class Mapping<Source,Destination>:IMapping
{
#region Constructor
/// <summary>
/// Constructor
/// </summary>
public Mapping()
{
Setup();
}
#endregion
#region IMapping Members
public Type SourceType { get { return typeof(Source); } }
public Type DestinationType { get { return typeof(Destination); } }
public void Sync(object SourceObject, object DestinationObject)
{
if (SourceObject.GetType() == SourceType)
{
for (int y = 0; y < Mappings.Count; ++y)
{
object SourceValue = Utilities.Reflection.GetPropertyValue(SourceObject, Mappings[y].Source);
Utilities.Reflection.SetValue(SourceValue, DestinationObject, Mappings[y].Destination, Mappings[y].Format);
}
return;
}
for (int y = 0; y < Mappings.Count; ++y)
{
object DestinationValue = Utilities.Reflection.GetPropertyValue(SourceObject, Mappings[y].Destination);
Utilities.Reflection.SetValue(DestinationValue, DestinationObject, Mappings[y].Source, Mappings[y].Format);
}
}
public object Create(object Source)
{
if (Source.GetType() == SourceType)
{
object DestinationObject = typeof(Destination).Assembly.CreateInstance(typeof(Destination).FullName);
Sync(Source, DestinationObject);
return DestinationObject;
}
object SourceObject = typeof(Destination).Assembly.CreateInstance(typeof(Source).FullName);
Sync(Source, SourceObject);
return SourceObject;
}
#endregion
#region Protected Functions
/// <summary>
/// Maps a source property to a destination property
/// </summary>
/// <param name="SourceExpression">Source property</param>
/// <param name="DestinationExpression">Destination property</param>
protected void Map(Expression<Func<Source, object>> SourceExpression,
Expression<Func<Destination, object>> DestinationExpression)
{
Map(SourceExpression, DestinationExpression, "");
}
/// <summary>
/// Maps a source property to a destination property
/// </summary>
/// <param name="SourceExpression">Source property</param>
/// <param name="DestinationExpression">Destination property</param>
/// <param name="Format">The string format that the destination should use</param>
protected void Map(Expression<Func<Source, object>> SourceExpression,
Expression<Func<Destination, object>> DestinationExpression,
string Format)
{
Setup();
string SourceName = Utilities.Reflection.GetPropertyName<Source>(SourceExpression);
string DestinationName = Utilities.Reflection.GetPropertyName<Destination>(DestinationExpression);
for (int x = 0; x < Mappings.Count; ++x)
{
if (Mappings[x].Destination == DestinationName)
{
Mappings.RemoveAt(x);
break;
}
}
for (int x = 0; x < Mappings.Count; ++x)
{
if (Mappings[x].Source == SourceName)
{
Mappings.RemoveAt(x);
break;
}
}
Mappings.Add(new MappingInfo(SourceName, DestinationName, Format));
}
/// <summary>
/// Removes a mapping
/// </summary>
/// <param name="SourceExpression">Source property to ignore</param>
protected void Ignore(Expression<Func<Source, object>> SourceExpression)
{
Setup();
string SourceName = Utilities.Reflection.GetPropertyName<Source>(SourceExpression);
for (int x = 0; x < Mappings.Count; ++x)
{
if (Mappings[x].Source == SourceName)
{
Mappings.RemoveAt(x);
break;
}
}
}
/// <summary>
/// Removes a mapping
/// </summary>
/// <param name="DestinationExpression">Destination property to ignore</param>
protected void Ignore(Expression<Func<Destination, object>> DestinationExpression)
{
Setup();
string DestinationName = Utilities.Reflection.GetPropertyName<Destination>(DestinationExpression);
for (int x = 0; x < Mappings.Count; ++x)
{
if (Mappings[x].Destination == DestinationName)
{
Mappings.RemoveAt(x);
break;
}
}
}
#endregion
#region Private Functions
/// <summary>
/// Sets up the mapping
/// </summary>
public void Setup()
{
if (Mappings == null)
{
Mappings = new List<MappingInfo>();
PropertyInfo[] Properties = typeof(Source).GetProperties();
Type DestinationType = typeof(Destination);
for (int x = 0; x < Properties.Length; ++x)
{
if (DestinationType.GetProperty(Properties[x].Name) != null)
{
Mappings.Add(new MappingInfo(Properties[x].Name, Properties[x].Name, ""));
}
}
}
}
#endregion
#region Protected Variables
internal List<MappingInfo> Mappings { get; set; }
#endregion
}
The mapping class was described in the previous post and it works in a similar fashion. It's a base class that needs to be implemented, the manager class goes looking for it in the assembly that you specify, etc. In the constructor, you would still declare your mappings but this time you can now specify a formatting for strings. For instance I could have a DateTime map to a string and have it formatted however you wanted by calling Map(DateTimeProperty,StringProperty,"THE FORMAT I WANT"). Obviously not that exactly as you probably don't have those properties and that format string wouldn't work at all... Past that the mappings are no longer a simple Dictionary of source/destination paths. Instead it's a MappingInfo class, which is really just the source/destination paths and another string that holds the formatting. Otherwise the setup is about the same.
Well there is a slight change to the setup code. Namely they now call Utilities.Reflection.GetPropertyName. It's the same as the GetName function from the previous post, just moved into my utility library. Nowwhere the changes start rolling in is the Sync function and a new function called Create. In Sync, the first thing you may notice is the fact that it checks to see if the Source object is actually of type Source. The reason for this is really to make my life easier. In my first attempt, it only synced from the Source to the Destination. This was great if you were only sending data one way, but if you wanted to sync the other way you had to set up another mapping class. Sort of kills the whole less coding/making your life easier idea. So the manager now just checks if the source/destination match up (in either order) and sends in the objects. As such the Mapping class needs to figure out which direction it's going. Once the direction is established it calls Utilities.Reflection.GetPropertyValue, which can be found below:
/// <summary>
/// Gets a property's value
/// </summary>
/// <param name="SourceObject">object who contains the property</param>
/// <param name="PropertyPath">Path of the property (ex: Prop1.Prop2.Prop3 would be
/// the Prop1 of the source object, which then has a Prop2 on it, which in turn
/// has a Prop3 on it.)</param>
/// <returns>The value contained in the property or null if the property can not
/// be reached</returns>
public static object GetPropertyValue(object SourceObject, string PropertyPath)
{
if (SourceObject == null||string.IsNullOrEmpty(PropertyPath))
return null;
string[] Splitter = { "." };
string[] SourceProperties = PropertyPath.Split(Splitter, StringSplitOptions.None);
object TempSourceProperty = SourceObject;
Type PropertyType = SourceObject.GetType();
for (int x = 0; x < SourceProperties.Length; ++x)
{
PropertyInfo SourcePropertyInfo = PropertyType.GetProperty(SourceProperties[x]);
if (SourcePropertyInfo == null)
return null;
TempSourceProperty = SourcePropertyInfo.GetValue(TempSourceProperty, null);
if (TempSourceProperty == null)
return null;
PropertyType = SourcePropertyInfo.PropertyType;
}
return TempSourceProperty;
}
In my case, I make no assumptions that you are only going to get shallow properties. For all I know you're going to want something like MyObject.CurrentDate.Month and map that to some Label somewhere. So the function takes a string path (in the example I gave it would actually be "CurrentDate.Month" assuming MyObject was the object and not a property) and simply loops through it trying to get to the property specified and its value. Anyway, the Sync function calls this to get the current source value and then feeds that to the Utilities.Reflection.SetValue function. This function is where it gets a bit more interesting.
/// <summary>
/// Sets the value of destination property
/// </summary>
/// <param name="SourceValue">The source value</param>
/// <param name="DestinationObject">The destination object</param>
/// <param name="PropertyPath">The path to the property (ex: MyProp.SubProp.FinalProp
/// would look at the MyProp on the destination object, then find it's SubProp,
/// and finally copy the SourceValue to the FinalProp property on the destination
/// object)</param>
/// <param name="Format">Allows for formatting if the destination is a string</param>
public static void SetValue(object SourceValue, object DestinationObject,
string PropertyPath, string Format)
{
string[] Splitter = { "." };
string[] DestinationProperties = PropertyPath.Split(Splitter, StringSplitOptions.None);
object TempDestinationProperty = DestinationObject;
Type DestinationPropertyType = DestinationObject.GetType();
PropertyInfo DestinationProperty = null;
for (int x = 0; x < DestinationProperties.Length - 1; ++x)
{
DestinationProperty = DestinationPropertyType.GetProperty(DestinationProperties[x]);
DestinationPropertyType=DestinationProperty.PropertyType;
TempDestinationProperty = DestinationProperty.GetValue(TempDestinationProperty, null);
if (TempDestinationProperty == null)
return;
}
DestinationProperty = DestinationPropertyType.GetProperty(DestinationProperties[DestinationProperties.Length - 1]);
SetValue(SourceValue, TempDestinationProperty, DestinationProperty, Format);
}
This function works in a similar fashion to the GetPropertyValue function to get the destination property that we want. This function then calls another version of SetValue:
/// <summary>
/// Sets the value of destination property
/// </summary>
/// <param name="SourceValue">The source value</param>
/// <param name="DestinationObject">The destination object</param>
/// <param name="DestinationPropertyInfo">The destination property info</param>
/// <param name="Format">Allows for formatting if the destination is a string</param>
public static void SetValue(object SourceValue, object DestinationObject,
PropertyInfo DestinationPropertyInfo, string Format)
{
if (DestinationObject == null || DestinationPropertyInfo == null)
return;
Type DestinationPropertyType = DestinationPropertyInfo.PropertyType;
DestinationPropertyInfo.SetValue(DestinationObject,
Parse(SourceValue, DestinationPropertyType, Format),
null);
}
And this funcion sets the property's value but you'll notice that there is a call to Parse in the value portion of the PropertyInfo.SetValue function. This is once again, yet another function within the utility library:
private static object Parse(object Input, Type OutputType,string Format)
{
try
{
if (Input==null || OutputType == null)
return null;
Type InputType = Input.GetType();
if (InputType == OutputType)
{
return Input;
}
else if (OutputType == typeof(string) && !string.IsNullOrEmpty(Format))
{
return StringHelper.FormatToString(Input, Format);
}
else if (OutputType == typeof(string))
{
return Input.ToString();
}
else
{
return CallMethod("Parse", OutputType.Assembly.CreateInstance(OutputType.FullName), Input.ToString());
}
}
catch { throw; }
}
This function determines if the objects are the same type. If they are, it simply returns the input object. If, however it is a string and the format string isn't null, it calls FormatToString (this is just the FormatToString function from my previous post). If it's a string but the format string is null, it simply calls Input.ToString(). And lastly if they are two different types (for example copying an int to a float), it calls yet another function called CallMethod:
/// <summary>
/// Calls a method on an object
/// </summary>
/// <param name="MethodName">Method name</param>
/// <param name="Object">Object to call the method on</param>
/// <param name="InputVariables">(Optional)input variables for the method</param>
/// <returns>The returned value of the method</returns>
public static object CallMethod(string MethodName, object Object,params object[] InputVariables)
{
if(string.IsNullOrEmpty(MethodName)||Object==null)
return null;
Type ObjectType = Object.GetType();
MethodInfo Method = null;
if (InputVariables != null)
{
Type[] MethodInputTypes = new Type[InputVariables.Length];
for (int x = 0; x < InputVariables.Length; ++x)
{
MethodInputTypes[x] = InputVariables[x].GetType();
}
Method = ObjectType.GetMethod(MethodName, MethodInputTypes);
if (Method != null)
{
return Method.Invoke(Object, InputVariables);
}
}
Method = ObjectType.GetMethod(MethodName);
if (Method != null)
{
return Method.Invoke(Object, null);
}
return null;
}
You see, I've been writing a lot of code that would need to call a function of an object using reflection as of late. In this case I can simply tell it the name of the function, send in the object, and any needed input values. The function in turn looks for functions with the specified name that takes the input values (if there are any). If it finds one, it then invokes it, sending in the appropriate values. That's it, but it allows me to do away with rewriting that bit of code every time I need it. Anyway, in this case it's called looking for the Parse function on the object (int.Parse, float.Parse, etc.). It then returns the newly parsed item which then gets set as the property's value. Note that it doesn't do anything special, if you pass in 1.2 and want to convert it to an int, it will fail.
Anyway, that's it to the Sync function (once you parse through the 10 or so layers). The other function is the Create function. This goes back to my need to have this thing act like a factory pattern a bit. All the function does is creates a new instance of either the destination or source object (basically it creates the opposite of what is sent in) and then calls Sync. That's it. So there you go, we now have a simple object to object mapper that does type conversion and string formatting. I'm actually pretty happy with it at this point, although I could speed it up with some lightweight code gen like Gunner Peipman has been doing in the object to object mapper that he has been building. Which by the way you should take a look at if your needs are fairly simple as his implementation is pretty good at this point. Unfortunately it doesn't fit my needs or I'd use it. The next post I'll show the reworked version of my factory/mapper that I was working on in the first post to work with the newer code. So try it out, leave feedback, and happy coding.
837972e0-46db-4f28-8d8f-3f8819496296|0|.0