Have session variables been optimised with .Net? Or is the best solution<BR>still to use a DB to store user state information?<BR><BR>All the best<BR><BR>RedI think it works better than asp, but you should still avoid it if possible. You can use cookies, viewstate, or choose to use session variables with a database(there is an option of storing session state in a database).Hey Red, <BR><BR>Here is an article regarding the changes to session state between classic and .net. Many of the issues with sessions have been resolved, but they should still be used sparingly.<BR><BR>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspnet/html/asp12282000.asp<BR><BR>])ryThanks Guys
<BR><BR>I think I will stick with using a State Object that acceses my SQL Database - It's just that we have a lot of legacy systems that are riddled with Session Variables :-/<BR><BR>Cheers<BR><BR>RussAlso try and use ViewState whenever possible. This way the data is stored on the page and does not touch either of the servers.Hi Guys<BR><BR>Can I add to the question about state. <BR>I am writing an online banking application and need to pass data from one page to the next. At the moment I parked the data in session but I feel it is not ideal.<BR><BR>does the<BR><form id="mainform" method="post" runat="server"page2.aspx"><BR>Listboxes, textboxes etc<BR></form><BR><BR>work? Why doesnt it just send all its data to page2.aspx as in plain ASP? it doesnt seem to go to the page2 in my code. If it is not designed like in ASP what is the recommended way of doing this<BR><BR>Thanks<BR><BR><BR><BR>
