Early Access Program for SmartAssembly
Moderators: Luke Jefferson, JasonC, StephenC, Alex.Davies, melvyn.harbour, GrahamH, Simon C
I'm using SA4 and I need to know how SA works on the following scenario:
One class library A that references another class library B. Assembly A was obfuscated with SA setting assembly B with dependency merging. So far so good.
Now, I've a console app X, that also references assembly B. On the X app, I use reflection to load obfuscated assembly A. The question is: Which assembly B the code from Assembly A will use? The one from X app or the one from Assembly A (that was dependency merged)?
- Posts: 1
- Joined: Sun May 09, 2010 12:02 am
A will always use the merged version, since once an assembly is merged into another assembly, it genuinely becomes part of that assembly, and it would be impossible for types to be resolved outside.
The console app will definitely not use the merged copy directly.
Red Gate .NET Tools
- Posts: 335
- Joined: Tue Dec 02, 2008 12:23 pm
- Location: Cambridge, uk
Return to SmartAssembly EAP
Who is online
Users browsing this forum: No registered users and 1 guest