Mono Migration Analyzer (MoMA)
I think everyone heard about the Mono project - the performing language environment of the .NET family of languages. Mono is not a complete equivalent of the Microsoft .NET Framework, but it allows you to run many .NET applications without recompiling. Those who wish can read about Mono here: ( The official site of the project ) The topic is not about the Mono environment itself, but about a small tool - Mono Migration Analyzer . MoMa is a small tool that analyzes .NET assemblies (exe, dll) for compatibility with the Mono environment. For me personally, the tool came in handy when porting builds to Linux.
MoMa analyzes the assembly (s) for the presence of unsupported calls and code sections. Although according to the statement of Novell Moma itself is not a panacea for all incompatibilities, that is, there may be situations where MoMa may not detect incompatible code. It is also worth noting another interesting feature - after analyzing the assembly, the utility will forgive send a report to the design team “to identify and focus on the most required functionality” (() Mono Team). Conclusion: you shouldn’t rely on MoMa as the main compatibility testing tool - you can fully test it only by testing the assembly on the target platform, but as a tool at the initial stage of assembly migration - definitely Must Have!
PS: By the way, here is a tutorial on porting non-trivial WinForms applications under Mono using Mono Migration Analyzer. And another thing: in the picture, an analysis report about my build, which successfully works under openSuse 11 and mono 2.0 - that is, MoMA did not miss anything.
MoMa analyzes the assembly (s) for the presence of unsupported calls and code sections. Although according to the statement of Novell Moma itself is not a panacea for all incompatibilities, that is, there may be situations where MoMa may not detect incompatible code. It is also worth noting another interesting feature - after analyzing the assembly, the utility will forgive send a report to the design team “to identify and focus on the most required functionality” (() Mono Team). Conclusion: you shouldn’t rely on MoMa as the main compatibility testing tool - you can fully test it only by testing the assembly on the target platform, but as a tool at the initial stage of assembly migration - definitely Must Have!
PS: By the way, here is a tutorial on porting non-trivial WinForms applications under Mono using Mono Migration Analyzer. And another thing: in the picture, an analysis report about my build, which successfully works under openSuse 11 and mono 2.0 - that is, MoMA did not miss anything.
')
Source: https://habr.com/ru/post/48027/
All Articles