Suppressing .Net-BroadcastEventWindow issue

19 Oct 2006 7:56 PM

Chris DiPierro

Since migrating an application from .Net framework 1.1 to 2.0, I have an
issue where when the app exits, I receive a popup error referring to the
.Net-BroadcastEventWindow having an application error.

Some searching through Google groups indicates that this is probably COM
related. The app does in fact reference a legacy COM object (not ours to
control) and if I don't access it, the error doesn't occur on exit.
Unfortunately, that COM object is rather important, so I can't choose to
not use it.

Ultimately the app seems to work fine and without any errors relating to
the COM object, and as mentioned, none of these issues existed in the
1.1 framework. At this point I'd just like to suppress the error if at
all possible. Finding the cause is a good goal going forward, but I
think this error is more aesthetic than consequential.

Any suggestions?

23 Oct 2006 6:16 PM

Taytay

Chris DiPierro wrote:
Show quote

> Since migrating an application from .Net framework 1.1 to 2.0, I have an
> issue where when the app exits, I receive a popup error referring to the
> .Net-BroadcastEventWindow having an application error.
>
> Some searching through Google groups indicates that this is probably COM
> related. The app does in fact reference a legacy COM object (not ours to
> control) and if I don't access it, the error doesn't occur on exit.
> Unfortunately, that COM object is rather important, so I can't choose to
> not use it.
>
> Ultimately the app seems to work fine and without any errors relating to
> the COM object, and as mentioned, none of these issues existed in the
> 1.1 framework. At this point I'd just like to suppress the error if at
> all possible. Finding the cause is a good goal going forward, but I
> think this error is more aesthetic than consequential.
>
> Any suggestions?

23 Oct 2006 6:17 PM

Taytay

We're seeing the same thing in our .NET 2.0 app, although we've only
had one report so far. We're using the new WebBrowser control, which I
believe is a wrapper around the AxWebBrowser that used to cause this
error back in the .NET 1.1 days. If anyone has any suggestions, I'd
love to hear them.

Cheers,

Taylor

Chris DiPierro wrote:
Show quote

> Since migrating an application from .Net framework 1.1 to 2.0, I have an
> issue where when the app exits, I receive a popup error referring to the
> .Net-BroadcastEventWindow having an application error.
>
> Some searching through Google groups indicates that this is probably COM
> related. The app does in fact reference a legacy COM object (not ours to
> control) and if I don't access it, the error doesn't occur on exit.
> Unfortunately, that COM object is rather important, so I can't choose to
> not use it.
>
> Ultimately the app seems to work fine and without any errors relating to
> the COM object, and as mentioned, none of these issues existed in the
> 1.1 framework. At this point I'd just like to suppress the error if at
> all possible. Finding the cause is a good goal going forward, but I
> think this error is more aesthetic than consequential.
>
> Any suggestions?