B
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
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