StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6646719
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-11T06:56:45.143
FavoriteCount
0
LastActivityDate
2011-07-11T06:56:45.143
LastEditDate
LastEditorUserId
0
OwnerUserId
167251
ParentId
6646544
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I'm not sure what you are asking, but here goes: Obfuscation is a process to make code hard (for a human) to read ("security through obscurity"). In C# the generated assemblies are typically easy to reverse engineer and obfuscation is therefor heavily used here. There's a number of products that does this. Since you mention CryptoLicensing as your licensing toolkit I'll suggest <a href="http://www.ssware.com/cryptoobfuscator/obfuscator-net.htm" rel="nofollow">Crypto Obfuscator</a> from the same vendor. I think they are totally separate products so don't expect any advantages over other products with CryptoLicensing. I've used this product and am quite happy. There's a number of issues to be aware of when doing obfuscation. Code that rely on reflection are prone to problems due to obfuscation (typically refering to a Type by name fails when the class has been renamed to something obscure). Persisentcy is typically prone to such problems. UI is also tricky. Crypto Obfuscator (and other obfuscators) support disabling some obfuscation features to avoid most of these problems. It also supports leaving one or more assemblies out of the obfuscation. I think it's important that your application is divivded into several sub-libraries/assemblies when doing obfuscation. This enables full obfuscations of parts of your application (e.g. the core), partial obfuscation of other parts (e.g. the UI) and some/none of the rest (e.g. persistent domain objects). I'm not familiar with Crypto Licensing so I won't cover that part of your question.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLicensing and Obfuscation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USlarsmoa
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.