You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2018/10/17 10:21:00 UTC
[jira] [Updated] (IGNITE-9877) .NET: LINQ does not work under .NET
Core 2.1 - AmbiguousMatchException
[ https://issues.apache.org/jira/browse/IGNITE-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-9877:
-----------------------------------
Summary: .NET: LINQ does not work under .NET Core 2.1 - AmbiguousMatchException (was: .NET: AmbiguousMatchException under .NET Core 2.1)
> .NET: LINQ does not work under .NET Core 2.1 - AmbiguousMatchException
> ----------------------------------------------------------------------
>
> Key: IGNITE-9877
> URL: https://issues.apache.org/jira/browse/IGNITE-9877
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Labels: .NET
> Fix For: 2.8
>
>
> One of the string methods is causing an exception:
> {code}
> Unhandled Exception: System.TypeInitializationException: The type initializer for 'Apache.Ignite.Linq.Impl.MethodVisitor' threw an exception. ---> System.Reflection.AmbiguousMatchException: Ambiguous match found.
> at System.RuntimeType.GetMethodImplCommon(String name, Int32 genericParameterCount, BindingFlags bindingAttr, Binder binder, CallingConventions callConv, Type[] types, ParameterModifier[] modifiers)
> at System.RuntimeType.GetMethodImpl(String name, BindingFlags bindingAttr, Binder binder, CallingConventions callConv, Type[] types, ParameterModifier[] modifiers)
> at System.Type.GetMethod(String name, BindingFlags bindingAttr)
> at Apache.Ignite.Linq.Impl.MethodVisitor.GetMethod(Type type, String name, Type[] argTypes, VisitMethodDelegate del)
> at Apache.Ignite.Linq.Impl.MethodVisitor.GetStringMethod(String name, Type[] argTypes, VisitMethodDelegate del)
> at Apache.Ignite.Linq.Impl.MethodVisitor..cctor()
> {code}
> We should clarify the signature of all string methods to avoid this in future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)