Description: Over the last 2 plus years, I5;ve run into several situations where developers have moved from classic ASP to ASP.NET and have chosen (not always correctly, in my opinion) to use their own \"custom methodology\" in an effort to avoid the codebehind model that5;s built into Visual Studio.NET. There are a number of reasons for this; they\'re not always all logical, and some are downright fallacious. I\'ll try to address some here and...