Let's say I have the 3 followings DTOs
public class Mailing
{
public long Id { get; set; }
//...
public long IdSender { get; set; }
public Sender Sender { get; set; }
public long IdTemplate { get; set; }
public Template Template { get; set; }
}
public class Sender
{
public long Id { get; set; }
public string Email { get; set; }
//...
}
public class Template
{
public long Id { get; set; }
public string Name { get; set; }
//...
}
And I have 3 expression trees to manage DAO-to-DTO conversion :
private static readonly Expression<Func<DaoMailing, Mailing>> ToMailingShort =
input => new Mailing
{
Id = input.Id,
IdSender = input.IdSender,
IdTemplate = input.IdTemplate,
// ...
};
private static readonly Expression<Func<DaoTemplate, Template>> ToTemplate =
input => new Template
{
Id = input.Id,
Name = input.Name,
// ...
};
private static readonly Expression<Func<DaoSender, Sender>> ToSender =
input => new Sender
{
Id = input.Id,
Email = input.Email,
// ...
};
How can I build the given expression from the 3 above ?
private static readonly Expression<Func<DaoMailing, DaoTemplate, DaoSender, MailingFull>> ToMailingFull =
(input, template, sender) => new Mailing
{
Id = input.Id,
IdSender = input.IdSender,
IdTemplate = input.IdTemplate,
// ...
Template = new Template
{
Id = template.Id,
Name = template.Name,
// ...
},
new Sender
{
Id = sender.Id,
Email = sender.Emai;,
// ...
}
};
The goal being, obviousely, to avoid rewriting each individual conversion in the composite one
The short answer is use AutoMapper, or the compiled expressions into functions. It is easy in C# to compose functions, much harder to compose expressions.
The longer answer is that this is possible, but not easy. Your code uses the 'friendly' Expression syntax, but to really mix & match the expressions, you would need to use the unfriendly version, which is much uglier and harder to maintain: