I was wondering if anyone knows a way of changing Visual Studio .Net's
behavior when dealing with code behind files, or perhaps explain in detail
why MS forces you to use code behind. I personally do not like using code
behind files. I would prefer to use inline coding or store the code for a
particular page in a DLL mainly to easily maintain the file structure of an
ASP.Net application. I haven't been able to locate a way to change this
inside VS. MS Web Matrix doesn't force you to use code behind, so why does
Visual Studio .Net? In Visual Studio .Net you can't even store the code in
a DLL file and have it inherit from a particular class without VS freaking
out when you try to load the .aspx or .ascx file into the editor. It's
VERY irritating.

Chaitanya Marvici