monkey at jpobst.com
Sun Oct 21 20:50:23 UTC 2012
The tool to generate the definition files is in github:
You will need to update AssemblyManager.cs to point to both the .NET and
Mono assemblies. You might also want to update to .NET 4.5.
After that, you put them in a zip file with a little bit of metadata and
they're ready. (See existing definition packs.)
I am guessing if you put them somewhere for Xamarin, they can upload
them to the definition update web service.
On 10/21/2012 3:40 PM, Leszek Ciesielski wrote:
> MoMA is indeed a very useful tool and it's a pity that it seems no
> longer to be supported. What would it take to update the masterinfos
> that it uses for reporting? They're missing for the last couple of
> release (about two years, I would say?). A lot of people start their
> migration/multiplatform work with MoMA and currently it under-reports
> Mono capabilities significantly.
> I understand that Xamarin no longer has the commercial interest in
> maintaining this tool, but it's valuable to the community, so perhaps
> it should transition to being maintained by community members? As it
> stands, MoMA relies on a webservice that is no longer updated and I'm
> guessing the report uploads aren't analysed as well?
> Kind regards,
> Leszek Ciesielski
> On Mon, Oct 8, 2012 at 3:29 PM, David Schmitt <david at dasz.at> wrote:
>> could someone please remove or update the wikipage at
>> http://www.mono-project.com/MoMA ? the download there only can check against
>> 2.8 and "File MoMA bugs" still links to the novell bugzilla.
>> Thanks && love, David
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list