Hi,
We have posted a new build that should address this issue. You can download the new build from our download page.
This build changed the design time support for the WebControl object. Instead of displaying all WebView's properties and events inside the WebControl's property/event list, this build adds the WebView component directly to the form and give it a name. As such instead of using:
Code: Visual Basic.NET
WebControl1.WebView.Url = some_url
In this build you would use:
Likewise, you would also be able to handle the events on the WebView object directly instead of through the WebControl object. To see the difference, you can start a new form and drag the WebControl into the form, you will see that in addition to adding a new WebControl into the form, a new WebView object is also being added into the form. You will then use the WebView object directly.
Hope this resolves the issue for you. Please feel free to let us know if you see any other problems.
Thanks!