Tech Off Post

Single Post Permalink

View Thread: Methods of protecting .net exe's from decompilation?
  • User profile image

    figuerres wrote:
    first thing I always ask is why?
    then what is the risk?
    what is the benefit?
    what is the cost?
    what is the audience (users, who, sales market)?

    most of the time the users are not going to mess with the code and the cost far outweighs the benefit.

    if the users are tech-savy hacker types then the same thing happens as a determined cracker will break any protection if they are willing to spend the time and effort.

    I often see similar types of responses when people ask about protecting their source..

    I guess some people simply don't understand..

    For a small operation like mine, code security is key to our business future. If we were to release our product in unencrypted .net, our competitors would gain substantial IP to help rocket them into markets where we already exist, and if our .net app could easily be reversed many new competitors would pop up.

    You see, not everybody is a adobe, or microsoft, or even winzip or nero...

    Some outfits have a lot of development time invested into developing product for consumers that have no current available options.. We invest heavily to make a product that most of the time, others don't know how to do. Again, if we released our .net unprotected well then these others would pop up out of the wood work.

    Now, most people say, well you provide great customer service and a great product and you won't have to worry about that. That only works if your target consumer is willing to pay the premium for those services. If your target consumer (unfortunately) wants the product at the lowest price that argument goes right out the door.