(Obviously there's a strong chance this won't meet many challenges you might place in front of it. Are you really interested in all the AM features? Is size an issue?
Any more context you can give? ) EDIT: As they've RTW'd over at AutoMapper Maybe now is the perfect time to ask the question in their forum while the eyes of the world are watching.
I'm just interested in a simple mapper that works on the . NET Compact Framework. Are you going to post your mapper on Google Code / CodePlex?
– Daniel O Feb 2 '10 at 0:25 @DanielO: Not sure whether you're referring to me or Omu. My answer was that I strongly believe that writing YAM is bad news for lots of reasons. On the other hand (where I have different fingers), depending on your exact usage scenario (you could elaborate in order to give us a picture of how much mapping you're doing and whether you're doing formatting and whether performance matters in your context), it may actually make sense to write something Quick And Dirty as Omu has a) shown is possible b) using.
Omu posted most of his and looks open to sharing - I'd ask him. – Ruben Bartelink Feb 2 '10 at 9:31 OK. I've seen that AutoMapper has CF support in the horizon, so I'll just go with the small mapping system until then.
– Daniel O Feb 5 '10 at 4:58 That's great news. The last thing you want is to be maintaining and extending something that isnt core to you. – Ruben Bartelink Feb 5 '10 at 9:05.
EmitMapper is faster emitmapper.codeplex. Com but is is subtle hope that it can run in CF upd: sorry, System.Reflection. Emit doesn't exist in .
Net cf.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.