And hope another developer never gets hired to make modifications to your code... :o)

>>>Question to the Refox gurus -
>>>How hard is it to 'break' something branded with Refox? I'm asking not because I want to 'break into' someone's code, but I want to assure myself nobody can break into mine.
>>>
>>>Is it REALLY foolproof?
>>>
>>>Thanks in advance!
>>
>>It looks like nothing is perfect. But at least a protection (ReFox, KonXise or any other mean) is still better than no protection at all.
>>
>>Like Jos said anybody that really wants to get the source code will find a way.
>>
>>I'm also looking for the best way to protect my app. A way that could be good is to replace method names, property names...
>>
>>In short replace everything meaningful by something meaningless.
>>
>>Example replace the method name "ComputeTheTaxes" by "AA1". I remember someone on the UT mentioning that this is what he was doing. But I don't remember who said that.
>>
>>And then after that renaming you protect the EXE with ReFox or your selected protection tool. As an end result you'll have a fair enough protection. One that'll discourage basic hackers wannabees. And for those that really want to work hard to get the source code they'll get something like
>>
>>do form SK2 with ad4, CF5
>>
>>Who would be brave enough to try to understand this. I'll give it to you that this can still be worked out but the additional complexity will probably discourage many.
>
>
>The renaming is a good idea. If you really want to make it hard for someone to read... name everything with one's, (1), L's (l) zero's (0) and O's (O). Who's going to want to look at something like
>Do From 10lOO11ll000 with l0010lll, l010OOOO