StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19842092
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-07T17:03:52.757
FavoriteCount
0
LastActivityDate
2013-11-07T17:16:43.097
LastEditDate
2017-05-23T10:27:06.667
LastEditorUserId
-1
OwnerUserId
2696426
ParentId
19666511
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Although it might not answer your question this might solve your problem: I was able to serialize all but one assembly required for deserialization alongside an object structure. The trick is to use reflection to inspect your object structure for types and the assemblies they are defined in. You can then write the assemblies as binary data into an object on serialization and load them into an AppDomain where you can use them to deserialize the rest of the object structure. You have to put the AppDomain handling, the root object and some base classes into an assembly that won't change and everything else is defined in assemblies depending on this "anchor". Upsides: <ul> <li>serialization does not break as long as the anchor assembly does not change</li> <li>can be used for obfuscation, e.g. some required assembly can be hidden in any file</li> <li>can be used for online updates, e.g. ship the assembly with any data</li> <li>as far as I'm concerned no problem with generics </li> </ul> Downsides: <ul> <li>security issues as bootstrapping could be used to inject code (some extra work for assembly SecurityEvidences)</li> <li>AppDomain borders are some work to cross</li> <li>blows up your serialized data (ok, for files - bad, for communication)</li> </ul> But hey, communication does not break unless you have different client versions and then you can do the bootstrapping on handshake. Sorry, I can't provide the code as it's too complex and too specific. But I share some insights in these other answers of mine: <a href="https://stackoverflow.com/questions/4545439/difference-between-datacontract-attribute-and-serializable-attribute-in-net/19836842#19836842">difference between DataContract attribute and Serializable attribute in .net</a> <a href="https://stackoverflow.com/questions/11122052/need-to-hookup-assemblyresolve-event-when-disallowapplicationbaseprobing-true/19702548#19702548">Need to hookup AssemblyResolve event when DisallowApplicationBaseProbing = true</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to create a SerializationBinder for the Binary Formatter that handles the moving of types from one assembly and namespace to another
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USNo answer
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.