Jim Holmes

I'm working with a .NET 2.0 WinForms app which hosts a WebBrowser control. I'm unable to launch resources which are located on the local filesystem.

The majority of the app's content is stored in a database. I use the WebBrowser's Navigating event and capture the target Url, then grab content from the DB and pass that content to the WebBrowser's HtmlDocument.DocumentText property.

That's working fine; however, I'm unable to navigate to open any resources on the local filesystem -- the Navigating event doesn't even fire when a link points to a file-based location.

I've tried setting the local machine lockdown registry key and opting out of cross-domain protection as noted here http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=813117&SiteID=1&pageid=0#1200595, but neither option worked for me.

I'm developing on Vista; however, the target OSes are Win 2000 SP4 and XP SP2.


Re: Internet Explorer Extension Development WebBrowser Control and IE7 on Vista


Hi Jim,

What happens when you test this on a Win2K/IE6 SP1 machine

(Be warned that IE6 SP1 has no forward compatibility with IE7 Vista... consider developing on a win2K machine first and then migrating to the IE7 platforms)

What happens when you enter your file based resource location in the address bar of IE7


Re: Internet Explorer Extension Development WebBrowser Control and IE7 on Vista

Jim Holmes

I can access the file-based resource fine from IE7's address bar. Furthermore, I can save the rendered HTML for the page holding the link, then open that file in IE7 -- navigation works fine since the HTML has been loaded from a file.

I seem to be having the same issue on Win2K/IE6, so perhaps this is more a cross-domain issue