Morten Nielsen

@DenKn Generally I'm not planning on adding geometric operations and calculations to the library. The reason being there's no way for me to exactly match the results of the official...

Also see the changes I made in these two PRs in our fork: - https://github.com/Esri/gdal/pull/2 - https://github.com/Esri/gdal/pull/4 They're not a full UWP implementation, but just ensures the bits of GDAL...

So the good news is since this was logged a LOT of apis have been white listed and if I'm not mistaken there's only one call left that isn't allowed...

@riverar I didn't see any difference in 16.10p1. Upgraded to preview 2, and that version won't even load (or create) the packaging project (likely because I got net6 installed). 

Even so, while the error you got is better, I still dont think its super helpful. Also interesting that the error in your screenshot has a different hresult value -...

Thanks @huichen123. > for the C++ exception, if you hit f5, you will see the nicer System.Runtime.InteropServices.COMException This does seem a bit counter-intuitive that you have to continue on an...

> However, it's not the primary message, and I am not sure how useful that will be. Generally the goal of this issue was to point out a poor message...

Line of code where it's being thrown for reference: https://github.com/microsoft/ProjectReunion/blob/1714557cad5e740c0153e451fbf0311c8e5bdfc1/dev/MRTCore/mrt/Microsoft.ApplicationModel.Resources/src/ResourceCandidate.cpp#L55 This error isn't thrown deep down where some resource candidate is being looked up. It's thrown right on the property...

> The easiest "improvement" is to disable native debugging. That Thanks. This is rather ironic actually, as generally I get better error information that can actually inspect with this turned...

Does this also mean we need to handle it and update the rectangles when dragging a window across two monitors with different DPI? (and how would that affect the drag,...