Morten Nielsen
Morten Nielsen
I'm seeing this on my high-dpi screens too. Looks pretty terrible.
Additional note: `\build\Microsoft.WindowsAppSDK.props` and `\build\Microsoft.WindowsAppSDK.targets` (as well as `buildTransitive\*`) needs to be moved to subfolders `net6.0-windows10.0.xxxxx` and `native`, so that the app sdk is only getting included into the project...
FYI Workaround: There is an ARM64 version of `genxbf.dll` in `\tools\arm64\` of the package and if I take that and copy it into the `x64` folder, the build does work....
Should be fixed in 1.1.4 according to release notes
I'm still seeing this in 1.1.4 with VS17.4.0preview1 on ARM64: 
@MSLukeWest I just set up a CI job on an ARM64 machine, and moving the referenced package to 1.1.4 did actually resolve it there. I'll go back and look at...
I'm hitting this over and over today as well with my maui app. This is a bit of showstopper as I keep not being able to build and run my...
Just in good order, I signed the CLA wrt to my parts of SharpMap, and allow all non-derived works in SharpMap that I built to be re-licensed under MIT (Just...
Yes by all means move the SharpMap stuff to MIT. I have no clue what I was thinking choosing LGPL back then 😬
I’d recommend for UI controls any property should be a get/set dependency property (and allow nulls for when data context isn’t available yet). That way you get mvvm support pretty...