Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The tool you linked to basically compiles the entire application into native code. That doesn't really "shut down" Reflection or anything else, it just turns the application into something entirely different, it's no longer bytecode and not technically a .NET assembly anymore.</p> <p>Callers with full trust can <strong>always</strong> use reflection on a .NET assembly and everything inside it. Aside from (a) obfuscation, which anybody with enough patience and determination could de-obfuscate, or (b) compiling into native code, which would prevent <em>any</em> kind of reflection (and many other useful features), you can't prevent this from happening, and you certainly can't restrict it to specific assemblies.</p> <p>The <code>ReflectionPermissionAttribute</code>, contrary to what one of the other answers says, does <strong>not</strong> prevent callers from reflecting <strong>on</strong> your code; rather, it controls access <strong>from</strong> that code <strong>to</strong> the Reflection APIs. It's not going to be of any help here.</p> <p>Why is it so important to hide your code or class structure anyway? Unless you're working for the NSA, most code just isn't that valuable/secret, and most applications are trivially easy to reverse-engineer given sufficient time and resources. Realistically, an attacker or plagiarist stands to gain very little from copying code out of Reflector and/or using Reflection to discover your API.</p> <p>I suppose I can only speak for myself, but given 1 free day to either implement a cool feature or invest in trying to protect the internal code, I would always work on new features that actually add value.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I restrict reflection for certain assemblies?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAaronaught
    1. USAaronaught
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have some requirements of this sort from client, they want to block some of the assemblies being reflected. So I needed to move code that I am reflecting within application, from those assemblies to separate one, but if there is a way to permit some particular assemblies to reflect, It can save a lot of work of mine
      singulars
      1. PO
      1. USviky
    2. CO@viky: Then your client needs to be educated on how reflection works. There is no opt-in/opt-out system. Moving the code to a separate assembly will not protect the code either.
      singulars
      1. PO
      1. USAaronaught
 

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