How to package an ASP.NET application to prevent customers from modifying it?
<p>Is there a tool or some general approach to packaging all the files of an ASP.NET application into binary form to prevent modification once its deployed?  I am thinking there would be a set of signed binaries and a config file for settings that we allow the customer to modify.  Has anyone attempted this, is it even possible?</p>

<p>I would pay a reasonable amount for a slick commercial product that did this with minimal hassle.</p>

<p><strong>UPDATE</strong></p>

<p>Sorry, from the answers I can see that I wasn't clear.  I meant literally packaging ALL files, not just the code files.  This means aspx, scripts, images etc.  I'm not trying to prevent reverse engineering... this is a supportability issue, i.e. to avoid dealing with problems brought about by customer messing with the files.</p>
