Suggestion: Patch Friendly Settings

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, melvyn.harbour, dom.smith

Suggestion: Patch Friendly Settings

Postby mclarke » Wed May 23, 2012 11:06 am

Hi,

We use binary patches for our application - I noticed in the EAP forum a similar question was asked: http://www.red-gate.com/messageboard/vi ... hp?t=11010

I'm finding that our binaries are changing quite a bit, even with a small degree of change (~75%). I would find it useful, if I was able to specify that small changes to the code base resulted in smallish changes to the compiled binary.

Thanks for your time,
Martin
mclarke
 
Posts: 6
Joined: Wed Feb 01, 2012 4:33 pm

Postby james.billings » Thu May 24, 2012 1:45 pm

Thanks for your post.

I don't think we've put any changes in to specifically assist in this scenario.

Many of the options in Smartassembly will stop you from subsequently post-processing the assembly. At a basic level, a binary diff of both assemblies *after* processing may work okay depending on the options you have selected, but the points raised in the previous post will still stand (in that a small change in the pre-obfuscated code could cause quite a large change to the resulting assembly once processed)
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.


Return to SmartAssembly 6

Who is online

Users browsing this forum: zwestfall and 1 guest