[Mono-dev] missing method warning on 1.1.15

[Zoltan Varga]

Probably due t the turning on of inlining.

             Zoltan

On 5/9/06, Carlos Solorzano <carlos at applianz.com> wrote:
> Ok thats easy enough! some reflection never hurt anyone!
>
> Any idea why it quit working when moving to .15?
>
> Zoltan Varga wrote:
> >                                            Hi,
> >
> > The proper way to do this is to dynamically lookup and invoke the
> > method, i.e:
> >
> > if (windows) {
> >    MethodInfo mi = typeof (FOO).getMethod ("BAR");
> >    mi.Invoke (....);
> > }
> >
> > The MethodInfo could be cached somewhere of course to speed this up.
> >
> >            Zoltan
> >
> > On 5/9/06, Carlos Solorzano <carlos at applianz.com> wrote:
> >> I use some libraries on my code that on windows those libraries have
> >> more methods than on linux, so typically I do a
> >>
> >> if (windows) callThatMethod();
> >>
> >> This has been working perfectly fine without having to compile my code
> >> just for mono. Today I upgraded to 1.1.15 from .13 and all of the sudden
> >> I am getting errors around those methods which are not present on mono.
> >> Any ideas what has changed?
> >>
> >>  WARNING **: TypeRef ResolutionScope not yet handled (9)
> >>
> >>  WARNING **: Missing method .ctor in assembly
> >>
> >> This code was working fine and its working fine when I roll back to .13
> >> and .10.1
> >>
> >> --Carlos
> >>
> >>
> >> _______________________________________________
> >> Mono-devel-list mailing list
> >> Mono-devel-list at lists.ximian.com
> >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>
> >
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>