Would you obfuscate your code before deploying it?
-
Actually this is more of seeking your opinion than seeking your help to have an issue resolved, I've been working on a website for a couple of months and I'm preparing to get it online, I'm planning to have it hosted on a dedicated server, the question is, would you obfuscate your code before deploying it to protect your hardwork? or you'd simply upload it with no obfuscation to avoid all the problems that come with it, e.g. performance decrease, being unable to log exceptions (as the information in the stack trace would be useless in that case) .. etc? What would you do? Thanks for any suggestions ...
Waleed Eissa Software Developer Sydney
-
Actually this is more of seeking your opinion than seeking your help to have an issue resolved, I've been working on a website for a couple of months and I'm preparing to get it online, I'm planning to have it hosted on a dedicated server, the question is, would you obfuscate your code before deploying it to protect your hardwork? or you'd simply upload it with no obfuscation to avoid all the problems that come with it, e.g. performance decrease, being unable to log exceptions (as the information in the stack trace would be useless in that case) .. etc? What would you do? Thanks for any suggestions ...
Waleed Eissa Software Developer Sydney
I never used to do it. It makes the deployment tough - AFAIK.
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
-
Actually this is more of seeking your opinion than seeking your help to have an issue resolved, I've been working on a website for a couple of months and I'm preparing to get it online, I'm planning to have it hosted on a dedicated server, the question is, would you obfuscate your code before deploying it to protect your hardwork? or you'd simply upload it with no obfuscation to avoid all the problems that come with it, e.g. performance decrease, being unable to log exceptions (as the information in the stack trace would be useless in that case) .. etc? What would you do? Thanks for any suggestions ...
Waleed Eissa Software Developer Sydney
You need to consider if theres actually any "valuable IP" in what you are deploying. I'd say that in 99% of applications, especially websites there just nothing unique or reusable being done. If you are worried that someone might read your code and learn some techniques they couldnt read tutorials elsewhere (and better documented) then you must be doing some quite cool stuff ;) Don't bother. We don't even obfuscate our products, its unlikely that anyone is going to be disassembling our code for reuse (and if they did they'd be exposing themselves to some pretty serious legal risk). Fact is that if your competitors need to copy you then they are always going to be behind. I'm using yFiles (a graph layout library) at the moment. Its obfuscated which is a massive pain in the arse for debugging. You get exceptions being thrown out saying "couldnt cast a.a.b.c to d", not even giving a slight clue what went wrong. Who is going to have the skill and time to dissassemble and reengineer a product that complex, without any trace of its origin, and be able to make it better enough to be able to sell it? Leads me to recommend it only if you need specific features it offers (otherwise go with a cheaper one). Mark Churchill Director Dunn & Churchill Free Download:Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.