Comments on: Using conventions with Passive View

By: Mark Nijhof

Mark Nijhof — Tue, 29 Dec 2009 20:45:03 +0000

@Rob G
Hehe it was more a joke towards some of the things I have been reading. I think on technical concerns something can be called a BaseXxxx without doing something evil

In my case perhaps Presenter is not a good name, perhaps something like AutoHookUpViewEventsPresenter would be a more descriptive name?

By: Rob G

Rob G — Tue, 29 Dec 2009 20:27:04 +0000

Oops – I called my base controller class “BaseController”. It’s all good and well that “Presenter” wasn’t taken by WinForms, but “Controller” *is* taken by MVC, and without creating a namespacing nightmare – what would you call it… “PrimaryController”?

Great post!

By: The Morning Brew - Chris Alcock » The Morning Brew #503

The Morning Brew - Chris Alcock » The Morning Brew #503 — Tue, 22 Dec 2009 08:16:14 +0000

[...] Using conventions with Passive View – Mark Nijhof picks up a theme from one of Ayende’s Effectus posts and talks about the conventions used in his Command Query Responsibility Separation Sample application [...]

By: Mark Nijhof

Mark Nijhof — Tue, 22 Dec 2009 02:41:21 +0000

@Jarod Ferguson @jdn Thanks guys, I'll blog about the little tiny test framework in the very near future.

By: jdn

jdn — Mon, 21 Dec 2009 21:48:39 +0000

1, that is. And agree with Jarod on liking to see the impl (WebForms are just fine).

By: jdn

jdn — Mon, 21 Dec 2009 20:53:58 +0000

“Then I have a base presenter class without the word “Base” because that would be EVIL”

LOL. 1

Enjoying this series, very informative. Agree with Jarod.

By: Jarod Ferguson

Jarod Ferguson — Mon, 21 Dec 2009 18:06:54 +0000

Pretty cool autowiring here. This would work well in webforms MVP too (why anyone would choose webforms, ya ya it sucks I know, just sayin)

Mark I like your spec framework, have you blogged it before? I would like to see the impl for OnDependency and On.

By: David Perfors

David Perfors — Mon, 21 Dec 2009 10:15:48 +0000

Actually, I still use WinForms… I don’t know why, but the project I’m working on was started with WinForms…

What I found difficult with the standard way of WinForms and your example is Application.Run();
I don’t know the details anymore, but I had troubles with don’t using the Application.Run() command… (I think it had something to do with the skin we use and the component framework that is providing that…)