WPF SplashScreen closes MessageBox - by triejan

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


14
0
Sign in
to vote
ID 381980 Comments
Status Closed Workarounds
Type Bug Repros 12
Opened 11/14/2008 7:06:01 AM
Access Restriction Public

Description

The System.Windows.SplashScreen appears to close message boxes that are displayed.  I do a lot of initialization behind the splash screen, and use messages boxes to indicate errors.  Because of this behavior, the user gets no opportunity to read the errors.
Sign in to post a comment.
Posted by XHEO INC on 8/9/2011 at 6:04 PM
This is not isolated to MessageBoxes. It applies to any window that uses the ShowDialog method.
Posted by kevin17 on 4/22/2010 at 4:39 PM
I am seeing something similar issue with MessageBox and WPF window. Closing the WPF window closes the MessageBox too. Can you please give me the details in code (C#) for the workaround. Thanks,
Posted by Microsoft on 2/4/2009 at 2:59 PM
This will happen if you display a MessageBox and don't explicitly set the parent. The window will implicitly parent itself off whatever window is currently active (in this case, the splash screen). In the Win32 world if you close a window then all child windows will also be closed. If you explicitly set the MessageBox's parent to another window then you'll be fine.

This issue was discussed quite a bit, but the resolution was that we don't want to special case MessageBox to be aware of the SplashScreen class. The current behavior isn't ideal, but it's a specific symptom of a more general thing that we wouldn't fully solve.
Posted by Microsoft on 11/18/2008 at 1:39 AM
We were able to reproduce the issue you are seeing. We are escalating this issue to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release
Posted by Microsoft on 11/17/2008 at 2:16 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)