> what's wrong with inheriting from Controller? No need to, there are other ways to discover Controller classes: - based on name - an interface - based on namespace There are other ways to expose the API a base controller gives us: - DI a service eg. Redirector or Renderer or Context
I can only have one base class so let me choose it, do not force one on me. If you get rid of this limitation (having to inherit from Controller) then "controller" becomes irrelevant and all u need is a method(action) to execute :) much simpler IMO. Cheers, John On 09/04/2011, at 16:52, Krzysztof Koźmic <[email protected]> wrote: > +1 on doco. > > what's wrong with inheriting from Controller? > > On 09/04/2011 3:42 PM, John Simons wrote: >> >> A few more points that I would like to see: >> - Awesome doco on how to get started + advanced topics; >> - Tools to automate tasks (eg. R# templates, VS integration, ....); >> - OWIN integration; >> - Conventions+++, please do not force me to inherit from Controller ever >> ever again! >> >> I'm wondering why bother with "Easy migration from ASP.NET MVC – you can >> have both co-existing in the same project if you want to" ? >> >> Cheers >> John >> >> >> From: Krzysztof Koźmic <[email protected]> >> To: [email protected] >> Sent: Saturday, 9 April 2011 10:12 AM >> Subject: Re: MR+++ goals and value prop >> >> It is hard to disagree with those points (value proposition). There's one >> (or two) notable absent though, that is conventions and defaults. >> >> I expected the "How does MR+++ help me?" to contain something like: >> >> - I can quickly add features with zero or mimimum "setup" by following MR+++ >> conventions and relying on reasonable defaults >> >> Another thing is, for me next gen web-apps more and more means - apps (vith >> version) optimized for mobile devices (smartphones, tablets). >> Making explicit effort to support that would fit the list well IMO. >> >> All in all - good to have you back :) >> >> Krzysztof >> >> On 09/04/2011 5:07 AM, hammett wrote: >> > If there's one thing I've learned at MS is that before writing a >> > single line of code, you should have a clear view of what you want to >> > accomplish, the value proposition - if you want people to use it - and >> > a measure of success. I've put together a small docs on my view to >> > mr+++ >> > >> > Thoughts? >> > >> > https://docs.google.com/document/d/1AkeeJPh8kZQKtnHN3RDR3v-UfG7zt9wCL0jMiualUqI/edit?hl=en&authkey=CN7U99YN >> > >> >> -- You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/castle-project-devel?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
