views:

18

answers:

1

We have a summary view in our winform app that uses a WebBrowser control to display the summary information from a web page. We are using this to gain some rich tabular layout that we could not accomplish using standard winform controls. the first time the view is displayed on the client it takes a while to spin up (launching IE in the background i assume) and the app freezes for quite a few seconds. I'm considering some sort of pre-loading mechanic that would get IE spun-up in the background and would like some community guidance.

I'm considering launching an off-screen or invisible form with a webbrowser control at app start or launching an IE instance in some sort of side thread at app start.

any suggestions?

+2  A: 

I've not experienced the start up lags you mention, but as an idea, on start-up you could navigate to about:blank. Then on browser's DocumentCompleted event you could kick off a navigation to your proper URL. That might help you understand whether it's your "IE spin-up" that's taking all the time or the content query and render.

In terms of your architecture, unless of course your "rich tabular layout" is already built and fully functional then you might consider using WPF (it has a good WinForms integration story too) in order to get some richer and sexier controls into your app.

Reddog