Managed C++ Support
waschlappen
I am using mono-cecil to determine breaking API changes in managed
code (from one build to the next one), which works pretty well. In
fact, it works so efficient that I'd like to extend my usage of mono-
cecil to check managed c++ code (created with MS .NET) as well.
Unfortunately, I was not able to load these assemblies successfully
using mono-cecil.
My questions:
1. Is managed c++ supported?
If I am not mistaken mono does support managed c++ in general - at
least I remember having read such a statement somewhere on the mono
homepage. I am not so sure about mono-cecil, however. If it is
supported, I am probably doing something wrong. In that case I would
of course be interested in downtracking my misusage.
2. If managed c++ is not supported yet, are there any plans on the
roadmap to support it in future, and if so, what would be the expected
timeframe here?
Best regards,
waschlappen
Jb Evain
On Mon, May 31, 2010 at 10:32 AM, waschlappen <waschl...@gmx.de> wrote:
> Unfortunately, I was not able to load these assemblies successfully
> using mono-cecil.
Do you use Mono.Cecil 0.9.* from github?
If no, please try with it, if yes, please mail me the assembly that
Cecil fails to load.
> 1. Is managed c++ supported?
Kind of. You can browse all the managed side of the binary, but you
can't write it back, not can you examine the unmanaged part of the
binary.
> If I am not mistaken mono does support managed c++ in general - at
> least I remember having read such a statement somewhere on the mono
> homepage. I am not so sure about mono-cecil, however. If it is
> supported, I am probably doing something wrong. In that case I would
> of course be interested in downtracking my misusage.
Mono only supports mixed mode assemblies on Windows.
--
Jb Evain <j...@nurv.fr>
waschlappen
Thanks for the prompt answer!
> Do you use Mono.Cecil 0.9.* from github?
using 0.6. I will switch to latest version then.
> > 1. Is managed c++ supported?
>
> Kind of. You can browse all the managed side of the binary, but you
> can't write it back, not can you examine the unmanaged part of the
> binary.
binary as well? As pointed out earlier, I am only interested in the
API signatures.
But being able to check the managed part is a good step forward for
me. So you've already helped me a great deal here.
Kind regards,
waschlappen
Jb Evain
> Thanks for the prompt answer!
Sure!
>> Do you use Mono.Cecil 0.9.* from github?
> That's a good point. I just verified and it turns out that I am still
> using 0.6. I will switch to latest version then.
Let us know if you have any assembly that make Cecil crash.
> Do you have any idea how I could examine the unmanaged part of the
> binary as well? As pointed out earlier, I am only interested in the
> API signatures.
I never had to do that. A quick googling shows:
http://www.pelib.com/index.php
You want to look at the export directory of the PE file. But then you
probably just get a mangled name and you enter an interesting painful
world to get their signature by unmangling them.
> But being able to check the managed part is a good step forward for
> me. So you've already helped me a great deal here.
Cool!
--
Jb Evain <j...@nurv.fr>
Alois Kraus
I do also have problems with Mono.Cecil and managed C++. But so far did not have time to upgrade to 0.9. You might want to check out the ApiChange tool which is based on mono Cecil and hosted at CodePlex. Here is the release note:
http://geekswithblogs.net/akraus1/archive/2010/06/03/140207.aspx
Did you have any success with Cecil 0.9 yet?
Yours,
Alois Kraus
--
--
mono-cecil
Jb Evain
On Wed, Jul 21, 2010 at 10:29 PM, Alois Kraus
<kraus...@googlemail.com> wrote:
> I do also have problems with Mono.Cecil and managed C++.
Please report any assembly that Cecil 0.6 or 0.9 fails to read.
--
Jb Evain <j...@nurv.fr>