Support symmetric conventions

[kkozmic]

Symmetric conventions would be ones like the following:

All DTOs must live in Foo.Dtos* namespace in Foo.Contracts.dll assembly
nothing but DTOs can live in Foo.Dtos* namespace in Foo.Contracts.dll assembly

It would be nice if we could somehow get separate reports for the two (generate both if both fail), although I doubt that would be possible. In that case, do we want to go for a double report (both failures in the same report) or just treat it as two failing asserts in a test where if the first fails users can't know about the second one.

Alternatively we could have an easy way of splitting this into two tests, although that sounds like a hassle...

[JakeGinnivan]

This is an awesome idea

[kkozmic]

do you want to spike it?

[JakeGinnivan]

Yeah k, will give it a go tomorrow. Just doing some VSTO Contrib stuff atm (trying to get the next release out, its very close!)

[kkozmic]

The trick here I imagine would be to do it in such a way that the convention data stays agnostic to whether convention that uses it is symmetric or not (the same data type could be used by different conventions, some symmetric some not...

[kkozmic]

ok, no worries, I probably won't have the time to do any work on it until the weekend anyway :(

[JakeGinnivan]

Exception message looks like this:

Dtos must be under the 'TestAssembly.Dtos' namespace
----------------------------------------------------

    TestAssembly.SomeDto


Non-Dtos must not be under the 'TestAssembly.Dtos' namespace
------------------------------------------------------------

    TestAssembly.Dtos.AnotherClass

This convention can also be used for Message handlers must be under the 'Foo.Handlers' namespace or Domain objects must be under the 'Foo.Domain' namespace

[kkozmic]

love it!