The WebBrowser control is a system component so there should be nothing to install or configure - it should always work.

There might be System admin rules that might cause the inability to embed the browser control. It's uncommon though.

The other issue that might be happening though is the fact the control uses IE7 by default and you're probably using a public mapping API. It's quite likely that the mapping API may have discontinued support for IE7 and that's why the map no longer works.

You can work around this by setting registry keys for your application and forcing a more reasonable version of IE to run.
http://weblog.west-wind.com/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version

+++ Rick ---




>Somehow lately, my Map project is missing the Microsoft Web browser component.
>
>So when I create the .exe and install it, then when I run it at customer sites, it opens a dialog box to look for ocx file. Then it errors out.
>
>I have made sure my FORM has the component on it, and under Tools, Options, Controls I have the Web browser checked.
>
>So my questions are,
>
>Where on the project should the component show up?
>How can I ensure the component is in the .exe package?
>Does the component need to be registered?
>
>This was working at some point in the past.
>
>Thanks