Comments
Sort by recent activity
No matter what you do, if your software is popular, it will be cracked if the cracker has the determination. In this day in age, you can slow the process and make it harder, but you can't stop it.
SA is a good tool, but the more popular a protection tool is, the more attention it will receive.
You should implement more complex security checks in your programs. Don't rely on a protection tool to do everything for you, implement another blanket of defense. / comments
No matter what you do, if your software is popular, it will be cracked if the cracker has the determination. In this day in age, you can slow the process and make it harder, but you can't stop it.
...
cadi wrote:
craigm: Your issue was reported over a month ago.. could you not use {sa} all this time, or did you find a workaround?
If it really is the same issue, then it would mean that the tool is confusing the version of the .NET mscorlib it is using, with the version of the Silverlight mscorlib that my target assembly references.. :shock: Eaton: Is there a possibility that I can try that build? My license does not entitle me to upgrade to 5.1 (was using the 3 and upgraded to 4). Of course I am looking into upgrading again, but in the mean time, I am hoping for a fix on the v4.0. It stopped working overnight, and I got a commercial product to obfuscate and release asap. [image]
Casper
Look in the EAP forum below, that is where they can be found. And I doubt Red Gate would backport a fix into an earlier version. / comments
cadi wrote:
craigm: Your issue was reported over a month ago.. could you not use {sa} all this time, or did you find a workaround?
If it really is the same issue, then it would mean that the to...
Have you tried the latest nightly build? I would have thought they would have fixed it already since it was reported before 5.1 was released. / comments
Have you tried the latest nightly build? I would have thought they would have fixed it already since it was reported before 5.1 was released.