http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660try this http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment13http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment13Tue, 02 Dec 2008 09:00:33 GMTHey Everyone, I put together a rough framework which allows you to render views to a string from a controller method in MVC Beta. Additionally, I also put together a Rails-like RJS javascript generating framework for MVC Beta. Check it out at [www.brightmix.com/.../how-to-renderpartial-to-s...](http://www.brightmix.com/blog/how-to-renderpartial-to-string-in-asp-net-mvc) and let me know what you think. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment12http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment12Sun, 16 Nov 2008 23:25:26 GMTI spent a few hours on the same problem (see [http://forums.asp.net/t/1315284.aspx](http://forums.asp.net/t/1315284.aspx)) and it's pretty disappointing to hear it cannot be fixed for RTM :-( @Haacked: Isn't there a way to "hack" it with some output caching? Something like BlockRenderer (see the link) does? http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment11http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment11Thu, 13 Nov 2008 09:51:51 GMTIt has taken me a long time to find this answer. Wow what a waste of time (+4 hours of hacking and searching). I wish there was better documentation for ASP.net (I know it's beta - but i'm impatient :) ) http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment10http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment10Thu, 13 Nov 2008 05:19:45 GMTI am agree with Ayende. When its not possible to do it, it should throw a exception instead of letting me standing in the rain. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment9http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment9Wed, 12 Nov 2008 15:41:29 GMTAyende, use the Spark view engine :) http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment8http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment8Wed, 12 Nov 2008 08:52:14 GMTI might be wrong, but isn't this still in beta? If so, why are you doing production work on this? http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment7http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment7Wed, 12 Nov 2008 08:35:39 GMTPhil, This means that I cannot get the view into a string. That is a PROBLEM. This is so because this is an incredibly common thing to do when you are playing around with composable apps and manipulating views. At the very least, this should throw an exception about this being not supported. Or, much better (from my point of view), is to get the framework to fake the pipeline in order to support it. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment6http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment6Wed, 12 Nov 2008 03:32:42 GMT@Haacked: maybe a compromise? I mean, when the writer parameter is the Response then you do nothing and go like now, so no possible performances hits. When the writer parameter is a custom one you change the response output stream calling the HttpResponse's private method "SwitchWriter" (using reflection) to supply the custom writer. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment5http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment5Tue, 11 Nov 2008 22:36:11 GMTThis is one of them tough decisions we had due to the nature of the framework we're building on. It's less than ideal, but is for the greater good eventually. Yes, the WebFormViewEngine ignores the writer parameter. We exposed the parameter in the underlying API to encourage *other* view engine implementors to do the right thing and write to the writer as they render the output rather than creating one big string that they write out at the end. In part, this was to make sure that RenderPartial would work with other view engines. Unfortunately, we can't change our own view engine to do this same thing as that would require changes to core bits of the Page class etc... MVC is built on top of ASP.NET core and we can't make changes to the core for MVC right now. Maybe when the next major framework release comes out, we can actually fix this. However, since the WebFormViewEngine already streams output to the writer rather than generating one big string, it doesn't suffer the key problem we wanted to solve. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment4http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment4Tue, 11 Nov 2008 22:17:37 GMTOMG!!!! The WebFormView doesn't do anything with the writer parameter, it just swallows it.... that really a bug... even tho I think it cannot be changed since the webviewengine is based on the webform model. One more reason not to use the WebFormViewEngine :) http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment3http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment3Tue, 11 Nov 2008 22:04:10 GMTTry to execute my code. You are going through a different code path. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment2http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment2Tue, 11 Nov 2008 21:56:23 GMTThat's weird, when you supply your own textwriter the render method of the view should write to it. It's used in testing views as well. In my testing code there is: MyTextView view = new MyTextView (templatePath); StringWriter writer = new StringWriter(); view.Render(null, writer); string rendered = writer.ToString(); And it works correctly, at least inside a test case. http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment1http://ayende.com/3687/another-asp-net-mvc-bug-rendering-views-to-different-output-source#comment1Tue, 11 Nov 2008 21:43:42 GMT