Deploying to a live server

I don't think there is a best practice regarding this, it all depends on
your specific clientel and if it's acceptable to either risk gettings errors
for a short time or that the server is taken offline.

If you are going to wait for no visitors you are probably in for a long
wait, but I guess you could simply use the iis logs for this.

In asp.net 2.0 there is an easy way to close down the site remotely, all you
do is upload a file named App_offline.htm and then remove it after you are
done, of course, like I said, it all depends on wheter it's acceptable for
your specific users to take it down in the first place.

KL.


"Gary Homewood" <gary.homewood.DeleteThis@gmail.com> skrev i meddelandet
news:1162388431.283536.119570@m7g2000cwm.googlegroups.com...
> Hi
>
> I have an ASP.NET 1.1 web application that I need to deploy to a live
> IIS. I was wondering if anyone has any guidelines or best practices as
> to how to do this most effectively. A tool to remotely monitor the
> number of users connected to the website would be useful, so I know
> when there's no-one on the site I could stop it and deploy the new
> version. I was hoping there might be a better way of doing it. Any
> suggestuions gratefully received.
>
> Thanks.
>
 >> Stay informed about: Deploying to a live server 

Well, it's quite possible I guess to have a clustered server and update one
at a time, however I've gotten my share of errors on large sites as well so
I think they just update it like everyone else. If everything has been
properly tested on a development machine it shouldnt take long to update
even a large site.

A while ago I saw a video from the guys over at MS that handle their site,
not specifically about this but it was interesting hearing about how they
handle one of the worlds largest and most visited websites.

I can't seem to find it now but It's somewhere around this site, lots of
other interesting stuff there as well:
http://channel9.msdn.com/

KL.


"Gary Homewood" <gary.homewood.TakeThisOut@gmail.com> skrev i meddelandet
news:1162396991.845660.52910@i42g2000cwa.googlegroups.com...
> Thanks for that; I thought that would be the kind of answer I'd
> receive. On reflection, I think it's only really an issue during my
> online ordering process, which I can log directly, and which doesn't
> involve a huge number of users. Still, out of interest, I'd like to
> know how Amazon do it....
>
> Cheers
>
> Gary
>
> On Nov 1, 3:10 pm, "KL" <non....TakeThisOut@nowhere.com> wrote:
>> I don't think there is a best practice regarding this, it all depends on
>> your specific clientel and if it's acceptable to either risk gettings
>> errors
>> for a short time or that the server is taken offline.
>>
>> If you are going to wait for no visitors you are probably in for a long
>> wait, but I guess you could simply use the iis logs for this.
>>
>> In asp.net 2.0 there is an easy way to close down the site remotely, all
>> you
>> do is upload a file named App_offline.htm and then remove it after you
>> are
>> done, of course, like I said, it all depends on wheter it's acceptable
>> for
>> your specific users to take it down in the first place.
>>
>> KL.
>>
>> "Gary Homewood" <gary.homew....TakeThisOut@gmail.com> skrev i
>> meddelandetnews:1162388431.283536.119570@m7g2000cwm.googlegroups.com...
>>
>> > Hi
>>
>> > I have an ASP.NET 1.1 web application that I need to deploy to a live
>> > IIS. I was wondering if anyone has any guidelines or best practices as
>> > to how to do this most effectively. A tool to remotely monitor the
>> > number of users connected to the website would be useful, so I know
>> > when there's no-one on the site I could stop it and deploy the new
>> > version. I was hoping there might be a better way of doing it. Any
>> > suggestuions gratefully received.
>>
>> > Thanks.
>
 >> Stay informed about: Deploying to a live server