First off, is the form that you are closing the form that contains the
Main(). In other words is it the entry point for the application. I know
you said the behavior wasn't happening before adding the Web Browser
control, however, I just want to make sure.
The only thing that pops into my head is that there is some exception
occuring. Does the process actually end (use Task Manager to find out)
As far as setting the object reference to null, that won't kick off the
garbage collection. You will want to try calling Dispose on the browser
control first. However, I don't think this will help. Have you tried
making a small sample application with the same structure. What if you
don't use the user control and just put the web browser control on the form?
Post more info and I will try to help.
Best of luck,
--
Tom Krueger
Smart Client DevCenter -
http://msdn.microsoft.com/smartclient/
Mobile DevCenter -
http://msdn.microsoft.com/mobility
This posting is provided "as is" with no warranties and confers no rights.
"moondaddy" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I have a vb.net 1.1 winforms app and am using a WebBrowser control
>(AxSHDocVw.AxWebBrowser) on it. When I close the form the entire
>application closes. This behavior didn't happen until I added the
>WebBrowser control. Actually, the WebBrowser (WB) control is on a User
>Control nested on another user control like this:
>
> Form1
> Main User Control (an open a number of different user controls
> depending on the function we want to perform)
> Control with WB.
>
> In the dispose event of the Main User Control I set the reference to ucWB
> to nothing hoping this would help, but it made no difference.
>
> Can someone explain what's happening here and how to resolve it?
>
> Thanks.
>
>
> --
> (E-Mail Removed)
>
Similar Threads
