A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
For anyone else with the same issue, until Microsoft gives us a proper fix, I have a potential workaround. It's messy, though, because it looks like the HTML string is composed by the rendering engine, then sent to the HtmlTextWriter in one big chunk.
In your .aspx.cs:
protected override void Render( HtmlTextWriter writer )
{
if( Page.IsPostBack )
{
writer = new HtmlTextWriter_Fix( writer.InnerWriter );
}
base.Render( writer );
}
class HtmlTextWriter_Fix : HtmlTextWriter
{
public HtmlTextWriter_Fix( TextWriter writer ) : base( writer )
{
}
public override void Write( string s )
{
if( s.Contains( "ResourceStreamID=Blank.gif ALT=\"Blank image" ) )
s = s.Replace( "ResourceStreamID=Blank.gif ALT=\"Blank image", "ResourceStreamID=Blank.gif\" alt=\"No content" );//[awaiss] The length has to match or the resulting content won't be parsed correctly (not sure why)
base.Write( s );
}
}