Best deployment strategy

[Binoy]

Hello,

I am new to .NET, so if my questions is dumb, please
excuse me.

We are moving our ASP model site to ASP.NET and I would
like to know the best deployment strategy that we can use
(we have a pretty big site). I got the following
information from a web site -

There are THREE deployment models.

1. Make all pages as it is in ASP (one aspx file with
design+code) - In this case, deploy all the files as is.

2. Code behind (.aspx file and .vb file - Deploy .aspx
file and compiled .dll - I have a doubt here, does this
mean that if I have a big web site, all the .vb files
will compile to a single big .dll file, which I have to
deploy?)

3. Use @page= option to create a code behind page (this
will create a .dll file for each page, deploy .aspx page
and corresponding .dll file)

Am I missing something or is this the way it is? If you
know some links where I can get more information, that
will also be appreciated.

Thanks in advance
-Binoy

[Mark Rossler]

I've read your replies to "binoy" regarding deployment options.

We have a similar desire in that we want smaller .dll's, too. Our desire is
founded in the fact that we deploy to nearly 200 sites, all private LANs.

If, for example, a bug is found during the running of Payroll, then the time
it takes to recompile, deploy to an FTP site, have the customer get from the
FTP site, and reinstall is critical. A large .dll hinders this
tremendously, while compiling to several smaller .dll's allows us to just
send a much smaller chunk to the site(s).

I agree that option #1 is to be avoided. We're living with option #2 for
now, but are hoping for a different solution.

So, how does option #3 work and why is that a bad thing?

Thanks for letting me pop in here,

Mark Rossler