Don't want to resurrect the dead, but I have just run into this issue again (and while browsing my own repo found the fix and link to this thread).
Is there nothing that we can do about it? We could make setting the SymbolReaderProvider automatically set the "ReadSymbols" to true, unless they have been manually set to false? Regards, Johannes On Mon, Dec 20, 2010 at 6:19 PM, Johannes Rudolph < [email protected]> wrote: > Backwards compatibility is a pain, always. > > The presence of a ReadSymbols (I implicitly included the "write side" here > too, forgot to mention) flag seems unintuitive then. How about removing this > flag and instead providing a DefaultSymbolReaderProvider that Cecil will > replace upon invoking? As far as I can see, this is the only Scenario where > the Flag is used. > > > On Mon, Dec 20, 2010 at 6:12 PM, Jb Evain <[email protected]> wrote: > >> On Mon, Dec 20, 2010 at 5:02 PM, Jb Evain <[email protected]> wrote: >> > That makes sense. >> >> It makes sense but it's annoying for all the code out there which >> assumes that setting the symbol reader (or writer) assumes that it >> means read (or write) the symbols. >> >> Jb >> >> -- >> -- >> mono-cecil > > > -- -- mono-cecil
