Hi,
we are developing a custom report designer for end users. The designer works against the CLR API while reports are persisted as serialized trdx.
To provide our designer with additional information, we decided to extend some of the classes. While this works just fine in some cases, it breaks the serialization in others.
Working example:
While the additional property is in fact being serialized, some parts of the base class are not. In this case the table's xml node '<Corner />' remains empty and the table body's node '<Cells/>' is missing.
Is there another way to achieve the desired behavior?
Kind regards
Sebastian
we are developing a custom report designer for end users. The designer works against the CLR API while reports are persisted as serialized trdx.
To provide our designer with additional information, we decided to extend some of the classes. While this works just fine in some cases, it breaks the serialization in others.
Working example:
public
class
ExtendedColumn : TableBodyColumn
{
public
string
Name {
get
;
set
; }
}
Broken example:
public
class
ExtendedTable : Table
{
public
int
HeaderHeight {
get
;
set
; }
}
While the additional property is in fact being serialized, some parts of the base class are not. In this case the table's xml node '<Corner />' remains empty and the table body's node '<Cells/>' is missing.
Is there another way to achieve the desired behavior?
Kind regards
Sebastian