Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One way or another, WCF must be able to bind elements in your service's data contract to your client's proxy classes. There is usually little value is obfuscating the proxy classes and their members, but if you do want to obfuscate them you can explicitly set the name of the types and their members using the <code>Name</code> parameter of the <code>[DataContract]</code> or <code>[DataMember]</code> attributes (eg. <code>[DataMember Name="ID"]</code>). Once you've done this, you can disable the "Types and fields marked as serializable" built-in rule from the Rename -> Built-In Rules tab and ensure that "Compatibility with XML serializer" is checked in the Rename -> Options tab. The caveat to this approach is that the names of the serialized properties are still included in your code (in the attributes), and are still sent over the wire.</p> <p>If you require more protection and you have control of both the service and the client, a better but more cumbersome option might be to put your service contract in its own assembly and process that with Dotfuscator. Again, disable the "Types and fields marked as serializable" built-in rule from the Rename -> Built-In Rules tab and ensure that "Compatibility with XML serializer" is checked in the Rename -> Options tab. Now reference the resulting service contract DLL from both your service and your client application. The tradeoff with this approach is that the contract members will all have obfuscated names (eg. "a") and you will have to reference them as such in your service and client application code. You can examine the map file Dotfuscator produces in order to make sense of the renamed names.</p>
    singulars
    1. This table or related slice is empty.
    1. POObfuscate WCF Proxy Classes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbsiegel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POObfuscate WCF Proxy Classes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI have control over both service and client. obfuscating service and referring in my code will have maintenance problem in future as you pointed out. Is there an option in Dotfuscator where I can obfuscate both simultaneously? In that way I build my service and client for release and then obfuscate together.
      singulars
      1. PO
      1. USHakim
    2. COIf that's the case, you could add your service binaries, your data contract DLL, and your client binaries to the same Dotfuscator project. Make sure to use the same settings I mentioned previously, and don't set a Name property in the datacontract/datamember attributes so that Dotfuscator will rename the contract's members. Then just make sure to include the obfuscated contract DLL with both the server & client binaries.
      singulars
      1. PO
      1. USbsiegel
    3. COit is not obfuscating classes because it say _"MyClass is decorated with System.Runtime.Serialization.DataContractAttribute."_
      singulars
      1. PO
      1. USHakim
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload