AxWebBrowser

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Clint MacDonald

    AxWebBrowser

    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

    #2
    Re: AxWebBrowser

    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 DocumentComplet e event?

    Charles


    "Clint MacDonald" <clint@igsol.co m> wrote in message
    news:O9n1yDiRDH A.940@TK2MSFTNG P11.phx.gbl...[color=blue]
    > 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[/color]
    even[color=blue]
    > if both are installed.
    >
    > When I open a windows form that has the Browser on it and try to Navigate[/color]
    to[color=blue]
    > a page using the OnEnter or OnLoad events, the page just sits there and[/color]
    does[color=blue]
    > nothing. If I make a button that navigates to a fil/page, then it works
    > fine....
    >
    > Help
    >
    > Clint MacDonald
    >
    >[/color]


    Comment

    • Clint MacDonald

      #3
      Re: AxWebBrowser

      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" <law.ck@btinter net.com> wrote in message
      news:u3QckTiRDH A.1552@TK2MSFTN GP10.phx.gbl...[color=blue]
      > 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 DocumentComplet e event?
      >
      > Charles
      >
      >
      > "Clint MacDonald" <clint@igsol.co m> wrote in message
      > news:O9n1yDiRDH A.940@TK2MSFTNG P11.phx.gbl...[color=green]
      > > 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[/color][/color]
      work[color=blue][color=green]
      > > properly.
      > >
      > > I now have found that in Studio 2003, that the probablem has come back[/color]
      > even[color=green]
      > > if both are installed.
      > >
      > > When I open a windows form that has the Browser on it and try to[/color][/color]
      Navigate[color=blue]
      > to[color=green]
      > > a page using the OnEnter or OnLoad events, the page just sits there and[/color]
      > does[color=green]
      > > nothing. If I make a button that navigates to a fil/page, then it works
      > > fine....
      > >
      > > Help
      > >
      > > Clint MacDonald
      > >
      > >[/color]
      >
      >[/color]


      Comment

      • Clint MacDonald

        #4
        Re: AxWebBrowser

        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" <law.ck@btinter net.com> wrote in message
        news:O3pQfPjRDH A.2332@TK2MSFTN GP10.phx.gbl...[color=blue]
        > 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[/color]
        initialises[color=blue]
        > fully before attempting to manipulate the DOM. Therefore, I always[/color]
        navigate[color=blue]
        > to about:blank in the Form_Load event, and then in the DocumentComplet e
        > event cache a reference to AxWebBrowser1.d ocument, cast as HTMLDocument. I
        > then use this when I need access to the DOM.
        >
        > Also, I stay in the DocumentComplet e event until AxWebBrowser1.R eadyState[/color]
        is[color=blue]
        > Complete. You would think that it must be on entry, but I have found that[/color]
        it[color=blue]
        > is not always.
        >
        > This may be overkill, but I definitely get fewer funnies now that I do all
        > this.
        >
        > HTH
        >
        > Charles
        >
        >
        > "Clint MacDonald" <clint@igsol.co m> wrote in message
        > news:%23JV%23w7 iRDHA.2152@TK2M SFTNGP12.phx.gb l...[color=green]
        > > Hi Charles:
        > >
        > > I have been playing around a bit and strangely enough....it seems to[/color][/color]
        work[color=blue]
        > in[color=green]
        > > the OnActivate event....
        > >
        > > however, here are a few more things I have noticed....in my MDI[/color]
        > environment,[color=green]
        > > 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[/color][/color]
        when[color=blue][color=green]
        > > the new child is opened with the AxWebBrowser on it, it causes all sorts[/color]
        > of[color=green]
        > > problems....
        > > 2) if the previous child window is not maximized or the datagrid has[/color][/color]
        fixed[color=blue][color=green]
        > > 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[/color][/color]
        then[color=blue][color=green]
        > > 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[/color][/color]
        maximized,[color=blue][color=green]
        > > 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" <law.ck@btinter net.com> wrote in message
        > > news:u3QckTiRDH A.1552@TK2MSFTN GP10.phx.gbl...[color=darkred]
        > > > Hi Clint
        > > >
        > > > I have been using the WebBrowser control from VB.NET for some little[/color][/color]
        > while[color=green][color=darkred]
        > > > 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[/color][/color]
        > any[color=green][color=darkred]
        > > > events, like the DocumentComplet e event?
        > > >
        > > > Charles
        > > >
        > > >
        > > > "Clint MacDonald" <clint@igsol.co m> wrote in message
        > > > news:O9n1yDiRDH A.940@TK2MSFTNG P11.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[/color][/color][/color]
        to[color=blue][color=green]
        > > work[color=darkred]
        > > > > properly.
        > > > >
        > > > > I now have found that in Studio 2003, that the probablem has come[/color][/color][/color]
        back[color=blue][color=green][color=darkred]
        > > > even
        > > > > if both are installed.
        > > > >
        > > > > When I open a windows form that has the Browser on it and try to[/color]
        > > Navigate[color=darkred]
        > > > to
        > > > > a page using the OnEnter or OnLoad events, the page just sits there[/color][/color]
        > and[color=green][color=darkred]
        > > > does
        > > > > nothing. If I make a button that navigates to a fil/page, then it[/color][/color]
        > works[color=green][color=darkred]
        > > > > fine....
        > > > >
        > > > > Help
        > > > >
        > > > > Clint MacDonald
        > > > >
        > > > >
        > > >
        > > >[/color]
        > >
        > >[/color]
        >
        >[/color]


        Comment

        Working...