Comments
Sort by recent activity
Chris.Allen wrote:
Good news, finally. I have a solution. I apologise how long it took (its a two-part solution which partly explains the complexity).
1.MandatoryPath="C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll"
It seems necessary to point to the full physical location of the real mscorlib. This can be found using, for example, Reflector (open it up in, for example, C:\Windows\Microsoft.NET\Framework\v4.0.30319\) and look at the bottom left window- reflector tells you the full physical location)
2. Smartassembly has a tendency to cache the settings file so one workaround I use is to copy the full install path:
C:\Program Files\Red Gate\SmartAssembly 6\*.*
and put it somewhere convenient, such as your desktop, the just run it form this new path- it re-reads all files.
This has been tested extensively. If you still get problems, please let me know which step and send new smartassembly debug log.
This solution works until the application references mscorlib 2 and 4 if you reference an dotnet 2 dll. Unfortunately I can't get a debug for some reason. / comments
Chris.Allen wrote:
Good news, finally. I have a solution. I apologise how long it took (its a two-part solution which partly explains the complexity).
1.MandatoryPath="C:\Windows\Microsoft.Net\a...
Chris.Allen wrote:
Please change the line:
<Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=b77a5c561934e089">
to:
<Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=b77a5c561934e089" mandatorypath="C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib ">
Still the same error. / comments
Chris.Allen wrote:
Please change the line:
<Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=b77a5c561934e089">
to:
<Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyTo...
The function is there but it still won't obfuscate, something that I notice is that even though I point it to the right path it keeps mentioning "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\mscorlib.dll" instead of the mandatorypath I supply / comments
The function is there but it still won't obfuscate, something that I notice is that even though I point it to the right path it keeps mentioning "C:\Program Files (x86)\Reference Assemblies\Microso...
Chris.Allen wrote:
Ok, thanks.
This is basically an error in how we resolve the assembly- if you point the mandatorypath to:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib
That should now work as its the *real* assembly.
Unfortunately that doesn't make a difference. / comments
Chris.Allen wrote:
Ok, thanks.
This is basically an error in how we resolve the assembly- if you point the mandatorypath to:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib
That should no...
I've tried:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1
If I set the mandatory path for the dll that get's merged it doesn't recognize the dll anymore so it has to be set on the main assembly. / comments
I've tried:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1
If I set the ma...
Please read: http://www.red-gate.com/supportcenter/c ... Attributes / comments
Please read: http://www.red-gate.com/supportcenter/c ... Attributes
One of the other interesting things you can do with this is make the exception reporter behave differently when you set a certain value.
For example I used it to be able to send some reports silently without user interaction (Visible = false; ShowInTaskbar = false; and some other small hacks needed). / comments
One of the other interesting things you can do with this is make the exception reporter behave differently when you set a certain value.
For example I used it to be able to send some reports silent...
Chris.Allen wrote:
The only defence is to ensure that all protections are added and added at their highest level.
Even with those settings, our program (130k+ lines of code) is easily reversed with the vital parts exposed!
Within a minute I was able to decipher internal passwords, logic and it resembled my code quite a bit again. / comments
Chris.Allen wrote:
The only defence is to ensure that all protections are added and added at their highest level.
Even with those settings, our program (130k+ lines of code) is easily reversed...