AsmResolver VS sambal

However, according to Washi1337, author of AsmResolver (an open source project similar to DnLib), the NativeWrite method tries to preserve the structure of the native code so that the assembly size cannot be reduced. Instead, it may even increase the size of the assembly (see https://github.com/Washi1337/AsmResolver/issues/267). And in the actual use, I found that after modifying these assemblies, the program would fail to start. Checking the Windows event log, I found that it was caused by CLR startup failure. According to Washi1337, if only the native code in the assembly contains ReadyToRun, we can simply remove the ILLibrary flag from the assembly. After all, the optimized assembly still preserves the original IL code. However, after I did what Washi1337 said, the program still failed to start. It is not clear why, because the assembly containing native code can not be tailored well, so I did not go into further research, welcome friends who are proficient in CLR to share experience.

It supports 4 commands, and then generate a small Windows EXE .The The commands are to sdisplay ddfiidfferent types of message box. Huh? Sounds odd. But it is my very simple compiler written in C# (can be written in any other lang. Just that the some sections of the EXE are hard-coded. Please feel free to look at : https://github.com/fm05/sambal and please give comments. Thank you.