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. 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 is available both as part of Microsoft Visual Studio, or as an open source. It works better on, say, Linux, and works but the UI looks quite foreign on Mac. I was tasked to take a fresh approach and objective overview from a C. 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:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |