title: Performance penalty on putting classes in aspx and ascx codebehinds
body: <p>What's the performance penalty on defining classes in an aspx/ascx codebehind rather than compiling them into a dll beforehand?  I know that this isn't a best practice and that there are numerous problems with this (e.g. difficult to unit test, code is not reusable, etc.), but it does come in very handy when you're dealing with classes that need to be modified on the fly several times a day since those modifications will not require any sort of app restart (e.g. App_Code changes, updating dlls in bin folder).</p>