Timeline for Helper Method for Generating Stubbed ICommand in Rhino Mocks
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 3, 2014 at 7:29 | comment | added | Dan | Actually, I meant currying + overloading ;) Ie, f(x) -> g(x, y) | |
| Sep 3, 2014 at 2:53 | comment | added | Mathieu Guindon | Psst - it's method overloading ;) | |
| Aug 25, 2014 at 14:59 | vote | accept | Robert Gowland | ||
| Aug 25, 2014 at 14:59 | comment | added | Robert Gowland | The Execute and CanExecute methods ICommand interface both accept an object instance, so I think that's what should be used here. Nice idea with the method chaining. It adds some complexity, but it makes it nicer for the consuming code. | |
| Aug 22, 2014 at 17:03 | comment | added | Dan | Ah yes. I've never used WPF, so I didn't know | |
| Aug 22, 2014 at 16:53 | comment | added | svick | This looks like ICommand from WPF, which is weakly typed. | |
| Aug 20, 2014 at 21:15 | history | answered | Dan | CC BY-SA 3.0 |