I get the same stack trace if I try it on the code produced by the pragma_directives_managed_unmanaged.cpp example from http://msdn.microsoft.com/en-us/library/0adb9zxe.aspx So, I guess writing mixed assemblies is broken in general.
On Dec 7, 11:12 am, "Larry S. Smith" <[email protected]> wrote: > On a two liner, ReadAssembly, then Write it dies with > > Unhandled Exception: System.ArgumentException: Value does not fall > within the expected range. > at Mono.Cecil.ModuleWriter.WriteModuleTo(ModuleDefinition module, > Stream stream, WriterParameters parameters) in D:\cecil\jbevain- > cecil-0.9.5-56-g5c32193\Mono.Cecil\AssemblyWriter.cs:line 87 > at Mono.Cecil.ModuleDefinition.Write(Stream stream, > WriterParameters parameters) in D:\cecil\jbevain-cecil-0.9.5-56- > g5c32193\Mono.Cecil\ModuleDefinition.cs:line 977 > at Mono.Cecil.ModuleDefinition.Write(String fileName, > WriterParameters parameters) in D:\cecil\jbevain-cecil-0.9.5-56- > g5c32193\Mono.Cecil\ModuleDefinition.cs:line 966 > at Mono.Cecil.AssemblyDefinition.Write(String fileName, > WriterParameters parameters) in D:\cecil\jbevain-cecil-0.9.5-56- > g5c32193\Mono.Cecil\AssemblyDefinition.cs:line 175 > at Mono.Cecil.AssemblyDefinition.Write(String fileName) in D:\cecil > \jbevain-cecil-0.9.5-56-g5c32193\Mono.Cecil\AssemblyDefinition.cs:line > 165 > at My.Hack.Main(String[] args) in D:\cecil\MyHack.cs:line 57 > > when writing back a C++ to managed wrapper. As I have both x86 and x64 > of that code, I tried it on both, and the stack trace is identical. > Unfortunately, I can't make this assembly public, but if writing mixed > assemblies is *supposed* to work instead of being a known limitation, > I'll try to reproduce it on a small example that I can make public. -- -- mono-cecil
