Also, when I did manage to get the assembly definition that way by the technique I described in the first post:
The only thing that seemed to work was using > System.Reflection.Assembly.ReflectionOnlyLoad to load the assembly from its > AssemblyName (version + name), and using that FullName (which includes the > public key) to resolve the assembly using AssemblyResolver. However, this > doesn't work properly either, because then the modified assembly gets an > indirect dependency on a higher version of mscorlib, somehow. Also, this > seems like a really roundabout way to do this. I didn't try just reading the binary though. On Monday, July 27, 2015 at 5:40:29 PM UTC+3, Greg Rosenbaum wrote: > > Is there a way of reading the definition without having to go to the > assembly's location and reading the binary? > Like having Cecil resolve it using just a name and a version number? > The assembly is referenced in the assembly I'm modifying (It's just > System). > -- -- -- 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.
