AxWebBrowser

[Clint MacDonald]

I have used the AxWebBrowser in a Visual Basic Project...

I found that both Framework 1.0 and 1.1 had to be installed for it to work
properly.

I now have found that in Studio 2003, that the probablem has come back even
if both are installed.

When I open a windows form that has the Browser on it and try to Navigate to
a page using the OnEnter or OnLoad events, the page just sits there and does
nothing. If I make a button that navigates to a fil/page, then it works
fine....

Help

Clint MacDonald

[Charles Law]

Hi Clint

I have been using the WebBrowser control from VB.NET for some little while
now, first with VS2002, and now with VS2003 (both now installed).

I have just tried navigating to the MS web site in the Form_Load event
without problem. Do you have any other stuff going on, e.g. processing any
events, like the DocumentComplete event?

Charles
"Clint MacDonald" <cl***@igsol.com> wrote in message
news:O9*************@TK2MSFTNGP11.phx.gbl...

I have used the AxWebBrowser in a Visual Basic Project...

I found that both Framework 1.0 and 1.1 had to be installed for it to work
properly.

I now have found that in Studio 2003, that the probablem has come back even if both are installed.

When I open a windows form that has the Browser on it and try to Navigate to a page using the OnEnter or OnLoad events, the page just sits there and does nothing. If I make a button that navigates to a fil/page, then it works
fine....

Help

Clint MacDonald

[Clint MacDonald]

Hi Charles:

I have been playing around a bit and strangely enough....it seems to work in
the OnActivate event....

however, here are a few more things I have noticed....in my MDI environment,
1) if I have another child opn that has a datagrid on it, the child is
maximized and the datagrid is resized using anchors as a result, then when
the new child is opened with the AxWebBrowser on it, it causes all sorts of
problems....
2) if the previous child window is not maximized or the datagrid has fixed
width, the child window with the AxWebBrowser on it loads fine with the
OnActivated event navigating....
3) If the other current child window does not have a datagrid on it, the
AxWebBrowser loads fine
4) If a previous child window with a datagrid, maximized is open, and then
another window without a datagrid on it is opened and maximized, then
AxWebBrowser window opens fine...thus meaning that it does not work fine
when the previous current child window has a datagrid on it, is maximized,
and the datagrid is resized using the anchors....

I do not see the link here, but there is a definate pattern that is now
obvious and predictable.

any ideas...

Clint
"Charles Law" <la****@btinternet.com> wrote in message
news:u3**************@TK2MSFTNGP10.phx.gbl...

Hi Clint

I have been using the WebBrowser control from VB.NET for some little while
now, first with VS2002, and now with VS2003 (both now installed).

I have just tried navigating to the MS web site in the Form_Load event
without problem. Do you have any other stuff going on, e.g. processing any
events, like the DocumentComplete event?

Charles
"Clint MacDonald" <cl***@igsol.com> wrote in message
news:O9*************@TK2MSFTNGP11.phx.gbl...

I have used the AxWebBrowser in a Visual Basic Project...

I found that both Framework 1.0 and 1.1 had to be installed for it to work properly.

I now have found that in Studio 2003, that the probablem has come back even

if both are installed.

When I open a windows form that has the Browser on it and try to

Navigate to

a page using the OnEnter or OnLoad events, the page just sits there and

does

nothing. If I make a button that navigates to a fil/page, then it works
fine....

Help

Clint MacDonald

[Clint MacDonald]

Looking even further into it,

this problem occurs whether I try and navigate or not...so the navigate to
blank does not even get executed...
I tried doing a test messagebox in the OnLoad even, and it never appears...

the window does not show entirely,
I get a second set of min/max/norm buttons in top right,
The window creates ghosts if another window is dragged over it...

WEIRD

So, What I have done as a work around, is any time a window is opened that
has an AxWebBrowser control on it, I automatically minimize all other child
windows using a for each loop, this solves the problem, but slows window
loading time somewhat.

Thanks for the insight

Clint

"Charles Law" <la****@btinternet.com> wrote in message
news:O3**************@TK2MSFTNGP10.phx.gbl...

Clint

I am not trying to use a datagrid, so that may be why I have not seen the
same problems as you have. That is not to say that I haven't had problems
...

I have been watching several newsgroups, and can see that lots of people
have issues with the WebBrowser control, and not just in .NET.

One thing I have found is that it is imperative that the control initialises fully before attempting to manipulate the DOM. Therefore, I always navigate to about:blank in the Form_Load event, and then in the DocumentComplete
event cache a reference to AxWebBrowser1.document, cast as HTMLDocument. I
then use this when I need access to the DOM.

Also, I stay in the DocumentComplete event until AxWebBrowser1.ReadyState is Complete. You would think that it must be on entry, but I have found that it is not always.

This may be overkill, but I definitely get fewer funnies now that I do all
this.

HTH

Charles
"Clint MacDonald" <cl***@igsol.com> wrote in message
news:%2******************@TK2MSFTNGP12.phx.gbl...

Hi Charles:

I have been playing around a bit and strangely enough....it seems to work

in

the OnActivate event....

however, here are a few more things I have noticed....in my MDI

environment,

1) if I have another child opn that has a datagrid on it, the child is
maximized and the datagrid is resized using anchors as a result, then when the new child is opened with the AxWebBrowser on it, it causes all sorts

of

problems....
2) if the previous child window is not maximized or the datagrid has fixed width, the child window with the AxWebBrowser on it loads fine with the
OnActivated event navigating....
3) If the other current child window does not have a datagrid on it, the
AxWebBrowser loads fine
4) If a previous child window with a datagrid, maximized is open, and then another window without a datagrid on it is opened and maximized, then
AxWebBrowser window opens fine...thus meaning that it does not work fine
when the previous current child window has a datagrid on it, is maximized, and the datagrid is resized using the anchors....

I do not see the link here, but there is a definate pattern that is now
obvious and predictable.

any ideas...

Clint
"Charles Law" <la****@btinternet.com> wrote in message
news:u3**************@TK2MSFTNGP10.phx.gbl...

Hi Clint

I have been using the WebBrowser control from VB.NET for some little while now, first with VS2002, and now with VS2003 (both now installed).

I have just tried navigating to the MS web site in the Form_Load event
without problem. Do you have any other stuff going on, e.g. processing any events, like the DocumentComplete event?

Charles
"Clint MacDonald" <cl***@igsol.com> wrote in message
news:O9*************@TK2MSFTNGP11.phx.gbl...
> I have used the AxWebBrowser in a Visual Basic Project...
>
> I found that both Framework 1.0 and 1.1 had to be installed for it to work

> properly.
>
> I now have found that in Studio 2003, that the probablem has come

back even
> if both are installed.
>
> When I open a windows form that has the Browser on it and try to

Navigate

to
> a page using the OnEnter or OnLoad events, the page just sits there

and does
> nothing. If I make a button that navigates to a fil/page, then it works > fine....
>
> Help
>
> Clint MacDonald
>
>