BLToolkit. Mapping ObjectToObject, without copy creation.

Problem in a trace: it is necessary to display one object on another (already created), types identical. For reference types to copy links. Found in BLToolkit class BLToolkit. Mapping. Map, it it does, but creates each time new object:

DestObject = BLToolkit.Mapping.Map.ObjectToObject<Template> (SourceObject); 

2 2011-04-07 22:25:00

•  
•  

•  
•  

Hello, NNetman, you wrote:

NN> the Problem in a trace: it is necessary to display one object on another (already created), types identical. For reference types to copy links.

Then it is possible to receive simply all fields of object (Type:: GetFields (BindingFlags. Instance|BindingFlags. NonPublic)) to walk on them and to appropriate field values of one object to fields of another:

using System; 
using System. Reflection; 

class Program 
{ 
  static void Main (string [] args) { 
    Action source = () => Console. WriteLine ("Aaa"); 
    Action target = () => Console. WriteLine ("Bbb"); 
    target ();//"Bbb" 
    Copy (source, target); 
    target ();//"Aaa" 
  }

  static void Copy (object source, object target) { 
    if (source == null) { 
      throw new ArgumentNullException ("source"); 
    } else if (target == null) { 
      throw new ArgumentNullException ("target"); 
    } else if (source. GetType ()! = target. GetType ()) { 
      throw new ArgumentException ("source. GetType ()! = target. GetType ()", "target"); 
    }//if 

    var type = source. GetType (); 
    var fields = type. GetFields (BindingFlags. Instance | BindingFlags. NonPublic); 
    Array. ForEach (fields, field => field. SetValue (target, field. GetValue (source))); 
  }
}

3 2011-04-07 22:40:00

•  
•  

•  
•  

Hello, NNetman, you wrote:

NN> the Problem in a trace: it is necessary to display one object on another (already created), types identical. For reference types to copy links. Found in BLToolkit class BLToolkit. Mapping. Map, it it does, but creates each time new object:
NN> DestObject = BLToolkit.Mapping.Map.ObjectToObject<Template> (SourceObject);

In the same place there is an overload which accepts destinationObject.

4 2011-04-08 00:04:00

•  
•  

 Yes _FRED _, it is a variant, but reflection me does not arrange.

5 2011-04-08 00:12:00

•  
•  

•  
•  

Hello, MozgC, you wrote:

MC> Hello, NNetman, you wrote:

NN>> the Problem in a trace: it is necessary to display one object on another (already created), types identical. For reference types to copy links. Found in BLToolkit class BLToolkit. Mapping. Map, it it does, but creates each time new object:
NN>> DestObject = BLToolkit.Mapping.Map.ObjectToObject<Template> (SourceObject);

MC> In the same place there is an overload which accepts destinationObject.

Yes, there there is an overload

public static T ObjectToObject <T> (object sourceObject, params object [] parameters); 

But here parameters, it is explicit not destinationObject that actually and was  , does not work.

6 2011-04-08 00:12:00

•  
•  

•  
•  

Hello, NNetman, you wrote:

NN> Yes _FRED _, it is a variant, but reflection me does not arrange.

And by what image  at you  does?

7 2011-04-08 00:30:00

•  
•  

•  
•  

Hello, _FRED _, you wrote:

_FR> Hello, NNetman, you wrote:

NN>> Yes _FRED _, it is a variant, but reflection me does not arrange.

_FR> And what image  at you  does?

It uses reflection once then on the fly collects the assembly and connects it.

8 2011-04-08 00:30:00

•  
•  

•  
•  

Hello, NNetman, you wrote:

NN>>> Yes _FRED _, it is a variant, but reflection me does not arrange.
_FR>> And what image  at you  does?
NN> It uses reflection once then on the fly collects the assembly and connects it.

Aha, means all the same arranges you  

The main thing in my answer was "to receive all fields of object, to walk on them and to appropriate field values of one object to fields of another". And  __ only on the first step to "receive" 

Not on an example it was necessary to turn attention (the example only shows that algorithm basically the worker), and to think over implementation of algorithm approaching you - the data in a question contained insufficiently what to consider all that to you actually it is required.

It would be desirable faster: please, it is possible and instead of SetValue/GetValue to use more modern methods:

using System; 
using System. Linq; 
using System. Linq. Expressions; 
using System. Reflection; 

class Program 
{ 
  static void Main (string [] args) { 
    Action source = () => Console. WriteLine ("Aaa"); 
    Action target = () => Console. WriteLine ("Bbb"); 
    target ();//"Bbb" 
    Copy (source, target); 
    target ();//"Aaa" 
  }

  static void Copy <T> (T source, T target) { 
    if (source == null) { 
      throw new ArgumentNullException ("source"); 
    } else if (source. GetType ()! = typeof (T)) { 
      throw new ArgumentException ("source. GetType ()! = typeof (T)", "source"); 
    } else if (target == null) { 
      throw new ArgumentNullException ("target"); 
    } else if (source. GetType ()! = target. GetType ()) { 
      throw new ArgumentException ("source. GetType ()! = target. GetType ()", "target"); 
    }//if 

    var copy = CreateMapper <T> (); 
    copy (source, target); 
  }

  static Action <T, T> CreateMapper <T> () { 
    var source = Expression. Parameter (typeof (T)); 
    var target = Expression. Parameter (typeof (T)); 

    var type = typeof (T); 
    var assigns = 
      from field in type. GetFields (BindingFlags. Instance | BindingFlags. NonPublic) 
      let left = Expression. Field (target, field) 
      let right = Expression. Field (source, field) 
      select Expression. Assign (left, right); 

    var lambda = Expression. Lambda <Action <T, T>> (Expression. Block (assigns), source, target); 
    return lambda. Compile (); 
  }
}

It is necessary to finish only this example to digestible (well there Memoize to fasten on obtaining  to learn to cause  with dynamic type ... but it already behind frames of the given arguing).

9 2011-04-08 00:30:00

•  
•  

•  
•  

Hello, NNetman, you wrote:

MC>> In the same place there is an overload which accepts destinationObject.
NN> Yes, there there is an overload

Track please for  in at writing of answers

NN> public static T ObjectToObject <T> (object sourceObject, params object [] parameters); 

NN> But here parameters, it is explicit not destinationObject that actually and was  , does not work.

There there is also such overload:

public static object ObjectToObject (object sourceObject 
[b], object destObject[/b], params object [] parameters) 

10 2011-04-08 00:30:00

•  
•  

•  
•  

Here about " __ only on the first step" to receive "" is generally speaking not truly. Because, by call GetValue/SetValue each time is used meta data. And in the second example, yes... The lambda is compiled... But by its each call it will be caused type. GetFields (BindingFlags. Instance | BindingFlags. NonPublic) besides, each time - . About Assign I do not know as it works most likely on clever  the code , only in this case will be faster than in the first example.

11 2011-04-08 08:45:00

•  
•  

•  
•  

Yes, really is such, found
  Thanks.

12 2011-04-08 08:45:00

•  
•  

•  
•  

Hello, the Anonymous author, you wrote:

Here about " __ only on the first step" to receive "" is generally speaking not truly. Because, by call GetValue/SetValue each time is used meta data.

Under  it is understood GetFields. Concerning GetValue/SetValue try to think attentively all the same that I told in the message.

And in the second example, yes... The lambda is compiled... But by its each call it will be caused type. GetFields (BindingFlags. Instance | BindingFlags. NonPublic) besides, each time  .

By a lambda call "GetFields" each time will not be caused. If you consider differently, write the code which it shows 
 
And, generally, you up to the end to read my message worked?