On Tue, Aug 14, 2007 at 10:56:51AM +0200, Jb Evain wrote: > > On 8/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > After I modify the Image, how can I store it again to assembly? > > That's currently not possible.
I think this would be useful. I started doing some thinking about what would be useful in a managed verifier, and this type of low-level binary checking seemed like a good place to start. Accordingly, I started making a list of cases to check, and test cases for each one - largely assemblies which violated some of the constraints in the file spec. However, there didn't seem to be a good way to write an outputter using Mono.Cecil.Binary which would let me write out the 'bad' assemblies. I'm not entirely sure of the best way to proceed - look for another tool to make the assemblies, or maintain a private fork of the Cecil code in which some of the key outputter classes are not declared sealed, and then derive an EvilAssemblyWriter from them? What do other people think? Thanks, Ben --~--~---------~--~----~------------~-------~--~----~ -- mono-cecil -~----------~----~----~----~------~----~------~--~---
