[phyrrus9]

Now, when I say code security I don't mean trivial things like checking your inputs, preventing overflows, maintaining a proper stack, etc. I'm talking specifically about reverse engineering, patching, and licensing constraints.

I'm currently working on a project where the client wants me to create something that is near impossible to crack or duplicate, but one of the requirements is that it must use a WPF GUI. Now, this raises an issue, because WPF being one of those stupid MS bytecode languages makes it very easy to reverse engineer and patch it. Here's my solution:
C#/WPF GUI
C dylib with core of application (native code)
force inlining of specific valuable functions to make patching much more difficult (attacker would have to patch hundreds of functions rather than just one)
daemon to handle the actual work (written in C++). This makes the C# portion of the code simply a "console" no different from a website.

Let me know what you guys to to enforce and implement code security.