Great reply Sven! Very informative. Smiley

Yggdrasil, it all depends on your product and who the target customers are, and who your current (and perhaps potential future) competitors are.

If you have no valuable proprietary information, then ease of decompilation is not really a threat to you.

If you have to compile in information that through decompilation can either give your potential customers a much easier way of using your product without paying you for the rights, or give your competitors answers to problems that would normally take many months to figure out, ease of reverse engineering becomes a serious issue.

Perhaps you are one of the only few who knows the solution and its algorithm to Problem A (which cannot be copyrighted or pattented for whatever reason). If your competitors get a hold of this information, it will unlock the doors to many products for them as well. The kicker is, your product will not function without putting this information inside of your assembly. What do you do? Just compile your code in the .NET environment and hope your competitors are ethical? Wink

If the most valuable algorithm you have in your software is how to read and write a text file, i don't think you have anything to worry about. Smiley

In response to your very last sentance, if you are referring to the decompilation of .NET assemblies, well I can tell you from experience, any programmer/hacker combo with even moderate skill can decompile and manipulate even obfuscated .net assemblies with ease. When I first decompiled a .net assembly, i was dumbfounded. I could not believe my eyes and then I could not believe such a easy reversable coding technology would ever find its place in the programmig world. I was wrong.