Hi! Yes, that's a know bug in the pdb symbol rewriting:
https://github.com/jbevain/cecil/issues/90 Jb On Tue, Dec 15, 2015 at 10:58 AM, Dominik Rauch <[email protected]> wrote: > Hi! > > The Visual Studio debugger (2013 and 2015) has problems with all our > Mono.Cecil-rewritten assemblies. > > Extension methods cannot be called in the debugger's watch window, i.e.: > > // fails after rewriting (works perfectly before rewriting) > // error: "myObj.ExtMethod() 'MyClass' does not contain a definition for > 'ExtMethod' and no extension method 'ExtMethod' accepting a first argument > of type 'MyClass' could be found (are you missing a using directive or an > assembly reference?) > myObj.ExtMethod() > > // always works > ExtClass.ExtMethod(myObj) > > Do you have any background information on this ? This is especially > unfortunate since VS2015 would now support lambda expressions and therefore > LINQ in the debugger. > > Best regards, > Dominik > > PS: We use the following code to null-op-rewrite the assembly: > var a = AssemblyDefinition.ReadAssembly (fileName, new ReaderParameters { > ReadSymbols = true }); > a.Write (fileName, new WriterParameters { WriteSymbols = true }); > > -- > -- > -- > 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.
