ASP.NET MVC

Re: BlockRenderer method broken in RC1?

Nik Coughlin — Sun, 01 Feb 2009 20:58:46 GMT

Thanks for posting that Herne, that's extremely reassuring!

Re: BlockRenderer method broken in RC1?

Herne — Fri, 30 Jan 2009 09:31:10 GMT

I've changed the last line of PartialRequest.Invoke to

SimpleWorkerRequest request = new SimpleWorkerRequest("dummy.html", null, new StringWriter(CultureInfo.CurrentCulture));
handler.ProcessRequest(new HttpContext(request));

and everything seems to be working again. Thoughts?

Edit: Just to clarify, I'm using BlockRenderer this way.

Re: BlockRenderer method broken in RC1?

Herne — Thu, 29 Jan 2009 16:56:48 GMT

Does anyone have any alternative ideas?

(Or a pointer to an idea :) )

Re: BlockRenderer method broken in RC1?

brs — Wed, 28 Jan 2009 21:17:01 GMT

Thanks, but the methods there are very similar to the block renderer, and have the same problem...

Re: BlockRenderer method broken in RC1?

Nik Coughlin — Wed, 28 Jan 2009 20:47:56 GMT

Here's a thread on Stackoverflow with several alternate methods

http://stackoverflow.com/questions/483091/render-a-view-as-a-string

Re: BlockRenderer method broken in RC1?

brs — Wed, 28 Jan 2009 17:43:27 GMT

Thanks for the explanation Phil. Can you recommend any alternatives for capturing the rendered HTML from a partial view? If not, is there any other way to update several different components of the page in a single request? Unfortunately my app is pretty dependent on this.

Re: BlockRenderer method broken in RC1?

Haacked — Wed, 28 Jan 2009 17:32:38 GMT

The reason we reset the content type is that if you set the content type in the action method, when you render the view, the view would change the content type. This is due to the Page's ProcessRequest method which sets the content type. Hopefully we can look at making changes to the core Page class in .NET 4, but we'll see. Sorry for the annoyance.

Re: BlockRenderer method broken in RC1?

brs — Wed, 28 Jan 2009 17:17:19 GMT

I agree, and it seems like a common enough request/complaint. I have been hoping that there would be a good way to do this before the final release, but that's looking less & less likely. It only seems to be getting more difficult with each new release...

I have also considered switching to a new view engine, but it would require rewriting quite a bit of code, which I would obviously like to avoid.

Re: BlockRenderer method broken in RC1?

Nik Coughlin — Wed, 28 Jan 2009 02:43:06 GMT

I was going to transition to RC1 today too, glad I didn't.

I'm doing something vaguely similar, using a BlockRenderer so that I can do RenderPartialToString

We need to be able to render partials to strings! There are just too many things that it's useful for.

Either that or stop using the webform view. God knows I'm not terribly fond of it... but I like intellisense too much to change my view engine.

BlockRenderer method broken in RC1?

brs — Wed, 28 Jan 2009 00:50:34 GMT

Hello,

In my app I need to be able to update several parts of the page with a single ajax request.

I have been using the BlockRenderer method for rendering several partial views. I then stick the rendered html into a JSON object for the javascript to insert into the page.

It appears RC1 breaks the BlockRenderer method. After rendering a partial view, the response stream must be flushed before you can retrieve the contents of the CapturingResponseFilter. It looks like Render() now resets the content type-- but since the response is flushed the first time you render a view, the headers are sent, and when the second view is rendered, you get an exception when it tries to reset the content type.

Is this related to the comment in the release notes about RenderPartial no longer resetting the content type? How can I work around this? Thanks in advance.