Activity overview
Latest activity by SlushPuppy
The problem is it is outputted from a private Rapid Development tool that outputs a .net assembly, and they already pass it through SA6. We tried making our wrapper using .NET (C#) but can't execute the assembly when using byte loaded assembly.
I assume this is the same problem we are having when using commercial licensing tools like ExecKey, Intellilock, and so on. They will wrap the exe, and the licensing wrapper works, but won't spawn off the exe properly. / comments
The problem is it is outputted from a private Rapid Development tool that outputs a .net assembly, and they already pass it through SA6. We tried making our wrapper using .NET (C#) but can't execu...
james.davies wrote:
OK. Using reflection on obfuscated code often causes issues.
Could you add the licensing wrapper to your code and then process with SA? (SA generally works best when it is done last)
Unfortunately no, the output we are given has already been run through SmartAssembly. It seems like Main() is always "#gB" but when I specifically invoke that function using Assembly.Invoke or other methods, it will launch two obfuscated module names (different every execution) but won't actually show the application. / comments
james.davies wrote:
OK. Using reflection on obfuscated code often causes issues.
Could you add the licensing wrapper to your code and then process with SA? (SA generally works best when it is ...
james.davies wrote:
Execute Assembly probably finds the entry point using
public virtual MethodInfo EntryPoint { get; }
(http://msdn.microsoft.com/en-us/library ... point.aspx)
Your best option is to use that rather than trying to manually lookup the entry point in the obfuscated assembly.
I was using the below code, which I believe is doing what you suggest.
Assembly a (byte loaded exe that is run through SmartAssembly)
a.EntryPoint.Invoke(null, null); / comments
james.davies wrote:
Execute Assembly probably finds the entry point using
public virtual MethodInfo EntryPoint { get; }
(http://msdn.microsoft.com/en-us/library ... point.aspx)
Your best option ...
ExecuteAssembly
I am trying to byte load an assembly that has been processed with SmartAssembly and execute it, but I am having a lot of problems.
If I use EntryPoint.Invoke, it load two obfuscated modules and the...