-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Document how to add a custom TypeConverter for AxHost.State serialization #8296
Copy link
Copy link
Open
Labels
📚 documentationOpen issue here - https://github.com/dotnet/dotnet-api-docs/issuesOpen issue here - https://github.com/dotnet/dotnet-api-docs/issuesarea-COMarea-Serialization-BinaryFormatter-FeatureWorkFeature work under the general area of BinaryFormatter related serializationFeature work under the general area of BinaryFormatter related serializationtracking-external-issueAn issue is caused by an external system and won't be fixed in this repoAn issue is caused by an external system and won't be fixed in this repo
Milestone
Metadata
Metadata
Assignees
Labels
📚 documentationOpen issue here - https://github.com/dotnet/dotnet-api-docs/issuesOpen issue here - https://github.com/dotnet/dotnet-api-docs/issuesarea-COMarea-Serialization-BinaryFormatter-FeatureWorkFeature work under the general area of BinaryFormatter related serializationFeature work under the general area of BinaryFormatter related serializationtracking-external-issueAn issue is caused by an external system and won't be fixed in this repoAn issue is caused by an external system and won't be fixed in this repo
Type
Fields
Give feedbackNo fields configured for issues without a type.
In order to avoid
BinaryFormatteryou need a customTypeConverterforAxHost.Stateto serialize without it. We have an existing converterAxHost.StateConverterthat does this, but it isn't actually registered forAxHost.State. We may decide to register it eventually, but even if we do, to support cross compilation with .NET Framework it's necessary to know how to inject aTypeConverterat runtime versus the normal way of applying an attribute.TypeConverterdocs should be updated with this how-to that we then refer to in our docs. Afaik it isn't described anywhere.