MBR IT/.NET 247 : How to update deployed apps? on ASPFriends.com 'aspngconfig' list

How to update deployed apps?

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngconfig' list.

cris brady

-- Moved from [aspngfreeforall] to [aspngconfig] by Sheik Yerbouti <Click here to reveal e-mail address> --

Hi, I have some questions regarding updating of deployed ASP.Net
applications. I've read the documentation and can't seem to get a handle
on it.

I have a .Net web application. I developed and tested it in my local
environment. Version 1 looks good to go, time to deploy. I flip the
project mode to Release and rebuild the project which creates the
projects DLL file from my code-behind files. I created a setup project
and created a setup using the .aspx files, not my .vb files, and the bin
folder. Copied the setup files onto a CD and installed it at the
client's site on their internal network. So good so far.

Of course, the client does some testing and discovers some issues, and
also wants some changes. I have 2 types of changes, interface (.aspx
files) and coding (.vb files).

Now the way I read the documentation, to update the .aspx files, all I
have to do is copy them into the web folder. The next time a user hits
that page, the .net runtime will notice the change and recompile.
Correct me if I'm wrong. If that's the case, updating the user interface
is easy.

It's the change to coding that I'm not sure about. I make a change to on
of my code-behind pages. When I do a rebuild, I get a new project DLL in
the bin directory. Now here is my main question: What do I need to do to
get this new DLL into production?

Does it work like the .aspx pages? Copy the new DLL into the production
BIN folder, overwriting the original? Do I have to regsvr32 the dll?
Stop and start the web server? Rebuild the Setup project and do a
complete reinstall?

Thanks!

Cris Brady
Ensuredmail - Security Made Simple
Chief Technical Architect
www.ensuredmail.com
Click here to reveal e-mail address

Reply to this message...

Kailas Tare

>>Does it work like the .aspx pages?
Yes

>>Copy the new DLL into the production BIN folder, overwriting the
original?=20
Yes

>>Do I have to regsvr32 the dll?
No.=20

>>Stop and start the web server?=20
No

>>Rebuild the Setup project and do a complete reinstall?
Depends, if you want to reinstall everything. The best approach I take,
it the XCopy deployment. I just ftp the changed .aspx pages in
appropriate directories and a dll in bin directory on production server.
The aspnet_wp.exe immeidately recognizes the change and loads the new
version of your dll in memory. All current ongoing requests are still
served by your old dll, but all new requests will be served by the new
version of your dll. You do not need to restart IIS or register
anything. This is why I love .Net.

But, say if you just want to change a part of your classes, I compile
them into seperate modules and ship to production as and when they are
changed. We have multiple team members working on different parts of one
web project. We compile group of related classes as modules and ship
them, instead of shipping full DLL.

I hope this will help.

Regards,
Kailas.

-----Original Message-----
From: cris brady [mailto:Click here to reveal e-mail address]
Sent: Friday, July 26, 2002 9:12 AM
To: aspngconfig
Subject: [aspngconfig] How to update deployed apps?

-- Moved from [aspngfreeforall] to [aspngconfig] by Sheik Yerbouti
<Click here to reveal e-mail address> --

Hi, I have some questions regarding updating of deployed ASP.Net
applications. I've read the documentation and can't seem to get a handle
on it.

I have a .Net web application. I developed and tested it in my local
environment. Version 1 looks good to go, time to deploy. I flip the
project mode to Release and rebuild the project which creates the
projects DLL file from my code-behind files. I created a setup project
and created a setup using the .aspx files, not my .vb files, and the bin
folder. Copied the setup files onto a CD and installed it at the
client's site on their internal network. So good so far.=20

Of course, the client does some testing and discovers some issues, and
also wants some changes. I have 2 types of changes, interface (.aspx
files) and coding (.vb files).

Now the way I read the documentation, to update the .aspx files, all I
have to do is copy them into the web folder. The next time a user hits
that page, the .net runtime will notice the change and recompile.
Correct me if I'm wrong. If that's the case, updating the user interface
is easy.

It's the change to coding that I'm not sure about. I make a change to on
of my code-behind pages. When I do a rebuild, I get a new project DLL in
the bin directory. Now here is my main question: What do I need to do to
get this new DLL into production?

Does it work like the .aspx pages? Copy the new DLL into the production
BIN folder, overwriting the original? Do I have to regsvr32 the dll?
Stop and start the web server? Rebuild the Setup project and do a
complete reinstall?

Thanks!

Cris Brady
Ensuredmail - Security Made Simple
Chief Technical Architect
www.ensuredmail.com
Click here to reveal e-mail address
| [aspngconfig] member Click here to reveal e-mail address =3D YOUR ID
| http://www.asplists.com/asplists/aspngconfig.asp =3D JOIN/QUIT
| http://www.asplists.com/search =3D SEARCH Archives

Reply to this message...

Tim Shay

I'm currently having the same or a very similar problem. When I copy out changes to our production server, changes in the ASPX pages are visible, but codebehind changes do not take effect. I've gone so far as to delete all copies of the DLL (in temp folders, etc.), and the code bombs when the DLL is not found, but it continues to run code from the old DLL - I'm positive! Has anyone seen this, and know how to fix it? So far, it only seems to affect one application.
Thanks!

--------------------------------
From: Tim Shay

Reply to this message...

Cris Brady

Thanks Kailas!

Cris Brady
Ensuredmail - Security Made Simple
Chief Technical Architect
www.ensuredmail.com
Click here to reveal e-mail address

[Original message clipped]

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com