jender624

As I've said, the "if" question is not really applicable anymore...it's already been decided that we will be protecting our app in some way. I'm just trying to get the options. I realize that none of these options will prevent determined individuals from cracking into the .exe, but we do want to at least make them work harder to do so. Here's another one...does anybody know of any way to only partially protect/encrypt an .exe file? For example, say I only wanted to protect certain assemblies, but not others. Just wondering if anybody has heard of something like this being done. Thanks! jender624

An additional question; does anybody know if it's possible or practical to first enfuscate an exe, then apply an encryption method, whether it be using something like exeshield or otherwise? Thanks, jender624

Our project manager has decided that we're going to employ some method to protect from decompilation, so the "if" question has been answered. It's the "how" that I need to figure out. Thanks for the other thread reference...the Salamander Protector that was suggested looks interesting. If anything, it's something that I can throw out on the table as a reference. If anybody thinks of anything else, I'd love to hear about it. Thanks, jender624

Hey all, Could somebody give me any resources that discuss options on how to protect source code from any efforts to reverse engineer it from the built executable? I've read about the Dotfuscator utility that comes with the visual studio 2005 beta... I'd like to learn about how to encrypt the exe, and any other techniques out there. Can anybody help me? Thanks, jender624