Agreed. That's currently a limitation of the .mdb reader library we're using.
I'll check upstream if that's fixed. Jb On Fri, Nov 14, 2014 at 11:56 AM, Andriy Tylychko <[email protected]> wrote: > Hi, > > I'm reading assembly: > > AssemblyDefinition.ReadAssembly(path, new ReaderParameters > SymbolReaderProvider = new MdbReaderProvider() }); > > and checking if it contains some specific attribute. If not I need to > override it (not modify, just override with a backup copy). I cannot because > `MdbReader` still keeps .dll.mdb file open and I don't see any way to > dispose it. Checking sources I found the only place where > `MdbReader.Dispose()` is called is on module writing. So the only solution > is to write assembly back w/o any modification which can take ~10 secs so is > not cool. > > Did I miss something? > > In general, it would be better to read all symbols to memory on module > reading and close symbol file immediately. > > Cecil v.0.9.5 > > Cheers, > Andriy > > -- > -- > -- > mono-cecil > --- > You received this message because you are subscribed to the Google Groups > "mono-cecil" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
