Mono Cecil documentation and tutorials?

Eh, after a few hours of googling, I conclude that apparently Mono.Cecil officially lacks documentation... quoting an email response from the library author Jb Evain (in April 2008):

> 2) Is there a documentation for Cecil (other than source code)?

Nop. It has plenty of examples all over the place though.

That said, here are some more links and notes that might be useful:

the archives of the the official mono-cecil mailing list
some emails on the mailing list suggest learning from various open-source projects using Mono.Cecil (there's a listing of some on the mono-cecil mailing list's Google page)
as far as I understand from the terse FAQ you mentioned, there seem to be only six classes making the core of Mono.Cecil (as seen on a diagram), so it may be enough to just open the DLL in some Assembly Browser (like the Visual Studio's Object Browser) and watch. Quite many people seemed to praise the library for it's simplicity.
- On the other hand, one guy expressed his concerns (email from November 2008) that the library is not so simple.

And some other more or less useful snippets, articles and other tidbits of information:

a series of tutorial articles on Nauman Leghari's blog; note that they are based in IronPython, but that shouldn't be a big problem
article: "Static Method Interception in .NET with C# and Mono.Cecil"
library author's blog seems to have some examples & snippets as well
some more or less related articles on CodeProject
other usage sample
an email with usage example
one more example

By the way, should you have some positive experience with the library in future, it would be nice if you considered starting e.g. some wiki (maybe on a free wiki hosting server) about it so that the knowledge you gained could help other people avoid the very problem we're talking about here...

JbEvain has unfortunately turned down an offer by someone I know to add XML documentation to all of Cecil's types and members. :/

romkyns 2010-08-05 14:47:23

not exactly an easy way under those circumstances, but should he be really strong, there's always the option to branch and add the comments for the public benefit in spite of author's humors - and then there's a chance that the author would regain his reason after some time, seeing the work already done. That's the virtue of Open Source, that the product becomes a public good.

akavel 2010-08-11 07:51:57

ansaurus

tags:

views:

answers:

Mono Cecil documentation and tutorials?

related questions