2.0.0 - DisplayRootViewFor, Message.Attach with Conductor throws ArgumentNullException

[caliburn-micro]

2.0.0 - DisplayRootViewFor, Message.Attach with Conductor throws ArgumentNullException

[nigel-sampson]

I've just recreated what you've described and not seeing the error. Could you create a repo that demonstrates the error.

[tthibodeau]

I was creating an example project and narrowed down when this issue appears.

The exception occurs if you have an x:Name attribute set on the element that matches a ViewModel method and use the Message.Attach="[Event Click] = [Action DoSomething()]" syntax.

Remove the x:Name attribute or change the name and the above syntax works fine.

Repo: https://github.com/tthibodeau/CMissue49.git

[nigel-sampson]

Ok, so the reason the first example didn't work was that under the covers the message conventions use Message.Attach which overwrites the one you created. The second example works because you're not using Message.Attach and the two behaviors can exist side by side.

I'd recommend making sure you don't have conflicting conventions going on.

While the convention manager checks to make sure it doesn't overwrite bindings. It may be a good idea to check that we don't overwrite existing method attachments.

I've created a more explicit issue for this.

[tthibodeau]

I understand why it's happening, but I thought I'd mention it as it wasn't an issue with 1.5.2.

Thanks for looking into it!