You searched for the word(s): userid:772532

More Search Options

RSS Available

• Re: Stateless Shared membervariables in VB.NET

  One of the main reasons why we're using SQL Server right now, is so that we can update the code without the session-data getting destroyed causing all the users to be logged out (plus it's a legacy from when we up until recently were using a Web Farm). Will the StateServer work like the SQL Server for software updates, or will a software update cause the StateServers data to be cleared? Have problems finding info about this through Google.

  Posted to State Management (Forum) by Phr34ker on 7/3/2008

• Re: Stateless Shared membervariables in VB.NET

  That's the way I have it right now to fix the problem that Shared caused. But this solution seems REALLY resource-demanding to me - unless Session caches the data. WHen I call Session["User"], the data is fetched and deserialized from the SQL Server. But I don't know if the Session-object temporarilly caches the deserialized object. If it does, this solution is a good alternative. But otherwise it means that it will have to fetch and deserialize every single time the User-object

  Posted to State Management (Forum) by Phr34ker on 7/3/2008

• Re: Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode...

  [quote user="santa_1975"] Serializing DataSet will be pretty heavy. Try to put your DataRow content into separate Session Variables like Session["UseName"] = <User Name value from the DataRow>; [/quote] And if you do, make sure to clean up the terrible mess that this will cause with all the persistent session-variables that will follow the user until his session is abandoned or times out, by calling Session.Remove( "nameOfTheProperty" ) on every single Session

  Posted to State Management (Forum) by Phr34ker on 7/3/2008

• Re: Stateless Shared membervariables in VB.NET

  It IS stored in a Session. Let me explain. When a user logs in, I have a User-property that serializes the user-object to a Session-variable (SQL Server Sessions), and also handles all the deserialization. But this means that as soon as the User-property is read, the data has to be read from the database and deserialized to the Session-object which then has to be typed and returned, and since this property is accessed at least 20 times on each page, that should in time create a serious bottleneck

  Posted to State Management (Forum) by Phr34ker on 7/3/2008

• Re: Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode...

  You can't serialize a DataRow, but I'm pretty sure you can serialize a DataSet. So fill a DataSet with the datarow and you should be fine. I'm not saying it's a GOOD solution, but it should work. Another option, is to simply create your own serializable class/structure and then transfer the data from the DataRow into the instance of the class/structure, then assign the instance to Session. THe reason it's working fine locally, is that you're not using Sql Server to store the

  Posted to State Management (Forum) by Phr34ker on 7/2/2008

• Stateless Shared membervariables in VB.NET

  Got a chock today, when I realised that Shared member-variables (VB.NET) in ASP.NET are persistent and (kind of) saved to the Application-object, which I REALLY don't want. In fact, this change in behaviour caused all the logged in users of the site to share the same user-object and cart, and things got really out of hand. So, how do I get a normal Shared variable which can be accessed without having an instance of the class, but still dies like any normal member-variable once the page has been

  Posted to State Management (Forum) by Phr34ker on 7/2/2008

• Re: Invalid postback or callback argument.

  In my case it originated from having a <form>-tag inside the <form runt="server">-tag - an old relic from an old HTML-page that taged along. Now, this doesn't apply to a Custom Control, but it might be the page he inserts the Custom Control on that has the same HTML-bug, in which case the control will fail.

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by Phr34ker on 2/25/2008

• Re: LinkButton Postback

  MY BAD! For some reason I called Request.QueryString instead of Request.Form, and I read through the code again, and again and again, but couldn't find the error. I guess I was blinded by my own stupidity, or something...

  Posted to Web Forms (Forum) by Phr34ker on 2/7/2008

• LinkButton Postback

  I've dynamically created a LinkButton, that should do a simple postback. But when I click the LinkButton, the Request.Form-collection is empty, and I really need some of the form data (that is not related to any ASP.NET-control). Is there something I have to to to enable PostBack, or is LinkButton not capable of posting back? The code I use to create the LinkButton: Dim lbtnAddPanel As New LinkButton lbtnAddPanel.ID = "lbtnAddPanel" AddHandler lbtnAddPanel.Click, AddressOf lbtnAddPanel_Click

  Posted to Web Forms (Forum) by Phr34ker on 2/7/2008
  Filed under: LinkButton eventhandler firing click vb.net Postback

• Re: invalid webresource request

  Adding it to AssemblyInfo.vb didn't work (VS complained immediatly, about WebResource not beeing a valid "Type"). But when I added: <Assembly: WebResource( "OnlineControls.AdvSearchControl_Ajax.js" , "text/x-javascript" )> just over the namespace-declaration of the page that used the resource, it worked perfectly.

  Posted to Custom Server Controls (Forum) by Phr34ker on 1/8/2008