Let's talk about how to use mono.

Let's talk about how to use mono.

Warensoft Training Center of the Chinese Emy of Sciences computing Institute

At noon today, I received an email about a previously written mono article. I have explained this and hope to share it with my friends who have the same questions. The mail content is as follows:

I found an article about mono using mono in windows on the Internet. I would like to ask, the winform program developed in windows, what is the difference between it and programs developed using Visual Studio? Is it just to improve the running speed without using JIT? Furthermore, why is mono development required on Windows? Can mono programs developed on Windows be directly transplanted to other platforms? I still have a question. On this website, I used the mono platform for Linux. Which one should I click and which download should I choose? I am sorry, I look forward to your answer.

Based on the above questions, I want to explain the following. net and Java frameworks are understood as the same. The code we write is in the upper-Layer Code, even if it is compiled, it is not the machine code, Ms is proposing. net, it is said that it can be cross-platform like Java. The principle of cross-platform is that we can use different JIT on different platforms to interpret the upper-layer languages we have compiled as the corresponding machine language, the problem is that the current "JIT" is a Ms product, which aims to translate the upper-layer language we wrote into a machine language that Windows can recognize, in addition, Ms does not provide "JIT" for other platforms. In fact, Mono is a third-party developed "JIT ", of course, in addition to interpreting the upper-Layer Code as a Linux machine language, Mono can also interpret it as a Windows machine language. Therefore, Mono and JIT are at the same level, but what mono explains is that on Windows platforms, Ms JIT is not good, and the speed is slow, in addition, there are fewer functions (WPF cannot be explained, most of the WCF cannot be explained, and some functions cannot be explained in winform ). In principle, the EXE is irrelevant to the dotnetframe in which you use mono or Ms. Therefore, you can use vs to write a program, compile the EXE, and run the program using mono, however, the problem is that vs uses Ms JIT to explain the program, so it is likely that it is beyond the scope of Mono's interpretation during development. How can we ensure that the vs program is not beyond the scope that mono can explain? Mono's official website provides a compatibility testing tool, but this tool is not free of charge. Mono has the following advantages: 1. cross-platform. some core DLL files during mono running can be directly packaged in the installation package without installing the entire framework. compared with netframework, netframework has a great advantage in packaging and compressing necessary DLL files during mono runtime, which is more than 10 MB. more than 40 m for net4.0, And now many projects have been developed using mono. I am a 3D game, the current unity3d engine is the kernel written by mono. To ensure Windows and Linux compatibility, you can write programs in monodevelop in windows. We recommend that you do not use winform for development, because winform is based on Win32 technology, its compatibility is not very good in Linux, and there is no winform designer in Mono develop (Mono IDE), which is a headache, in mono, we recommend that you use GTK # as a third-party form Technology for UI. In monodevelop, you can select Mono or. NET Framework. You can select mono. However, if you are developing in Linux, you can use monodevelop in Linux. As for mono installation in SuSE, I just installed mono when it first came out, and now I have forgotten it, so you need to study it by yourself, I hope my explanation will be helpful to you!