Bug 3245 - DateTimeOffset.ParseExact throws "Invalid format string" for round-trip format
Summary: DateTimeOffset.ParseExact throws "Invalid format string" for round-trip format
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 2.10.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-06 19:42 UTC by Andreas Sommer
Modified: 2012-09-11 10:26 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Demo of the problem (1.28 KB, text/plain)
2012-02-06 19:42 UTC, Andreas Sommer
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Andreas Sommer 2012-02-06 19:42:56 UTC
Created attachment 1320 [details]
Demo of the problem

Please have a look at the attached example program. It contains multiple examples that don't work, and a working example with Parse instead of ParseExact. This is probably related to #992 ("DateTime.ParseExact disregards valid format string").

ParseExact with the format string "o" (roundtrip format) throws the FormatException "Invalid format string". As there are multiple throw statements with the same message, I couldn't find out from the 2.10.8 source code what the problem seems to be.
Comment 1 Marek Safar 2012-02-07 05:15:04 UTC
Already fixed in master