Bug 29789 - DateTime.TryParseExact fails on "dd/MM/yy"
Summary: DateTime.TryParseExact fails on "dd/MM/yy"
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: 4.0.0
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-05-06 07:51 UTC by Mikkel Kruse Johnsen
Modified: 2015-05-07 02:28 UTC (History)
2 users (show)

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

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:

Description Mikkel Kruse Johnsen 2015-05-06 07:51:40 UTC
Mono 4.0.1 Fails on this:

"DateTime.TryParseExact ("01/08/16", "dd/MM/yy", null, DateTimeStyles.None, out dt))"

where as this works fine.

"DateTime.TryParseExact ("01-08-16", "dd-MM-yy", null, DateTimeStyles.None, out dt))"

It all worked in Mono 3.12
Comment 1 Alexander Köplinger 2015-05-06 10:31:56 UTC
If you run this with LC_ALL=en_US it works, but it fails with e.g. LC_ALL=de_DE.

The reason is you pass null for the "provider" parameter, which means according to MSDN:

> If provider is null, the CultureInfo object that corresponds to the current culture is used.

It's not a bug, just pass CultureInfo.InvariantCulture instead of null and your code should work fine.
Comment 2 Mikkel Kruse Johnsen 2015-05-07 02:28:19 UTC

Was a different between Mono and .NET and since Mono now uses .NET source code it failed.