>-----Original Message-----
>Hi there! After debugging the disassembling of a CLI-
specification
>compliant I'd built manually using the SSCLI version of
ILDASM, I
>found that the latter expects some metadata tables (I've
found the
>MethodSemantics & CustomAttribute ones so far) to be
ordered by a
>given criteria. Basically, I realized that the code does
a binary
>search on these tables.
>Sadly, my entries were not ordered (given that the ECMA
specification
>makes no assumption on this matter) but ILDASM (the one
shipped with
>the commercial version of the framework and the SSCLI
one) failed to
>find many of the custom attributes' parents when
disassembling my
>code. Clearly, it is failing to find the corresponding
entries in the
>CustomAttribute table. Using Remotesoft's NET Explorer,
Reflector or
>Asmex works flawlessly.
>Anyone from Microsoft listening?
>
>cheers,
>Alan
>.