Re: Mono.Cecil dependency in monodocer

Miguel de Icaza wrote:
> Hello,
> 
>> Atsushi Eno wrote:
>>> I noticed that the latest monodocer depends on cecil (and the
>>> build is broken there). If we use it, I think -pkg:mono-cecil
>>> should be used in the makefile(.am).
>> Yes.  I was thinking some pending Cecil bugs would be fixed quickly, and
>> I was waiting for that to finish up those changes.  Turns out reading
>> custom attributes from an assembly is trickier than I realized.
> 
> Joshua mentioned today that he might want to backport to Reflection and
> use some 2.0 reflection APIs to get the attributes out.

So, I've reverted all of my Cecil changes.  This is a good opportunity
to use Cecil, so if Cecil makes it into a release, I think we should go
with it.

That leaves two questions.  The first is whether using gmcs will have
any build ramifications?  The 2.0 reflection API is the alternative in
order to get custom attributes (and generics) documented properly.

For anyone: If monodocer is compiled with gmcs, is it still able to load
assemblies compiled against the 1.0 corlib?  I don't have a grasp of how
assembly versioning works in .NET... (Yeah, I could try it.)

-- 
- Joshua Tauberer

http://taubz.for.net

"Unfortunately, we're having this discussion. It's too bad,
because guess who listens to the discussion: the enemy."
_______________________________________________
Mono-docs-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-docs-list