DateTime.Parse...

[Kris11]

I recently found that if I pass in a date string like the this

DateTime.Parse("01-01/2002");

DateTime.Parse, parses it correctly and returns back 01/01/2002. Is this a documented behavior? Have you seen any documentation which discuss a behavior like this.

Just curious...

-Kris

 

[chiph]

.Parse() is pretty flexible, and it does a pretty good job most of the time, but I'm surprised it would accept something like that!

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[JurkMonkey]

I imagine MS is using Regex's that allow you to put any crap in the middle of a date tag as long as its not numeric and it will still work.

Try parsing 02!-..01/1995 and see if it goes. Now that would be amazing.

 

[JurkMonkey]

My sweet hoo hoo it's magic! It actually does work!

 

[NeilTrain]

Too bad SQL Server isn't as forgiving, I tried dumping the format in the RSS spit out by google news into a SQL DateTime and it fails (i.e. "Sun, 16 Oct 2005 04:10:43 GMT") had to DateTime.Parse().ToString() it, so no biggie. thank goodness for static methods