Comments
Sort by recent activity
You can try to use the Input option when calling SA. Then you can use the same file. I am trying something like this on my build server: <SmartAssembly.MSBuild.Tasks.Build ProjectFile="$(DeploymentRoot)\CommonFile.saproj"
Input="$(DeploymentRoot)\Target1.dll"
OverwriteAssembly="True"
MarkAsReleased="True" />
<SmartAssembly.MSBuild.Tasks.Build ProjectFile="$(DeploymentRoot)\CommonFile.saproj"
Input="$(DeploymentRoot)\Target2.dll"
OverwriteAssembly="True"
MarkAsReleased="True" />
/ comments
You can try to use the Input option when calling SA. Then you can use the same file. I am trying something like this on my build server:<SmartAssembly.MSBuild.Tasks.Build ProjectFile="$(Depl...
I never build a version targeted for a release. Instead, we build a release version on each build. When I have to do a release, I pick the last successful build, run validation tests, and then release it to the customer. At this point I mark our build as retain indefinitely and need to mark the obfuscation as released.
I need to understand how this decryption is managed and be able to see that the decryption information is available. I will hate to be in a position where I am trying to solve a customer problem and cannot decode a stack trace. / comments
I never build a version targeted for a release. Instead, we build a release version on each build. When I have to do a release, I pick the last successful build, run validation tests, and then rele...
There is none except for the info you can find on the website. [image]
However, the support is good. [image] / comments
There is none except for the info you can find on the website.
However, the support is good.