exe and wrap it in a Wine environment that you can copy to other Macs, and I don't think the other Macs have to have Wine installed I think the Wineskin wrapper contains all the necessary Wine files. There's a software package for macOS called Wineskin that lets you take an arbitrary Windows. Wine tries to provide an environment where Windows apps can run under Linux or macOS, including tons of libraries implementing Windows APIs which do not exist on Linux or macOS. exe in macOS without a VM, you would need Wine. They call functions that are specific to Windows and often have no direct macOS equivalent. You can also develop standad Mac OS X installation packages.īut with such UI, you will need to do a big part of development with real Mac OS X system.Windows. If you want to follow authentic Mac's UI rules, you will need additional project which is installed on top on Mono and - attention! - replaced Mono's runtime command line: It works better on, say, Linux, and works but the UI looks quite foreign on Mac. With Mono, you can develop applications on Windows and run on Mono (Windows or other platforms) without re-compliation. The product common for Windows and Mac is Mono, an alternative CLR implementation: NET FCL, BCL + some non-standard libraries, with some limitations.

NET applications on many platforms, for the applications limited to some standard subset of. On Mac OS X, and other *NIX (Unix-like) systems, an executable file can have any file name, '.exe' or not. The function of a file is defined by its content, not name. If you change file name ('.exe' is nothing but a file name), the Window shell wont recognize it, but you still can start the application programmatically. It used to be a notion of obsolete Microsoft systems, but now this is mostly just a convention. Essentially, there is no such thing as 'extension'.

The paragraph below (indented) was initially written in response to first version of the question, which was later fixed by the inquirer:

Run .exe file mac