We are running a slightly old version of cecil but just calling ReadSymbols results every time with a Null Reference Exception.
12:10:15.073 - AutoTest.Minimizer.Extensions.BackGroundProcessException: background error occurred ---> System.NullReferenceException: Object reference not set to an instance of an object. at Mono.Cecil.ModuleDefinition.ReadSymbols() at AutoTest.Minimizer.TestMinimizer.BuildFullMap(BuildFullMapParams buildFullMapParams) at AutoTest.Minimizer.TestMinimizer.BuildFullMap(String filename) at AutoTest.Minimizer.Extensions.EnumerableExtensions.<>c__DisplayClass5`2.<ForkAndJoinTo>b__0(Object x) --- End of inner exception stack trace --- at AutoTest.Minimizer.Extensions.EnumerableExtensions.ForkAndJoinTo[T,TVReturn](IEnumerable`1 input, Int32 count, Func`2 func) at AutoTest.Minimizer.TestMinimizer.DoInitialIndexOf(List`1 assemblies) at AutoTest.VM.MinimizingPreProcessor.Initialize() On Thu, Aug 4, 2011 at 11:00 AM, Jb Evain <[email protected]> wrote: > On Thu, Aug 4, 2011 at 4:58 PM, Greg Young <[email protected]> wrote: >> Wouldn't that be a bit expensive since it returns AssemblyDefinitions >> (eg to create an assembly definition just to create another >> assemblydefinition?). Seems like its a forced copy/paste job as I cant >> override anything in the default as well no? > > I think I misunderstood your first question. No, using > ReaderParameters and resolvers are not the only way to read symbols. > > If you have an existing module, you can simply say: > > module.ReadSymbols () > > or: > > module.ReadSymbols (provider); > > Jb > > -- > -- > mono-cecil -- Le doute n'est pas une condition agréable, mais la certitude est absurde. -- -- mono-cecil
