Client-Side ASP.NET Revisited?

The WebBrowser control runs with the same security paranoia model that’s in Internet Explorer. This means is that a Web page referencing local external JavaScript or CSS files will not be rendered—even when an absolute, HTTP URI pointed at a client-side ASP.NET ‘server’ is used (such as the one described by Dino Esposito in “ASP. NET Client-side Hosting with Cassini”). Evidently the WebBrowser control will not load a file declared in a src or href attribute from a location that is in any way related to the local file system.

My workaround is to ‘inject’ the contents of these files into the Web page during the load event of the Windows Forms hosting the WebBrowser control:

#region Load external files:

this._clientXml = new XPathDocument(Properties.Settings.Default.ClientXml);

this._clientXslt.Load(Properties.Settings.Default.ClientXslt);

string css = String.Empty;
using (StreamReader file = File.OpenText(Properties.Settings.Default.ClientCss))
   css = file.ReadToEnd();

string jsData = String.Empty;
using (StreamReader file = File.OpenText(Properties.Settings.Default.DataValidationJs))
   jsData = file.ReadToEnd();

string js = String.Empty;
using (StreamReader file = File.OpenText(Properties.Settings.Default.ClientJs))
   js = file.ReadToEnd();

using (StreamReader file = File.OpenText(Properties.Settings.Default.ClientXhtml))
   string xhtml = file.ReadToEnd();
xhtml = String.Format(xhtml,jsData,js,css);
this._browser.Document.Write(xhtml);

#endregion

Before I resorted to such a primitive (and effective) solution, other options related to Client-Side ASP.NET ‘servers’ were examined. The following table summarizes:

rasx()