Comments
Sort by recent activity
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...
Sorry , I don't have an example. Only a some notes from a developer about using SmartAssembly with Azure.
The notes are:
We (SmartAssembly) can't open cspkg files. 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.
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.
I hope that makes more sense. / comments
Sorry , I don't have an example. Only a some notes from a developer about using SmartAssembly with Azure.
The notes are:
We (SmartAssembly) can't open cspkg files. Making SA work on the assemblies...
After building SA should show that is has detected and updated the satellite assemblies, in conjunction with the main assembly.
Satellite assemblies should not be merged or embedded as that would break them.
It is also possible that the localizable property has been pruned. You could try excluding it from pruning (and obfuscation). / comments
After building SA should show that is has detected and updated the satellite assemblies, in conjunction with the main assembly.
Satellite assemblies should not be merged or embedded as that would b...
Satellite Assemblies should be handled by later versions of Smart Assembly
What version are you using ? / comments
Satellite Assemblies should be handled by later versions of Smart Assembly
What version are you using ?
Glad you got it sorted. FYI - you can control the folders searched by SA.
These are stored in an XML file: SmartAssembly.settings. This will be in a location like:
C:\Program Data\Red GateSmartAssemblyThere will be an editable section that looks like:
<DependenciesSearchPaths>
<SearchPath>C:\Program Files (x86)\Microsoft Silverlight\4.0.50401.0</SearchPath>
<SearchPath>D:\Removed Folder</SearchPath>
</DependenciesSearchPaths> / comments
Glad you got it sorted. FYI - you can control the folders searched by SA.
These are stored in an XML file: SmartAssembly.settings. This will be in a location like:
C:\Program Data\Red GateSmartAsse...
Unfortunately it is difficult for SmartAssembly to process an assembly that has already been processed by a different Obfuscater. This is because the metadata can be stripped out and that appears to be the case here. So sadly it looks like this assembly can't be merged or embedded , and you will need to distribute it will your application. / comments
Unfortunately it is difficult for SmartAssembly to process an assembly that has already been processed by a different Obfuscater. This is because the metadata can be stripped out and that appears ...
Yes, you are correct. I have replicated the problem and it is exactly as you described. I will add this to our bug tracking system. Many thanks for bringing this to our attention. / comments
Yes, you are correct. I have replicated the problem and it is exactly as you described. I will add this to our bug tracking system. Many thanks for bringing this to our attention.