[Mono-dev] Class Status updates

[Miguel de Icaza]

Hello,

> One remaining problem is concerning Microsoft.VisualBasic.  Maybe this
> needs to be removed from $SECTIONS since the source is not in the mcs
> tree any longer.  The error message is at the end of this mail.

Lets remove it to fix the immediate problem (and since we can not
currently automate this, lacking a VB compiler).

But one issue that came up while talking to Jordi was that we would like
to also run status pages for other modules, in particular "olive", and I
would think that we would like to do the same for Visual Basic as well,
would this be something we could do?

For Visual Basic, I would say that it might be fine to just run it in
"semi-automatic" mode, that is to say, if the assembly is available on
the disk (the assembly built with the Microsoft VB compiler) it would
generate the compare information.