![]() ![]() However, your understanding of the problem is not correct.Ī WPF app based on standard "WPF App(.NET Framework)" template.Īdd a button and double click toe write a click handler as follows: using System I don't have any older W10 machines available for test. Dialog popped up with "WpfApp1 has stopped working"Īltogether this leads be to think in the direction of either a common setting for Windows 10 or a Windows Update of Windows 10 (recent?). Windows 10 1803, Visual Studio 2017, fx 4.6.1ġ I tried the same app on the same machine, but another user, same problem.Ģ I tried the same app on two other computers running the same OS (and version), same problem.ģ I tried the same app on two other computers running Windows Server 2016 (KB4457131 and KB4091664 installed) and Windows 7. ![]() Is this really the expected behavior? If yes, why so? I find it strange or embarrassing that I have not observed this earlier. I do observe that it takes some time which is to generate the crashdump, but I didn't expect that the user simply is not notified However, running the exe without the debugger (debug or release compile doesn't matter) the app is simply stopping without any notice. When debugging (with default exception settings) the exception helper window is shown as expected. Made the simplest of WPF apps, just a button which, when clicked throw an exception. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |