{"id":10841,"date":"2006-04-25T12:17:56","date_gmt":"2006-04-25T12:17:56","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2006\/04\/25\/using-culture-culture-culture-script-scriptblock\/"},"modified":"2019-02-18T13:25:04","modified_gmt":"2019-02-18T20:25:04","slug":"using-culture-culture-culture-script-scriptblock","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/using-culture-culture-culture-script-scriptblock\/","title":{"rendered":"Using-Culture -Culture culture -Script {scriptblock}"},"content":{"rendered":"

One of the traditional challenges with scripting is dealing with different CULTURES.  Imagine the case where you are writing a script and you’ll have to parse datetime string from different cultures.  If it was just one culture, you could set the process culture and be done with it.  Here is a function that allows you to run a portion of a script in a different culture:<\/font><\/p>\n

Function Using-Culture (
[System.Globalization.CultureInfo]$culture = (throw “USAGE: Using-Culture -Culture culture -Script {scriptblock}”),
[ScriptBlock]$script= (throw “USAGE: Using-Culture -Culture culture -Script {scriptblock}”))
{
    $OldCulture = [System.Threading.Thread]::CurrentThread.CurrentCulture
    <\/font>trap 
    {
        [System.Threading.Thread]::CurrentThread.CurrentCulture = $OldCulture
    }<\/font>
    [System.Threading.Thread]::CurrentThread.CurrentCulture = $culture
    Invoke-Command $script
    [System.Threading.Thread]::CurrentThread.CurrentCulture = $OldCulture
}<\/font><\/p>\n

Here is an example of it working:<\/p>\n

[332:]MSH> using-culture ar-IQ {get-date}<\/font><\/p>\n

30 \u062a\u0634\u0631\u064a\u0646 \u0627\u0644\u062b\u0627\u0646\u064a, 2005 09:01:38 \u0635<\/font><\/p>\n

[332:]MSH> using-culture ar-IQ {$global:d=[DateTIme]::Parse(“30 \u062a\u0634\u0631\u064a\u0646 \u0627\u0644\u062b\u0627\u0646\u064a, 2005 09:01:38 \u0635”)}
[332:]MSH> $d<\/font><\/p>\n

Wednesday, November 30, 2005 9:01:38 AM<\/font><\/p>\n

[332:]MSH> using-culture de-de {get-date}<\/font><\/p>\n

Mittwoch, 30. November 2005 09:02:29
[332:]MSH> using-culture de-de {$global:d=[DateTIme]::Parse(“Mittwoch, 30. November 2005 09:02:29”)}
[332:]MSH> $d<\/font><\/p>\n

Wednesday, November 30, 2005 9:02:29 AM<\/font><\/p>\n

<\/font> <\/p>\n

The great thing about this approach is that you can put any code you want into the script block.  It can be a single cmd, a pipeline or a full script.<\/font><\/p>\n

Enjoy!<\/font><\/p>\n

Jeffrey P. Snover [MSFT]<\/font><\/p>\n

[Edit: Monad has now been renamed to Windows PowerShell. This script or discussion may require slight adjustments before it applies directly to newer builds.<\/i>]<\/p>\n","protected":false},"excerpt":{"rendered":"

One of the traditional challenges with scripting is dealing with different CULTURES.  Imagine the case where you are writing a script and you’ll have to parse datetime string from different cultures.  If it was just one culture, you could set the process culture and be done with it.  Here is a function that allows you to […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10841","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"

One of the traditional challenges with scripting is dealing with different CULTURES.  Imagine the case where you are writing a script and you’ll have to parse datetime string from different cultures.  If it was just one culture, you could set the process culture and be done with it.  Here is a function that allows you to […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10841","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=10841"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10841\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=10841"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=10841"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=10841"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}