I have a view rendering a stream using the response BinaryWrite method. This all worked fine under ASP.NET 4 using the Beta 2 but throws this exception in the RC release:
I did Levi's answer. It's actually super easy. My code writes an image to the response, which is previously gotten from the file system after various checks.
public class BookImageResult : ActionResult
{
private readonly GraphicReport graphicReport;
public BookImageResult(GraphicReport graphicReport)
{
this.graphicReport = graphicReport;
}
public override void ExecuteResult(ControllerContext context)
{
var response = context.RequestContext.HttpContext.Response;
response.Clear();
response.ContentType = graphicReport.ContentType;
response.BinaryWrite(graphicReport.Image);
response.End();
}
}
The line at the end of the controller just looks like this:
return new BookImageResult(graphicReport);
Someone mark Levi's response as the answer!
Another way to do something similar is to use the built-in File
ActionResult
:
var bytes = GetPdfBytes("Performance Report", htmlString);
return File(bytes, "binary/octet-stream", "Performance Report.pdf");
When a ViewPage begins executing, it assumes certain things about the remainder of the request. The particular thing that is tripping you up is that a ViewPage assumes that the remainder of the request will be a normal HTML or some other textual response, so it switches the response's TextWriter with its own writer.
In your case, you should make a new ActionResult-derived class whose ExecuteResult method encapsulates the logic in your Page_Load method. Your action method should return an instance of your custom class, and the invoker will run the ExecuteResult method at the appropriate time. This bypasses the view engines entirely, which prevents the error you're running in to and gives you a slight performance boost.