Last post Jun 12, 2008 01:54 PM by blaketaylor
Apr 18, 2008 12:58 AM|[C.I.] Reman|LINK
The ComponentController can´t return the ActionResult - it´s still "void". Will this issue be solve in the next release or is the ComponentController "obsolent"?
Apr 18, 2008 02:51 AM|Haacked|LINK
What is the ComponentController? I'm assuming that's something in MvcContrib. If so, you should post that question to their forums.
Apr 18, 2008 03:09 AM|[C.I.] Reman|LINK
No - the ComponentController is from your team:
I use this special controller to display dynamic data on an masterpage:
Apr 18, 2008 03:42 AM|Haacked|LINK
Wow, indeed you're right. I think this may be an experimental class someone should not have left in there. I'll look into it.
Apr 18, 2008 03:48 AM|Eilon|LINK
Indeed, ComponentController is used by some of the rendering helpers to render sub-components. We didn't update that class yet in part since we're considering some brand new designs for implementing sub-controllers and sub-components. If you need that class
you might want to consider just using Preview 2 until we've hashed out all the details.
Apr 18, 2008 04:08 AM|[C.I.] Reman|LINK
Ah - thanks for the info.
It still works (for now) - I just wonder why this controller don´t return an ActionResult.
Jun 12, 2008 01:54 PM|blaketaylor|LINK
I hope you guys decide to keep and enhance this feature.
Perhaps the concept of "component controllers" can be replaced with normal controllers the render an alternative view based on a "request context". This would open the doors for the Html.RenderComponet method to take a bool, that turns it into an ajax request
from the rendered output on the clientside.