Re: ComponentController and ActionResult

blaketaylor — Thu, 12 Jun 2008 04:00:00 GMT

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.

Re: How about a very complex page which need many "MVC modules/parts" ?

shinakuma — Thu, 20 Dec 2007 05:00:00 GMT

[quote user="abombss"]By the way Render_Component was deprecated in RoR in favor of partials which are simply UserControls in MS MVC.[/quote]

Explains why Monorail didn't have this concept either. That's very unfortunate. I understand that the problem overusing it will cause. And I also agree with the sentiment that probably 95% of the time, partials are a better way for view partitioning. But I still think that there is definitely a place for components. I like this controller-action seperation over before filters.

[quote user="convit"]Could you please help me to implement a helper function with prototype like this:[/quote]

At first, I wasn't planning on doing this. I briefly played around with the routing features of the drop. Other than that, I haven't had the chance to really dig into this ctp. But curiosity got the best of me and I decided to give it a shot. Gave me a chance to understand the internals of ms-mvc a little better. Bewarned, it's just a proof of concept. There might be a better way of doing it.

In your ViewPage or ViewMasterPage, just do something like <%= this.RenderComponent( new { Controller="Top10", Action="Index", ForumId = 1 } ) %>, that will jump out, invoke Top10Controller.Index(1) and spit out the fragments. Inside the action, you should have access to everything in the context.

public static class RenderComponentExtension
{

public static string RenderComponent(this ViewPage viewPage, object values)
{
string path = viewPage.Url.Action(values);
IHttpContext context = viewPage.ViewContext.HttpContext;
return RenderComponent(path, context);
}

public static string RenderComponent(this ViewMasterPage masterPage, object values)
{
string path = masterPage.Url.Action(values);
IHttpContext context = masterPage.ViewContext.HttpContext;
return RenderComponent(path, context);
}

private static string RenderComponent(string path, IHttpContext context)
{
string oldPath = context.Request.Path;

context.RewritePath(path);

RouteData routeData = RouteTable.Routes.GetRouteData(context);
Type handlerType = routeData.Route.RouteHandler;
IRouteHandler routehandler = (IRouteHandler)Activator.CreateInstance(handlerType);
RequestContext requestContext = new RequestContext(context, routeData);
IHttpHandler httpHandler = (MvcHandler)routehandler.GetHttpHandler(requestContext);

TextWriter oldWriter = context.Response.Output;
StringWriter newWriter = new StringWriter();
context.Response.SwitchWriter(newWriter);
httpHandler.ProcessRequest(HttpContext.Current);

context.RewritePath(oldPath);
context.Response.SwitchWriter(oldWriter);

return newWriter.ToString();
}

}

Search results matching tag 'render_component'

Re: ComponentController and ActionResult

Re: How about a very complex page which need many "MVC modules/parts" ?