Comments
Sort by recent activity
I think this has been answered here: http://www.red-gate.com/MessageBoard/vi ... hp?t=14073 / comments
I think this has been answered here:http://www.red-gate.com/MessageBoard/vi ... hp?t=14073
We believe we have fixed this bug in the latest version of SmartAssembly.
Please click on “Check For Updates†(under “Tools†on the left hand side) and upgrade SmartAssembly. (to v6.5.2.21)
Please let us know if the problem is fixed (or not) / comments
We believe we have fixed this bug in the latest version of SmartAssembly.
Please click on “Check For Updates†(under “Tools†on the left hand side) and upgrade SmartAssembly. (to v6.5.2.21)
P...
I am not sure why you don't have access to the code until after it has been processed by Smartassembly ? Do you have a Smartassembly license ?
The supported way to use Smartassembly is to apply it last , and not to use reflection on obfuscated code. / comments
I am not sure why you don't have access to the code until after it has been processed by Smartassembly ? Do you have a Smartassembly license ?
The supported way to use Smartassembly is to apply i...
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) / comments
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)
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. / comments
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 t...
You can exclude code from obfuscation to avoid problems.
This can be done via the SmartAssembly GUI or in code using custom attribute (http://www.red-gate.com/supportcenter/C ... rtAssembly) / comments
You can exclude code from obfuscation to avoid problems.
This can be done via the SmartAssembly GUI or in code using custom attribute (http://www.red-gate.com/supportcenter/C ... rtAssembly)
Yes, storing reports locally is possible. However the stored reports will be encrypted, so listing them may not be useful. The de-obfuscation information is stored on your SmartAssembly client (in the map file and database) and so the error reports need to be moved to the client to be viewed.
There is an example project provided with Smartassembly. It should be located C:\Program Files\Red Gate\SmartAssembly 6\SDK\Exception Reporting\4 Via Email
You need to
1) Save the reports using the SDK (using reportExceptionEventArgs.SaveEncryptedReport(fileName))
2) You can then send the reports by a means of your choice.
3) You then add the report to the SmartAssembly databse using the addreport command (http://www.red-gate.com/supportcenter/C ... rtAssembly)
4) View reports as normal using the Smartassembly GUI / comments
Yes, storing reports locally is possible. However the stored reports will be encrypted, so listing them may not be useful. The de-obfuscation information is stored on your SmartAssembly client (in...
SmartAssembly will only merge or embed assemblies which are in the references metadata. So you will need to add the reference to the main assembly for SmartAssembly to detect it. / comments
SmartAssembly will only merge or embed assemblies which are in the references metadata. So you will need to add the reference to the main assembly for SmartAssembly to detect it.
"Making SA work on the assemblies before they're packaged is required. It's probably best to make SA part of your release build process. "
So you will need to create an msbuild script that runs smartassembly after build but before packaging. And that build script will also need to make sure the copies under /obj/ get replaced with obfuscated versions.
Here is a helpful article about using smartAssembly with msbuild http://www.red-gate.com/supportcenter/C ... 479859.htm / comments
"Making SA work on the assemblies before they're packaged is required. It's probably best to make SA part of your release build process. "
So you will need to create an msbuild script that runs sma...
Note that because of the way the azure build magic works, simply obfuscating assemblies in the output directory isn't sufficient, you need to make sure the copies under /obj/ get replaced with obfuscated versions.
Please try that and see if it helps / comments
Note that because of the way the azure build magic works, simply obfuscating assemblies in the output directory isn't sufficient, you need to make sure the copies under /obj/ get replaced with obfu...