May make SerializationContext.GetTypeBinding() and GetTypeAlias() virtual

[GoogleCodeExporter]

There may be exceptional scenarios in which deserialized types are lazily
resolved or created on the fly (by using dynamic assemblies, for example).
Here, the type mapping offered by SerializationContext may not be sufficient. 

Making GetTypeBinding() virtual could provide a bit more flexibility.

Probably GetTypeAlias() should be virtual, too. 

Alternatively, SerializationContext could be transformed into an interface
to separate the interface required by the serializer and the actual
implementation.

...armin.

Original issue reported on code.google.com by paramatrix@gmail.com on 11 Aug 2008 at 1:34

[GoogleCodeExporter]

The aliasing code has been split off into its own class called 
TypeAliasCollection.  GetTypeAlias and GetTypeBinding are virtual and you can 
set the TypeAliases property 
on the SerializationContext to an overriden TypeAliasCollection class.

Original comment by elliott....@gmail.com on 26 Jan 2009 at 1:05

• Changed state: Coded
• Added labels: Milestone-Release3.0, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

3.0 Release

Original comment by elliott....@gmail.com on 26 Jan 2009 at 2:22

• Changed state: Verified