[Mono-bugs] [Bug 78618][Nor] Changed - DateTime.Parse format exception with milliseconds

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Jun 13 22:47:33 EDT 2006


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 atsushi at ximian.com.

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

--- shadow/78618	2006-06-13 13:02:13.000000000 -0400
+++ shadow/78618.tmp.24410	2006-06-13 22:47:33.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 78618
 Product: Mono: Class Libraries
 Version: 1.1
 OS: GNU/Linux [Other]
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: atsushi at ximian.com                            
 ReportedBy: dbrain at bandwidth.com               
 QAContact: mono-bugs at ximian.com
@@ -52,6 +52,9 @@
 Could be an issue for other users as this time format is the default for
 Ngpsql/Postgresql timestamp.
 
 ------- Additional Comments From atsushi at ximian.com  2006-06-13 13:02 -------
 Any serious DateTime user should use ParseExact() instead. Parse()
 could fail depending on the culture.
+
+------- Additional Comments From atsushi at ximian.com  2006-06-13 22:47 -------
+fixed in svn (r61689).


More information about the mono-bugs mailing list