[
https://issues.apache.org/jira/browse/IGNITE-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998479#comment-15998479
]
Pavel Tupitsyn commented on IGNITE-5172:
----------------------------------------
* {{RegisterType}} fixed to use type name from current {{BinaryNameMapper}}
* As a result, multiple bugs in {{TypeNameParser}} and {{TypeResolver}} were
uncovered and fixed (simple names resolving, array handling)
TC is green, merged to master.
> .NET: Dynamic type registration uses assembly-qualified type name
> -----------------------------------------------------------------
>
> Key: IGNITE-5172
> URL: https://issues.apache.org/jira/browse/IGNITE-5172
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryProcessor.RegisterType}} uses {{AssemblyQualifiedName}}, which
> includes assembly version.
> This has two issues:
> * We ignore current name mapper, so this type name is not the same as type
> name in binary metadata, marshaller, etc
> * This breaks when same type comes from assemblies with different versions,
> which is a valid scenario. Binary protocol is flexible and does not care
> about type versions, it tolerates new or missing fields.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
