Windows Arm64 translation is lagging. Please compile an windows arm64 installation package.

[Dash]

8cx gen3 running very slow.
As title.Thank you.

[OneCommander Support]

I never did anything for ARM but just saw that .NET 4.8.1 supports it although for that I would need to upgrade to VS2022 and renew subscriptions for a few libraries to support it. Even then I don't know if all the referenced libraries would work with it, and I don't have ARM device to test it with, so I am not sure where I would get to that.

What exactly is slow running it on ARM? Did you try both Software and Hardware rendering from Settings>Advanced (full program restart required inbetween) or turning off Acrylic/Mica effect in Settings>Themes

[Hernan Martinez]

I can help with testing. I have a Windows DevKit (the one with the Snapdragon 8cx gen3) and a Surface Laptop 7th gen (with a Snapdragon X Elite)
I'll start investigating if all the third libraries currently support ARM64.

But it's true. I thought that it was done in .NET 6 or 8. If Framework, than 4.8.1 is required.

What is the full list of third party libraries you use? Are there third party libraries beyond the ones in the About/Licenses dialogs?

Thank you,

Hernan

[OneCommander Support]

As long as it is Framework, it is fine. The About/Licenses dialog has list of all libraries, plus commercial library Jam Shell from https://www.jam-software.com/, but I didn't check with them yet about the support. In the worst case I can manually implement all that I am using from them if everything else was available. 

[OneCommander Support]

Hey, we there is a test build of ARM64 if you have time to check 
https://onecommander.com/OneCommander0.0.44.0.zip
It needs .NET10

On Sunday, July 14, 2024 at 7:00:52 PM UTC-4 hernan.c...@gmail.com wrote:

[Hernan Martinez]

It's not ARM64 

[OneCommander Support]

Thanks for checking. This looks like Process Explorer... I have an old SurfaceProX SQ1 at work and I'll check what's missing next week

[Hernan Martinez]

It's not just that. The .exe image is also an AMD64 image, not ARM64. Are you sure you just game the wrong build by mistake?

[OneCommander Support]

Thanks, that's helpful. I think you’re right that the .exe I posted is not an ARM64 apphost, so I may have packaged/published it differently than I intended.

My thinking was that the managed assemblies are AnyCPU, and with the ARM64 .NET 10 runtime installed Windows/.NET might run the managed code as ARM64. But I may be mixing that up with the native launcher: the .exe itself can still be an x64 apphost even if the main managed DLL is AnyCPU.

I wanted to suggest launching the onecommander.dll directly with the ARM64 dotnet runtime to skip wrong exe apphost, but I realized that I still had referenced 2 libraries without ARM support, so I will work on that first