AssertConfigurationIsValid collect all errors rather than throw first one

[hazzik]

It would be useful to see all mapping validation errors at one go http://martinfowler.com/articles/replaceThrowWithNotification.html

[hazzik]

In DryRun

[jbogard]

So currently I do a two step operation - first find unmapped members, then find unmapped types. This is to do both in one go?

[hazzik]

Not in one go, but in one exception. Currently if you have unmapped types, AM will throw one exception for each unmapped type usage.

Consider following situation

class A {} 
class B {} // A => B is NOT mapped
class Source 
{
    public A P1 {get; set;}
    public A P2 {get; set;}
    public A P3 {get; set;}
}
class Dest
{
    public B P1 {get; set;}
    public B P2 {get; set;}
    public B P3 {get; set;}
}

So the sequence of events would be like this:

1. AM throws that Source.P1 => Dest.P1 using unmapped A => B
2. Fix by doing something about this, but do not map A=>B & Recompile & Run
3. Repeat for next unmapped class

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.