... who can't run half of their large-scale software with an ancient version of .NET on Arm.
reply... yet they still struggle to try and port their code to a newer .net version that does run on ARM. And do a bunch of other work tasks that can utilize this hardware.
reply(But, you bring up a great point, regardless!)
Here is a particularly irritating example. Cabinet Vision, some CAD type of software.
replyRequires ancient .NET. That actually is available for Arm though.
Required Jet DB driver 2010, which doesn’t exist on Arm, although it’s only needed for the installer.
Requires SQL Server embedded 2012 and 2016, which don’t exist on Arm at all. Yep, both versions.
Also required PowerShell version 2, which was deprecated in 2017, although they magically figured out how to fix that once Windows 10 was EOL’d and Win. 11 doesn’t support v2.
The vendor has zero plans to ever support this on Arm.
They will eventually get their lunch eaten by a new competitor who decides to just release a macOS version.
I try to avoid Microsoft products these days (modern dotnet is pretty nice though), but from my past experience, I believe every bit of this and have run into all of these with other software, including the requiring of multiple versions of MSSQL Embedded, which is just unholy.
replyNot really Microsoft’s fault, except that their exceptional backwards compatibility means vendors get away with requiring 16-year-old libraries.
reply