Debugging (Windows)
Elements comes with integrated support for debugging for native Windows apps, either locally on your Windows PC or remotely from your Mac via CrossBox, using its own "Island" debug engine.
In Water, "Windows PC" will automatically be selected as the default run destination in the CrossBox device picker, and then same in [Visual Studio](/Visual Studio). In Fire, you must select (or newly connect to) a remote Mac, first.
Once done, simply select "Run" ("Start" in Visual Studio), or press ⌘R (Fire) or Ctrl+R (Water) or F5 (Visual Studio) to run your app. When debugging via CrossBox, your app[ will first be transfered to or updated on the remote Windows PC or VM (parts may already be there from the build), before it launches.
Architectures
By default Windows apps build for the architecture of your local Windows installation – x86_64 in most modern cases, but potentially i386 on older systems, or arm64 when working on a Windows/ARM device – so that they will run natively.
Depending on your hardware type, you can optionally also debug different architectures of your project in the Windows on Windows translation layer, by setting a different Architecture in Project Settings (If you enable more than one architecture, the debugger will run the one most appropriate).
- Windows/x86_64 can run x86_64 and i386 binaries
- Windows/ARM46 can run arm64, x86_64 and i386 binaries
- Windows/i386 can run onoy i386 binaries