Beware the Ides of March—But by Who's PowerShell Calendar?

re: Beware the Ides of March—But by Who's PowerShell Calendar?

rjcox — Fri, 16 Mar 2012 10:55:01 GMT

@Richard.Siddaway

Having saved me the need to note the locale dependency in the article's example, there is a solution: Use ISO format. This is unambiguous with a four digit year:

PS> [datetime]"2012-08-10"

will always give you midnight 10 August 2010.

re: Beware the Ides of March—But by Who's PowerShell Calendar?

K_Schulte — Thu, 15 Mar 2012 20:10:13 GMT

Hi Ed,

a good short article that explains some details of dates.

It is quite ingteresting what we can do with dates and we should pay attention to date formats!

@Richard: Right! Living in Germany, I encounter the same problems, you do!

But there is one thing, I can asure you ... you typed in: [datetime]"51/3/12"

This will never be a valid date ... not in the UK, not in the US and not here :-)))

Klaus (Schulte)

re: Beware the Ides of March—But by Who's PowerShell Calendar?

Richard.Siddaway — Thu, 15 Mar 2012 19:14:37 GMT

Hi quick comment on international dates.

Regarding

[datetime]"3/15/12"

The syntax shows month/day/year and results in

Thursday, March 15, 2012 12:00:00 AM

Living in the UK I'm more used to day/month/year but if I try

PS> [datetime]"51/3/12"

Cannot convert value "51/3/12" to type "System.DateTime". Error: "String was not recognized as a valid DateTime."

I have to do

[datetime]"3/15/12"

Over the years I have found that its safer for me to do

[datetime]"15 March 2012"

as it always works.

This is caused by the culture settings in PowerShell

PS> Get-Culture

LCID Name DisplayName

---- ---- -----------

2057 en-GB English (United Kingdom)

PS> Get-UICulture

LCID Name DisplayName

---- ---- -----------

1033 en-US English (United States)