Accessing private variable through PrivateObject on Obfuscated library

Question

0.00/5 (No votes)

See more:

Hi,

I am not able to access private variable value using PrivateObject if my library is obfuscated. i know the variable name and other information are changed when we do obfuscation but is there any workaround for that ?

if i am accessing private variable of the serialized class then it is working fine but non-serialized class's private variables are not accessible using PrivateObject.

can anyone suggest any other solution to get private variable value ?

Thanks
-Amit.

Posted 30-May-12 23:32pm

AmitGajjar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BobJanova · Answer 1 · 2012-05-31T00:45:00

Solution 1

Does your obfuscator generate a log file which tells you what each method/field was translated to? If so, you might be able to use that to reverse the mappings in your test harness and look up the post-obfuscation value.

Note that if you're using reflection looking for known class/method/property names in your actual code (as opposed to the tests), you will need to exclude the targets of that reflection from obfuscation.

Posted 31-May-12 0:45am

BobJanova

Comments

AmitGajjar 31-May-12 6:51am

i only have obfuscated library,even i don't know which tool is used to obfuscate :)

BobJanova 31-May-12 9:36am

Then you're pretty much screwed, the whole purpose of obfuscation is to remove meaning from the compiled code (IL in this case) so if you're looking for particular meaningful names you will not succeed.

AmitGajjar 1-Jun-12 0:31am

actually i have created lots of test cases for checking private variable. but till date we are checking on non-obfuscated library. now client have requirement to check our all test cases on obfuscated library. so stuck there... :(