Hi, Bryan.
re:
In 1.x, I never really used website projects. I would just build
a class library that happened to include some aspx pages, then
load the aspx pages and the compiled dll to the web server.
I'd like to be able to do something similar with vs2005/2.0.
You can do it in the same identical way in VS.NET 2005.
It's just that VS.NET/ASP.NET/.NET Framework 2.0 offer
different compilation models, but the basic compile-to-assembly
and-publish-only-the-dll-and-related-files model is still good to go.
Even though ASP.NET offers seven specialized directories,
you basically only need /bin and aspx pages for a site to work.
The rest is just frosting on the cake.
The "pre-compile" option in ASP.NET 2.0 is not the same thing
as "pre-compiling" an assembly, btw. The "pre-compile" option
in ASP.NET 2.0 means that the aspx pages will not have to be
JIT-compiled and that, therefore, there will be no delay in serving them.
As you probably know, when a page is called for the first time, it's JIT-compiled,
and there's a slight delay in serving the page, while it's being compiled.
When you pre-compile in ASP.NET 2.0, there won't be a delay for the first page.