The website will allow compiling each page on the fly, if you opt to put
source on the server. It also compiles each folder and/or page (per rules)
as a different DLL.

The web app project produces a single DLL (ala Visual Studio .NET) and you
cannot easily compile on the fly unless you stick code in the actual page
(not completely sure about that either).

I generally use the web app project type, as I deploy full sites, not
partial. In fact, I see little purpose in deploying single pages for an
Enterprise site (I am sure someone, somewhere has a good reason). You can
set either to go to http://localhost/siteName.

*************************************************

its just a preference. web applications are most compatiable with VS 2003
projects (which was the justification for adding the feature) .

the main difference is with web applications, there is a project file and
and visual studio compiles the codebehind files into a dll, then compiles the
aspx pages. with a web site visual studio uses the aspnet_compiler to compile
the aspx page and the codebehind. both support additional project files for
library dlls (via a solution file).

due to the compile methods, web sites need global methods defined in
app_code, and if a page references another one a reference directive is
required, or an interface should be defined in app_code, and a cast done.

the implemention of web applications is a little hacky (vs goes thru hoops
to keep the aspnet_compiler happy), but you will find lots of developers like
it.

-- bruce (sqlwork.com)