Deploying 2.0 WebSites

[daokfella]

I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)

If so, we're just duplicating the file system from the development
machine to the production server?

I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason

[George Ter-Saakov]

You are correct except #2. If you moving aspx files then you do not have
precompiled DLLs unless you added some DLL as a reference.

aspx and vb files compiled on a fly by asp.net. But if you wish you can
precompile your application then you do not need to move aspx or vb files.
George.
"daokfella" <jj******@hotmail.comwrote in message
news:11**********************@c77g2000hse.googlegr oups.com...

I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)

If so, we're just duplicating the file system from the development
machine to the production server?

I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason

[David R. Longnecker]

While I prefer the new methodology of web sites, there is the option to use
a Web Application project rather than a Web Site project. The WAP follows
a similar 2003 project set of complication and rollout rather than the direct
copy/publish of .net 2.0.

http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx has more information.

-dl

--
David R. Longnecker
http://blog.tiredstudent.com

GYou are correct except #2. If you moving aspx files then you do not
Ghave precompiled DLLs unless you added some DLL as a reference.
G>
Gaspx and vb files compiled on a fly by asp.net. But if you wish you
Gcan precompile your application then you do not need to move aspx or
Gvb files.
G>
GGeorge.
G>
G"daokfella" <jj******@hotmail.comwrote in message
Gnews:11**********************@c77g2000hse.googleg roups.com...
G>

>I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)
If so, we're just duplicating the file system from the development
machine to the production server?

I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason

[Joey]

On Jun 25, 2:35 pm, daokfella <[e-mail]:

I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)

If so, we're just duplicating the file system from the development
machine to the production server?

I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason

Right click on the name of your project at the top of your solution
tree.
Choose "Publish Web Site"

The simple options box that follows will give you several options.

I prefer to develop the app as a "file system" website. Then when I'm
ready to deploy it, I run "Publish Web Site," uncheck "Make this web
site updateable" (this forces stub pages for the aspx pages and rolls
BOTH the aspx and code-behind pages into dll file(s),) and then
publish to a local or intranet folder running IIS (i.e. 'C:\Inetpub
\wwwroot'). Once it's in the IIS folder, I can test hit it with
(http://localhost). Also, since everything is there, I can also copy
it out to other servers easily, if that's what I need. That always
seems to work very well.

[Juan T. Llibre]

Also, remember that VS 2005 SP1 includes WAP
as the default without needing a separate install.

With it, you get to choose the number and names of the dll's.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"David R. Longnecker" <dl*********@community.nospamwrote in message
news:46************************@msnews.microsoft.c om...

While I prefer the new methodology of web sites, there is the option to use a Web Application
project rather than a Web Site project. The WAP follows a similar 2003 project set of
complication and rollout rather than the direct copy/publish of .net 2.0.

http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx has more information.

-dl

GYou are correct except #2. If you moving aspx files then you do not
Ghave precompiled DLLs unless you added some DLL as a reference.
GGaspx and vb files compiled on a fly by asp.net. But if you wish you
Gcan precompile your application then you do not need to move aspx or vb files.
GGGeorge.

G"daokfella" <jj******@hotmail.comwrote in message
Gnews:11**********************@c77g2000hse.googleg roups.com...
G>

>>I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)
If so, we're just duplicating the file system from the development
machine to the production server?

I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason

[David R. Longnecker]

Ahh, good call; forgot about that.

-dl

--
David R. Longnecker
http://blog.tiredstudent.com

JLAlso, remember that VS 2005 SP1 includes WAP
JLas the default without needing a separate install.
JLWith it, you get to choose the number and names of the dll's.
JL>
JLJuan T. Llibre, asp.net MVP
JLasp.net faq : http://asp.net.do/faq/
JLforos de asp.net, en español : http://asp.net.do/foros/
JL======================================
JL"David R. Longnecker" <dl*********@community.nospamwrote in
JLmessage
JLnews:46************************@msnews.microsoft .com...

>While I prefer the new methodology of web sites, there is the option
to use a Web Application project rather than a Web Site project. The
WAP follows a similar 2003 project set of complication and rollout
rather than the direct copy/publish of .net 2.0.

http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx has more
information.

-dl

GYou are correct except #2. If you moving aspx files then you do
not
Ghave precompiled DLLs unless you added some DLL as a reference.
GGaspx and vb files compiled on a fly by asp.net. But if you wish
you
Gcan precompile your application then you do not need to move aspx
or vb files.
GGGeorge.
G"daokfella" <jj******@hotmail.comwrote in message
Gnews:11**********************@c77g2000hse.google groups.com...
G>

>>>I'm still stuck on the .dll and bin folder mentality in 1.1. When
deploying a 2.0 web application, there is no web .dll to deploy?

So is this how we deploy in 2.0?
1. Copy the app_code folder
2. Copy the bin directory containing any pre-compiled dlls
3. Move BOTH aspx AND aspx.vb files into the applicable directories
(is this correct?)
If so, we're just duplicating the file system from the development
machine to the production server?
I guess this technically makes my life easier if I fix a particular
bug in a single *.vb file. I can just copy the vb file over (rather
than compiling and copying the entire web.dll over like in 1.1.

Is this all correct? Or am I missing anything?

Jason