469,590 Members | 2,464 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,590 developers. It's quick & easy.

deploying and re-deploying ASP.Net applications

Here's is our configuration

..Net Framework 1.1, Windows 2000, AppCenter 200

Our developers use XCOPY to deploy to the AppCenter NLB cluster (obviously, to the node that is the controller

Scenario - they deploy Version 2.5 of Application "A" to the web server at 8AM. The application is now live and in use. At 9AM they decide they need to deploy Version 2.6 of Application "B" They XCOPY all necessary files to the web server, overwriting the existing Application "A" Version 2.5, with Version 2.6. These are both "private" assemblies, as should be intuitive from the XCOPY nature of the deployment.

Problem - often, in this situation users of the early versions are dropped, disconnected, session is closed. It was my understanding that .Net would allow users already using the previous version to continue until finished. Is this true? Am I reading this wrong? Is this only true of shared assemblies in the GAC.

Also, this article seems to indicate that Norton Anti-Virus may be to blame here?

http://support.microsoft.com/default...kb;EN-US;31614

Has anyone else experienced this? How to your developers deploy ASP.Net applications?
Nov 18 '05 #1
2 1061
"Tom N" <no****@npt.nuwc.navy.mil> wrote in message
news:F9**********************************@microsof t.com...
Here's is our configuration:

.Net Framework 1.1, Windows 2000, AppCenter 2000

Our developers use XCOPY to deploy to the AppCenter NLB cluster (obviously, to the node that is the controller)
Scenario - they deploy Version 2.5 of Application "A" to the web server at 8AM. The application is now live and in use. At 9AM they decide they need
to deploy Version 2.6 of Application "B" They XCOPY all necessary files to
the web server, overwriting the existing Application "A" Version 2.5, with
Version 2.6. These are both "private" assemblies, as should be intuitive
from the XCOPY nature of the deployment.
Problem - often, in this situation users of the early versions are dropped, disconnected, session is closed. It was my understanding that .Net
would allow users already using the previous version to continue until
finished. Is this true? Am I reading this wrong? Is this only true of
shared assemblies in the GAC.
Also, this article seems to indicate that Norton Anti-Virus may be to blame here?
http://support.microsoft.com/default...b;EN-US;316148

Has anyone else experienced this? How to your developers deploy ASP.Net

applications?

When certain files are changed, the web application is restarted. Among
other things, when you change web.config (not user.config!) or the .dll of
your web application, the application will restart.
--
John Saunders
John.Saunders at SurfControl.com
Nov 18 '05 #2
Yes, that's what I figured, and that's what Norton AV seems to cause by scanning web.config.
Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Nel | last post: by
4 posts views Thread by Craig Bailey | last post: by
1 post views Thread by Chris | last post: by
11 posts views Thread by James | last post: by
4 posts views Thread by Alan Walkington | last post: by
1 post views Thread by John Ryan | last post: by
10 posts views Thread by James | last post: by
8 posts views Thread by Beowulf | last post: by
1 post views Thread by joost | last post: by
3 posts views Thread by presspley | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.