StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I have a similar application and I think the WebBrowser control works very well. If you think it's what you need, I would for it and there's many other applications that do something similar. You can call Javascript functions in the HTML page from C# using <code>HtmlDocument.InvokeScript()</code>, and C# from Javascript using <code>window.external</code> and having this two-way communication makes life simple.</p> <p>Users do not need IIS installed as you're not running a web server, just displaying content using HTML.</p> <p>I would go for the built-in IE control rather than webkitdotnet to be honest. Although WebKit itself is superior to IE, the webkitdotnet project at version 0.5 it doesn't have the C#<> JavaScript communication or DOM access and it seems hard to tell if it's still being actively developed. It'll be great if/when it gets feature parity as IE is obviously far from perfect, but the advantage of the built-in IE control is every user of your app will have it already installed and the WebBrowser control is well tested. There are some disadvantages I've found:</p> <ul> <li>IE versions may range from 6 to 9, so you'll to test to make sure your content works in all (as with a website).</li> <li>There's a bug in IE (at least up to 8) that relative links do not work in combination with a <code><base href="file://..."></code>. This can stop you being able to use relative links in your local HTML documents.</li> <li>Sometimes pages display differently inside the WebBrowser control than they do out of it. For instance, <a href="http://bugs.jquery.com/ticket/7104" rel="nofollow">http://bugs.jquery.com/ticket/7104</a> is one and I've come across another similar bug affecting cufon. </li> <li>For compatibility reasons, even if your users install IE > 7 the WebBrowser control will still render your content in IE7 rendering mode by default. This is different to standalone IE which renders in the most-standard mode by default, so it can catch you out if you're not expecting it. You can change this by adding <code><meta http-equiv="X-UA-Compatible"</code> tag if you want, though I actually found it makes life easier as it reduces the amount of different versions you've got to test against.</li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload