Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am designing a web app that will be licensed to organisations to install on their Intranets. I am using the ‘Publish’ feature in VS 2010. This creates all the necessary aspx pages but compiles code into a DLL so it is not exposed to the client.
However, the published web.config remains editable so presumably the client could turn <compilation debug="true"> to look at my code, or change the assembly references to effectively ‘mod’ the app. Is it necessary/possible to get around this?
Unless you’re shipping source code, turning
<compilation debug="true">will have no effect on the released/published DLLs.You can obfuscate your DLLs so that even if they look it up in Reflector, it doesn’t make much sense.