[Mono-bugs] [Bug 55978][Wis] Changed - NumberFormatInfo error running an aspx page

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by chris@turchin.net.

http://bugzilla.ximian.com/show_bug.cgi?id=55978

--- shadow/55978	2004-06-27 08:57:51.000000000 -0400
+++ shadow/55978.tmp.630	2004-06-27 09:23:03.000000000 -0400
@@ -296,6 +296,40 @@
 in <0x002eb> ExecuteHandlerState:Execute ()
 in <0x00084> StateMachine:ExecuteState
 (System.Web.HttpApplication/IStateHandler,bool&)
 
 
 
+
+------- Additional Comments From chris@turchin.net  2004-06-27 09:23 -------
+as I mentioned to gonzalo on 2004-06-22:
+
+the following bug
+                                                                     
+                                                  
+http://bugzilla.ximian.com/show_bug.cgi?id=55978
+                                                                     
+                                                  
+was gone for quite a while but i updated from cvs today and it seems
+to have regressed in my blogx app:
+                                                                     
+                                                  
+http://turchin.homelinux.net/blogx/Default.aspx
+                                                                     
+                                                  
+it also occurs in the session1.aspx  test from the test webapp
+included with xsp from cvs:
+                                                                     
+                                                  
+http://turchin.homelinux.net/test/session1.aspx
+
+
+--END
+
+in fact, to me it appears as if two webapps which both use sessions
+have problems. the test/ asp.net webapp that comes with xsp from cvs
+runs fine together with the blogx/ webapp on my server. only when i
+try using the session test page do i see the problem. with other
+webapps that use the session from the beginning, i see this problem
+immediately (e.g. they don't run at all, just return a stack trace).
+
+hope that helps.