Dialog Text Missing .Net apps (VB.NET)

Topic

New Reply

Hi

I have somehow managed to have the text in any dialog box (messagebox) not show. I suspect it has something to do with the text forecolour being the same as the background? But I don’t have any idea how I managed to change this.

It is only in .NET that I have the problem, VB6 and other apps show dialog boxes with black text (making it visible). Other computers run the same .NET apps and show the correct colours.

Suggestions appreciated.

Reply | Quote

Replies

Hi Jayden,

I don’t know if your problem is related to this or not, but I discovered some strange behavior when using the MessageBoxOptions argument of the Messagebox.Show() method. I usually use the overload without this argument. However, it’s possible that the problem is caused because of the WindowsXP theme or application color defaults. So try it both ways – with and without the argument.

See the MSDN for details on this argument.

Hope this helps!

Reply | Quote

Hi Jayden,

I don’t know if your problem is related to this or not, but I discovered some strange behavior when using the MessageBoxOptions argument of the Messagebox.Show() method. I usually use the overload without this argument. However, it’s possible that the problem is caused because of the WindowsXP theme or application color defaults. So try it both ways – with and without the argument.

See the MSDN for details on this argument.

Hope this helps!

Reply | Quote

Hi

Thanks mark . You have added another piece to the puzzle, hopefully getting us closer to a resolution….

I tried messagebox.show with the option of MessageBoxOptions.DefaultDesktopOnly and this displays the text.

However, i don’t want to have to convert all my current applications to using this .. also, I get dialogs from the .NET framework with missing text still (they are not obviously using this option). Clicking these at random is a bit risky (I did a SP upgrade for the .net framework and got a dialog box with no text…so had to just guess what to click … it was asking if I wanted to restart my computer).

There must be something somewhere where a settings has been upset?

J

Reply | Quote

Hi

Thanks mark . You have added another piece to the puzzle, hopefully getting us closer to a resolution….

I tried messagebox.show with the option of MessageBoxOptions.DefaultDesktopOnly and this displays the text.

However, i don’t want to have to convert all my current applications to using this .. also, I get dialogs from the .NET framework with missing text still (they are not obviously using this option). Clicking these at random is a bit risky (I did a SP upgrade for the .net framework and got a dialog box with no text…so had to just guess what to click … it was asking if I wanted to restart my computer).

There must be something somewhere where a settings has been upset?

J

Reply | Quote

It looks like it is the upgrade to McAffee VirusScan Enterprise 8 that has caused this problem! We are now experiencing it through-out the company on those PCs that have been upgraded to the newest version of VirusScan.

We will continue testing and post any more info here, including the fix if we find one.

Regards

Reply | Quote

Okay, the problem was definitely McAffee VirusScan Enteprise V8 upgrade….

It appears that the “Buffer Overflow Protection” that is enabled causes this problem.

The resolution is to disable McAffee Buffer Overflow Protection in the McAffee console window … and viola, the problem is resolved!

So…my next question…why would McAffee be picking up the Show method of the MessageBox class as being a problem with Buffer Overflow? The interesting point is the overloaded method using the MessageBoxOptions argument is NOT picked up as violating this?

Seems strange to me…

Anyway, thanks for your help Mark.

Reply | Quote

I’m glad you found the solution.

I don’t think the problem lies with McAffee disrupting the .NET Framework. I think it goes a step lower than that – the Windows API. I’ll bet McAffee has some kind of hooks into the API that affect the same method that is called by the .NET framework for MessageBox.Show()

Reply | Quote

I’m glad you found the solution.

I don’t think the problem lies with McAffee disrupting the .NET Framework. I think it goes a step lower than that – the Windows API. I’ll bet McAffee has some kind of hooks into the API that affect the same method that is called by the .NET framework for MessageBox.Show()

Reply | Quote

Okay, the problem was definitely McAffee VirusScan Enteprise V8 upgrade….

It appears that the “Buffer Overflow Protection” that is enabled causes this problem.

The resolution is to disable McAffee Buffer Overflow Protection in the McAffee console window … and viola, the problem is resolved!

So…my next question…why would McAffee be picking up the Show method of the MessageBox class as being a problem with Buffer Overflow? The interesting point is the overloaded method using the MessageBoxOptions argument is NOT picked up as violating this?

Seems strange to me…

Anyway, thanks for your help Mark.

Reply | Quote

It looks like it is the upgrade to McAffee VirusScan Enterprise 8 that has caused this problem! We are now experiencing it through-out the company on those PCs that have been upgraded to the newest version of VirusScan.

We will continue testing and post any more info here, including the fix if we find one.

Regards

Reply | Quote