lhak

Is this supposed to work with the latest cswinrt preview release? I tried to access the IMemoryBufferByteAccess interface of a IMemoryBufferReference object, but a simple cast or calling reference.As() results...

@dongle-the-gadget Yes, I currently use code based on a helper class with the [WindowsRuntimeType] attribute and StrategyBasedComWrappers to not rely on the built-in com support. I also tried calling Marshal.QueryInterface()...

I tested it with the lastest available cswinrt and .net versions and still observe the same error message as in the bug description. I did not see any errors/warnings in...

I tried it again in my application and still see the reported error, even when updating to the newest packages. So this issue is apparently still not fixed.

@lukasf: Thanks for the updated project. I tested it and it works correctly. So I compared the project files to those of my application and found an issue: The .csproj...

It seems that the issue is caused by the WindowsRuntimeBuffer class (and related extension methods like AsBuffer() for arrays) when trimming is enabled. Workaround: Add a TrimmerRootDescriptor file with the...

I have attached a repro project here: [MrtCrashRepro.zip](https://github.com/microsoft/WindowsAppSDK/files/14308199/MrtCrashRepro.zip) Steps to reproduce the issue: -Build project as Release / x64 -Launch the resulting .exe with windbg

I have seen such issues when a packaged app includes a dll with third-party dependencies. In this case, all of these dependencies also have to be included in the package/output...

The resources.pri file (and all other native libraries) are actually embedded into the .exe file now and extracted to a temporary directory when you start the application. I checked your...