Problem with MessageBoxex that don't stay on the screen

[Roy Chastain]

I have a rather large fat client program that is being one touch deployed by clicking a link to the exe on a remote IIS server.
This client is doing .NET Remoting to a server that is hosted in the IIS that the client was just loaded from.

Problem is that MOST (NOT all) of the MessageBox.Show calls in the client do not work correctly on one or more systems.
All of them do not fail on any given system and the ones that fail on one system may or may not fail on the other systems. It
appears that any given call that fails on a system will always fail on that system. Some of the calls have never failed on any
system.

The failure is very simple, the MessageBox flashes up and disappears and the "Default Beep" sound occurs during this process.
Sometimes you only see a glimpse of the message and sometimes it is display long enough to actually see that it was there. (1/4
second would be the longest time.)

I have seen failures on both Win2K SP4 and XP SP1 both running framework v1.1

Any ideas?

Thanks

 

[Jerry Pisk]

Seems like some kind of a popup killer.

Jerry

I have a rather large fat client program that is being one touch deployed

by clicking a link to the exe on a remote IIS server.

This client is doing .NET Remoting to a server that is hosted in the IIS

that the client was just loaded from.

Problem is that MOST (NOT all) of the MessageBox.Show calls in the client

do not work correctly on one or more systems.

All of them do not fail on any given system and the ones that fail on one

system may or may not fail on the other systems. It

appears that any given call that fails on a system will always fail on

that system. Some of the calls have never failed on any

system.

The failure is very simple, the MessageBox flashes up and disappears and

the "Default Beep" sound occurs during this process.

Sometimes you only see a glimpse of the message and sometimes it is

display long enough to actually see that it was there. (1/4

 

[DNE]

You can try MsgBox method instead and see if you get different results.

Seems like some kind of a popup killer.

Jerry

I have a rather large fat client program that is being one touch

deployed
by clicking a link to the exe on a remote IIS server.

This client is doing .NET Remoting to a server that is hosted in the IIS

that the client was just loaded from.

Problem is that MOST (NOT all) of the MessageBox.Show calls in the

client
do not work correctly on one or more systems.

All of them do not fail on any given system and the ones that fail on

one
system may or may not fail on the other systems. It

appears that any given call that fails on a system will always fail on

that system. Some of the calls have never failed on any

system.

The failure is very simple, the MessageBox flashes up and disappears and

the "Default Beep" sound occurs during this process.

Sometimes you only see a glimpse of the message and sometimes it is

display long enough to actually see that it was there. (1/4

 

[Guest]

Behind the scenes MsgBox calls System.Windows.Forms.MessageBox.Show

But I don't know what causes Roy's problem, though

Regards, Jakob.

 

[Roy Chastain]

Well, the problem has been found, but it is not really explainable to me.

Much to my surprise it IS a pop-up stopper. I have Panic Ware installed on my system and I had the option "Close error dialogs
automatically" set. The explanation of this setting is that it "Automatically closes script and object error dialogs generated by
Internet Explorer when some pop-up windows are prevented". Clearing this makes things work.

Now, the reason(s) that I don't understand are
1) - I have the Panic Ware pop-up blocker disabled.
2) - This not a script error and should never have been seen by Panic Ware
3) - Application is running in IEExec not IE and again Panic Ware should not have had any visibility to it.

This brings up a couple of questions concerning the relationship of IE and IEExec. This implies that if something hooks into IE,
they are also hooked into IEExec. I don't really think this is a good idea. Granted Panic Ware is not a Microsoft product, but
Microsoft might want to look at how things hook and how IE and IEExec relate to each other.

Bottom line is this makes applications running in IEExec much less usable, when user has decided to try to stop the rest of the
trash on the internet.