Activity overview
Latest activity by Eaton
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.
I'm glad you were able to find and fix the problem! Looking forward to a fix version. [image] / comments
I'm glad you were able to find and fix the problem! Looking forward to a fix version.
Did you customize the SA error report module in any way or are you using on of the default ones? / comments
Did you customize the SA error report module in any way or are you using on of the default ones?
I have provided a sample project. Hopefully you guys can use it to pinpoint the problem.
Let me know if you need anything else. I am more than happy to help you make SmartAssembly a better product. / comments
I have provided a sample project. Hopefully you guys can use it to pinpoint the problem.
Let me know if you need anything else. I am more than happy to help you make SmartAssembly a better product.
Paul.Martin wrote:
Eaton wrote:
I can't look at a protected version because it gives me a build error every time.
Sorry yes.
OK, well that narrows down the problem slightly. If you have a look in the *.csproj (or *.vbproj) in notepad or similar does it mention both versions of mscorlib?
I have done some very intensive research on this matter. I have checked my project file for references to mscorlib, but none exist. All of the other references are there, but none to mscorlib at all.
I then proceeded to start a new project and put all of my classes and forms into it. Still the same issue. / comments
Paul.Martin wrote:
Eaton wrote:
I can't look at a protected version because it gives me a build error every time.
Sorry yes.
OK, well that narrows down the problem slightly. If you have a l...
Paul.Martin wrote:
Could you have look at your original (before SmartAssembly protected) assembly in Reflector and see if it is referencing two version of mscorlib.
SmartAssembly should look at the version of mscorlib referenced and from that and a few other hints link against the correct version of the framework.
That is what I am doing, I open my unprotected assembly in Reflector and there are two references. I can't look at a protected version because it gives me a build error every time. / comments
Paul.Martin wrote:
Could you have look at your original (before SmartAssembly protected) assembly in Reflector and see if it is referencing two version of mscorlib.
SmartAssembly should look at ...
Ok, thanks, I added it, but now I get get a build error: http://img641.imageshack.us/img641/5119/errorgj.png
I backed up my old project file so I tried that and I still got the error. So I am guessing it is a recent change in my application that is causing this.
However, in the EAP forum, which doesn't appear to be here anymore, I recall someone having this error. He had two versions of mscorlib referenced. I open my application in Reflector and I have two referenced! .NET 2 and 4.
Any idea on how to remove that reference? It isn't in the References in the project itself in VS. / comments
Ok, thanks, I added it, but now I get get a build error:http://img641.imageshack.us/img641/5119/errorgj.png
I backed up my old project file so I tried that and I still got the error. So I am guessi...
I already did, but I do not expect much from them as they usually fix bugs they find and not the ones that people report.
Also, I can't get your workaround to work. Is this correct?
<Options>
<DoNotAddPoweredByAttribute />
<WebProxy UseProxy="0" />
<Projects UseRelativePaths="1" />
</Options>
Because that is not working.
Also, why is it not recommended to do that? / comments
I already did, but I do not expect much from them as they usually fix bugs they find and not the ones that people report.
Also, I can't get your workaround to work. Is this correct?
<Options>...