Yet another blog, yet another open source project

zdeslav wrote on February 27. 2008 at 19:36:

This can be solved by creating a default instance in CustomerDTO:
class CustomerDTO
{
   private SalesRecipientDTO m_salesRecipient = new SalesRecipientDTO();

   public SalesRecipientDTO SalesRecipient { get... }
}

I prefer this to having a SalesRecipient property which can return null.

However, if your SalesRecipientDTO is mapped to SalesRecipient entity you don't need to do it, new instance will be created automatically (see Otis.Tests/UserDTO.cs, which has a similar Boss property which is automatically initialized by the assembler). Of course, it means that you must provide a mapping definition for SalesRecipientEntity->SalesRecipientDTO

zdeslav wrote on February 27. 2008 at 22:48:

i am not sure i fully understand to what property on the source side you want to map. I suppose that customerDto.SalesRecipient.Name receives the value from customerEntity.Name ?

If this is the case, you can use the following trick (i call it a trick because it is not actually a supported scenario, but it works):

[MapClass(typeof(CustomerEntity))]
public class CustomerDTO
{
    // this will generate code which maps  CustomerDTO.SalesRecipient to the source CustomerEntity object
    [Map("source")]  
    public SalesRecipientDTO SalesRecipient;
}

[MapClass(typeof(CustomerEntity))] // map to CustomerEntity class, too
public class SalesRecipientDTO
{
    [Map("$FullName")] // map to CustomerEntity.FullName
    public string Name;
}

public class CustomerEntity // entity type
{
    public string FullName;
}

I will think about it, and try to support it in clearer manner. By the way, for debugging purposes, you can do this (must be called before cfg.BuildAssemblers, or cfg.GetAssembler):

cfg.GenerationOptions.OutputFile = @"d:\output\test.cs";
cfg.GenerationOptions.OutputType = OutputType.SourceCode;

this will generate the mapping code in file d:\output\test.cs (folder d:\output must be already created). In this case mapping assembly will not be
generated so you can't perform the actual mapping but it is helpful if you have trouble with mapping results.

zdeslav wrote on February 27. 2008 at 23:02:

Since you are the first person that i know of which uses otis (besides me, of course) I am more than glad to help

zdeslav wrote on February 28. 2008 at 12:38:

I think this is a genuine bug in Otis. When creating mapper assembly, for every source or target type a reference to its assembly is added. however, if they derive from type defined in some other assembly this one will not be added. I will submit a bug for this.

I don't have time to test it now, but i believe that the following workaround might work:

Add a 'dummy' mapping from any type to DomainBase type, e.g.:
<class name="Namespace.DomainBase, Company.Domain" source="Object" />

this will generate assembler for Object->DomainBase which will do nothing, but it will force mapper to reference the assembly where DomainBase is defined (i hope).

zdeslav wrote on March 3. 2008 at 12:01:

new version (0.2.17) is uploaded at googlecode (http://code.google.com/p/otis-lib/downloads/list). It fixes the external assembly reference issues, and adds some minor improvements (details here: code.google.com/p/otis-lib/wiki/OtisRoadmap)