DLLs

Sorry for the short and sweet. It was a bad week. Compiling with the command line compiler sucks. VS.NET puts together the entire process, so you don't see that you're actually referencing all the assemblies as well as selecting all the files that must be compiled into the project. It's quite a bit of typing to compile a normal site using the command line compiler--it's not as simple as choosing a folder and saying "Compile That!" The advantage of the method used by the command compiler is that you can take several project's files (let's say for a corporate framework) and combine them into one assembly. So there could be a MyCompany.Web, MyCompany.EnterpriseServices, etc. But, as I've mentioned before, the best way to compile things of this nature is to use a build tool and configure a build. Sorry to ramble.

Well that is the short and sweat version :) Basically how it worx when you use Visual Studio .NET is that when you start a ASP.NET project your ASPX files are link to corresponding ASPX.CS files this is know as code behind. Now When you compile all the ASPX.CS file gets compiled into one dll typically with the name of your project (unless you changed it) then you could upload all the resource file (images etc...) and ASPX file and zero code only the dll located in the bin folder... ad your site will work fine and no one but you has source for the project... I havnt done this in command line yet but I assume its the same way you would compile any other .NET assembly in .NET ;) hope this helps

Write code->compile code->walla...DLL.