Comments
Sort by recent activity
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.
Here is the article that describes how SmartAssembly searches for dependencies http://www.red-gate.com/supportcenter/C ... rtAssembly
Additionally you can remove a folder from the dependiency search by editing an XML file: SmartAssembly.settings. This will be in a location like:
C:\ProgramData\Red Gate\SmartAssemblyThere will be an editable section with the tag <DependenciesSearchPaths> / comments
Here is the article that describes how SmartAssembly searches for dependencieshttp://www.red-gate.com/supportcenter/C ... rtAssembly
Additionally you can remove a folder from the dependiency search...
There is a risk that SmartAssembly might be pruning some of the workarounds in your manifest.
Can you trace the problem to a specific SmartAssembly feature (such as Pruning) ? / comments
There is a risk that SmartAssembly might be pruning some of the workarounds in your manifest.
Can you trace the problem to a specific SmartAssembly feature (such as Pruning) ?
The first place to start is this article about using SmartAssembly with Silverlight: http://www.red-gate.com/supportcenter/C ... rtAssembly
As you will read, some of SmartAssembly's features will not work with Silverlight applications due to technical limitations in Silverlight.
If you still experience problems with your processed assembly then you can use Error reporting to help find the cause as outlined in this article http://www.red-gate.com/supportcenter/C ... 362558.htm / comments
The first place to start is this article about using SmartAssembly with Silverlight:http://www.red-gate.com/supportcenter/C ... rtAssembly
As you will read, some of SmartAssembly's features will no...
SmartAssembly can merge or embed dependencies, but doesn't attempt to embed the *.exe.config file. Exe.config is useful because it is separate and can be edited outside the application , so there is no reason to embed it. / comments
SmartAssembly can merge or embed dependencies, but doesn't attempt to embed the *.exe.config file. Exe.config is useful because it is separate and can be edited outside the application , so there...