Jaiganėsh Kumaran
Jaiganėsh Kumaran
You could use [Avalonia UI](https://github.com/AvaloniaUI/Avalonia) for building a cross-platform .NET app. It has Fluent Design for a modern design.
@ChihweiLHBird Using System.IO will make it slower because UWP apps have limited access and you need to use StorageItems to get them. Instead we can use the native API: https://docs.microsoft.com/en-us/uwp/api/Windows.Storage.Compression?view=winrt-19041
@duke7553 It seems to not support by default but System.IO should be sufficient. Explorer has a private implementation which is not exposed to other apps.
The item type is pulled from Windows so it remains in your system language and we can't do anything about that.
It's an architecture issue. Some old Windows built-in apps are still compiled for ARM32, but that doesn't run on M1 as only 64-bit is supported. Maybe Parallels is emulating an...
@kanadgodse For safety, I would recommend that you disable app updates from the Store after installing it as it might auto-update to the ARM32 version later.
Instead of just maximized, there could be a snap point in which the sidebar is automatically opened and pinned.
@miloush .NET Native will be soon deprecated because it's incompatible with .NET 5
Instead of C#, you should migrate WinRT code to C++/WinRT. You'll get much better performance than C++/CX.
> FYI: "[UWP platform is now deprecated](https://winaero.com/microsoft-has-published-details-on-how-to-migrate-uwp-apps-to-windows-app-sdk/)". UWP isn't deprecated, latest .NET support and WinUI 3 is not available.