I'll get straight into it, one of my pet peeves is working with `DateTime` it's more than likely my lack of understanding when it comes to `cultures` `timezones` and globalization.

Within my App, that is used on international level, I'm trying to figure out the best approach to build a function that will handle all formats irrespective of passed in format.

I suppose at the moment I'm not entirely sure, why I have a specific format that will not parse into a date, which is passed in via a client.

This is all in test for the time being, but never the less a pain in the beep...

At the moment, I'm trying to convert `en_gb` dates and also a `standard ISO format` Snippet of code attached.

```
string[] formats = {
    "d/M/yyyy h:mm:ss tt", 
    "d/M/yyyy h:mm tt",
    "dd/MM/yyyy hh:mm:ss", 
    "d/M/yyyy h:mm:ss",
    "d/M/yyyy hh:mm tt", 
    "d/M/yyyy hh tt",
    "d/M/yyyy h:mm",
    "d/M/yyyy h:mm",
    "dd/MM/yyyy hh:mm", 
    "dd/m/yyyy hh:mm",
    "yyyy-MM-dd'T'HH:mm:sszzz",
    "dd/MM/yyyy hh:mm:ss UTC"
};

if (DateTime.TryParseExact(val, formats, 
    CultureInfo.CurrentCulture, 
    DateTimeStyles.AllowWhiteSpaces, out dt))
{
    return dt;
}

```

So if I may ask, why does `13/06/2017 10:25:00 UTC` parse but `27/06/2017 16:11:00 UTC` fails (returns false).

I feel I may have been staring at this for too long.

Really appreciate a nudge in the right direction...