Question

We have a couple of commercial .Net 2.0 applications that run just fine on Linux with Mono. For consistency across our product line, we've recently ported all of our projects to .Net 4.0. This introduces some problems under Mono, but nothing insurmountable, I'm sure.

When running our assemblies through MoMa, since porting to .Net 4.0, we see a large number of "MonoTodo" issues that I don't know how to interprete. Are these something I can safely ignore?

e.g., Our MoMa scan report gives:

    Calling Method      Method with [MonoTodo]          Reason
    bool MyMethod ()    bool Type.op_Equality (Type, Type)  Implement it properly once 4.0 impl details are known.

What does this reason actually mean? Presumably, the Equality operator does work well.

Était-ce utile?

La solution

Currently the MoMA definition files are unmaintained and do not reflect recent Mono state - I'm afraid you will have to check the class library source code to verify the TODOs yourself.

Or, if you are really using the version of Mono that MoMA compares against - yes, you will have some issues running on 4.0 profile.

Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow
scroll top