everytime publish our .net app on azure, users bein logged off , sign in again, our users won't understand. user sessions implemented using simplemembership provider.
is there way keep user sessions alive, after update our app?
i think have misunderstood publishing does. when publish application create new instance of w3wp.exe process. web process application memory stored (keeping simple). if publish creating new instance , old getting destroyed.
all sessions lost.
for example, every time publish website, make change web.config. cause application unload , iis recycle.
causes:
web.configchangesbin foldercontent change- manual
iisapplicaiton pool recycle
if need keep sessions alive should @ session-state modes
Comments
Post a Comment