Question about updating live asp.net website

[emblewembl]

Hi all,

I'm involved in a members based website which has been redeveloped from classic ASP and now uses ASP.Net. The results are great but there is one major downside to all of this. When we make any change to any of the code behind we have to upload the new dll to the bin folder of the live application. This results in all logged in members being 'kicked out'. Is this there anyway of stopping this happening? It's kind of frustrating to think that code changes could be made with classic ASP without any disruption to logged in members...... Interested in other thoughts/suggestions on this topic.

Thanks.

i love chocolate

 

[Joulius]

Re-uploading the dll and/or saving the web.config file results in application being restarted, so all Application and Session objects are disposed. The only solution that comes into my mind right now to not lose the members' login status is to change the login method -> local cookie that holds the info about login status and the login verification made against that cookie. Not very elegant, but will solve the login problem, but will not solve your problems regarding SessionState (in-memory . I'm not very sure if, keeping the Session into a SQL DB, will solve the SessionState.

 

[Smeat]

Another option is to update the server at a time when the site is not being used. If there is never a guaranteed time for this then you might want to prevent users loggin in until the server has been updated, perhaps showing a 'Site under routine maintenance' statement so that users are aware that the site is not broken.

HTH

Smeat

 

[emblewembl]

Thanks guys, we already put up a site under maintenance page but just wondered if there was a better solution. Thanks for all input.

i love chocolate

 

[jkelly2956]

You can change the page directive for the asp.net page to not use the codebehind feature.

<%@ Page Language="vb" AutoEventWireup="false" src="tt.aspx.vb" Inherits="tt"  %>

This only helps on asp.net pages and any other classes will need to be compiled and the dll updated.