|
Hello, when we was checking to upgrade to visual studio 2012 we noticed that SessionManager doesn't work, we don't know exactly if its because the new IIS or the framework it self, so my question is should we start upgrading or we should wait till dataobjects.net team do some work? (i mean if we upgrade will we face many problems?) |
Hello Ahmad, could you please clarify what you mean by 'SessionManager doesn't work', i.e. you get an exception or something behaves not like you expect?
Anyway it's worth checking if you accidentally switched between WebDev.WebServer (aka Cassini) and IIS / IIS Express during migration. Those have different Web.config layout for registering IHttpModule implementations (e.g. SessionManager).
Hello Denis, Visual studio 2012 uses IIS Express as the default development server and i uses it.
i use the settings defined in web.config for visual studio 2010 web application(IIS 7.5), but when running the application, Session.Current always equal null, though i do the same settings i done for IIS 7.5 web application.
also i need to know if i will face any other problem in upgrade (perhaps you can till me of any resource exist on the web to make the upgrade easier). thanks
Is there any chance that your old setup uses IIS in classic mode and new setup in integrated mode?
Classic mode uses
system.web/httpModulessection for registering http modules, whereas integrated mode usessystem.webServer/modulessection.