Issue when running published ARM64 app and setting RenderOptions

[NickeManarin]

Hi, I published my app as ARM64 but users are getting an error when running it.
Setting RenderOptions triggers a BadImageException:

An attempt was made to load a program with an incorrect format. (0x8007000B)
System.BadImageFormatException
 at MS.Win32.PresentationCore.UnsafeNativeMethods.MilCoreApi.RenderOptions_ForceSoftwareRenderingModeForProcess(Boolean fForce)
 at System.Windows.Media.RenderOptions.set_ProcessRenderMode(RenderMode value)
 at Myapp.App.App_Startup(Object sender, StartupEventArgs e) in App.xaml.cs:line 156
 at System.Windows.Application.OnStartup(StartupEventArgs e)
 at System.Windows.Application.<.ctor>b__1_0(Object unused)
 at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
 at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Here are the publishing settings:

---

The line that triggers the issue looks like this:

RenderOptions.ProcessRenderMode = UserSettings.All.DisableHardwareAcceleration ? RenderMode.SoftwareOnly : RenderMode.Default;

The project that UserSettings comes from (Util) is getting published as ARM64 as expected and the only Nuget package (System.Drawing.Common) is as well ARM64.

But I noticed that several DLLs are x86 instead of ARM64, this includes the app's main DLL (NameOfTheApp.dll), System.dll, System.Drawing.dll and others.

What's causing the crash? How can I debug this?

[lindexi]

@NickeManarin Could you see #5747 ?

How can I debug this?

Enable the native code debugging in VisualStudio.

[NickeManarin]

Thank you. I'll take a look at that PR.
I don't have access to an arm64 machine now, is there any way to know (client side) which part is causing the issue?
Can nuget packages cause this issue? I'm using SharpDX as well.

[NickeManarin]

So, this was fixed in newer versions of .NET.