[Mono-dev] Understanding & Resolving MoMA Issue Messages
monoman at gmail.com
Thu Dec 3 06:54:41 EST 2009
Probably is a problem with MoMA's list of Mono APIs. Please report a
bug on MoMA.
Rafael "Monoman" Teixeira
"To be creative means to be in love with life. You can be creative
only if you love life enough that you want to enhance its beauty, you
want to bring a little more music to it, a little more poetry to it, a
little more dance to it."
On Thu, Dec 3, 2009 at 9:19 AM, RobVesse <rvesse at vdesign-studios.com> wrote:
> Hi all
> I'm looking into porting an existing .Net API I develop so that it will also
> work under Mono, I have a few third party libraries which I use which I'll
> need to change/drop from the Mono port but I'm having some problems solving
> one of the issues that the Mono Migration Analyzer is reporting on my own
> code. The message is as follows:
> Method missing from Mono - NameValueCollection HttpResponse.get_Headers ()
> So looking at the methods that are calling this it appears to just be the
> case that I've used code like the following:
> String accept = response.Headers["Accept"];
> Which I can replace fairly easily with:
> String accept = response.AcceptTypes;
> The issue is that even after I make this change in all the places where it
> occurs I still get the exact same issues reported by MoMA. Does this mean
> that internally the missing method still gets called and hence isn't
> portable to Mono?
> What partly confuses me is that as far as I can see from the documentation
> the method in question should be supported so I'm unsure why MoMA gives an
> error anyway?
> View this message in context: http://old.nabble.com/Understanding---Resolving-MoMA-Issue-Messages-tp26624389p26624389.html
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list