A suggestion for the next release.
For processing and storing the received results,
it would be much more convenient in the future if all model/response/request classes were serializable as XML.
- First of all adding:
[Serializable]
This is not the case today, as interfaces such as ICollection and IDictionary, ... are used there.
As a result, wrapper classes or properties always have to be added for “simple” serialization,
and the classes from the GITHUB project cannot be used directly.
That causes many manual work and can result in errors and conflicts.
Specific examples:
- SessionInvoice.UpoDownloadUrl of type = Uri:
-- better to use string
- InvoiceStatusInfo.Details of type = ICollection:
-- better to use List
- InvoiceStatusInfo.Extensions of type = IDictionary:
-- better to use List (with own element type)
A suggestion for the next release.
For processing and storing the received results,
it would be much more convenient in the future if all model/response/request classes were serializable as XML.
[Serializable]
This is not the case today, as interfaces such as ICollection and IDictionary, ... are used there.
As a result, wrapper classes or properties always have to be added for “simple” serialization,
and the classes from the GITHUB project cannot be used directly.
That causes many manual work and can result in errors and conflicts.
Specific examples:
-- better to use string
-- better to use List
-- better to use List (with own element type)