This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 72%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAY%3C/text%3E%3C/svg%3E)
In my application, I have a MainWindow that inherits from System.Windows.Window. Within this MainWindow, there's a System.Windows.Controls.Button. Clicking this button triggers the opening of a second window, also inheriting from System.Windows.Window. To display this second window, I utilize the ShowDialog method from the System.Windows.Window class.
However, during debugging (F5), if I click the button to open the second window and then click outside the second window, it loses focus. Interestingly, when running the program without debugging (Ctrl+F5), this issue doesn't occur. In this case, the second window behaves as a modal window, maintaining focus even when clicked outside.
I've already ensured that the second window is set to have the MainWindow as its owner. Despite this, the issue persists. Any suggestions on resolving this discrepancy in behavior would be appreciated.
I have included a link to the project on GitHub for reference.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello @Asya Yesayan ,
Thank you for taking time to post this issue in Microsoft Q&A forum.
Please kindly try the suggestion shared by Viorel.
I would also suggest you submit a ticket here: Developer Community - Visual Studio.
Thank you for your response, it resolved my issue. However, I'm curious to understand why disabling the 'XAML Hot Reload' feature fixed the problem. Could you please provide an explanation?
Report a concern
Hello @Asya Yesayan ,
There are still some limitations on the XAML Hot Reload feature.
The issue you found is, probably, a potential impact. That’s why I suggested you try to report this issue on our Developer Community. You can directly contact VS product team there and it’s helpful to improve the limitations and the features of the XAML Hot Reload.
But for your scenario, it’s obvious that disabling the XAML Hot Reload feature "fixes" this issue.
If you do submit a ticket on our Developer Community, please kindly share the ticket link here for better tracking.
Happy coding!
To work around the discrepancy, try to disable the “XAML Hot Reload” feature in Options dialog (“Debugging” area).
Thank you for your response, it resolved my issue. However, I'm curious to understand why disabling the 'XAML Hot Reload' feature fixed the problem. Could you please provide an explanation?