On Fri May 16 11:13:37 2025 +0000, Rémi Bernon wrote:
Fwiw, not a big issue that early but I gave monodis a try, and it expects a GUID entry first and asserts when missing, then some "#~" data, and segfaults when missing. I'm not sure that should determine the order of priority we should output these sections, but is the current code supposed to work, in some minimal way, with another tool?
Streams are written in the same order as midlrt writes them. I don't know of any ordering requirement for WinRT metadata files but perhaps .NET assemblies do require a certain order? The streams are essentially empty now. In followup patches the table stream (#~) will be added and the other streams will be filled too.