Sargo wrote:[color=blue]
>
> Im about done with my coding on my latest project and want to use a
> Obfuscator to protect it. What suggestions can everyone offer for one. My
> project is done as a hobby and I would prefer one thats freeware or under
> 100 bucks (if these types exsist)
>
> Hopefully they will protect against VS.NET decompiler as well.
>[/color]
Your last sentence makes me think if you know what 'obfuscation' means.
One question: In which form are you delivering your project?
As source code or as compiled (and possibly linked) binary.
If the later is the case: Don't worry. The binary (the library or
the executable) will already be in a form that no one can reverse
engineer it without lots of effort.
All an obfuscator does is: Work on the source code level to make
the program text unreadable. If you don't hand out the source code,
you don't need to obfuscate it. If you do: Well, a start is to remove
line breaks and cram lots of statements into a single line. Also: renaming
variables to one or two letters ( the letters i, 1, l are good candiates
for that as they look pretty much the same ) helps too.
But: Even obfuscated code can be made readable, if someone puts a little bit
of effort into it.
--
Karl Heinz Buchegger
kbuchegg@gascad.at 
