Replies: 3 comments 10 replies
-
It is documented in the release notes. |
Beta Was this translation helpful? Give feedback.
-
@NXY666 thanks for your report. As @DarranRowe mentions, the buffer overwrite issue was fixed in the Feb 27 release of Windows App SDK. Can you confirm what version of the Windows App Runtime (and consequently, MRM.dll) your app is loading? Another option is to provide us with a minimal repro project or a mindump. |
Beta Was this translation helpful? Give feedback.
-
@NXY666 yes, the second dump captures your crash, but doesn't include all dump information, as ".dump /ma ..." would. However, you can see from the dump that the error propagation begins with a call to the app's OnLaunched handler (typically in app.xaml.cs): And the error HRESULT is: I'd suggest debugging your OnLaunched handler, breaking on C# exceptions. Closing this issue as it does not appear to be a Windows App SDK error. |
Beta Was this translation helpful? Give feedback.
-
After upgrading from 1.5.240124002-experimental2 to 1.5.240205001-preview1, publishing an unpackage package using PublishSingleFile only generates a single .exe file (previously, many other files were also generated).
After the upgrade, I am unable to successfully open the published software (there is no problem when PublishSingleFile is removed). I tried using windbg to debug, but I don't understand it and don't know which information could be helpful.
Here are all the logs it outputted:
I'm not sure if this is a bug in the SDK or in my software.
Beta Was this translation helpful? Give feedback.
All reactions