{"version":"1.0","provider_name":"Scripting Blog [archived]","provider_url":"https:\/\/devblogs.microsoft.com\/scripting","author_name":"Doctor Scripto","author_url":"https:\/\/devblogs.microsoft.com\/scripting\/author\/the-scripting-guys\/","title":"2014: A PowerShell Year in Perspective - Scripting Blog [archived]","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"VYytLAArSO\"><a href=\"https:\/\/devblogs.microsoft.com\/scripting\/2014-a-powershell-year-in-perspective\/\">2014: A PowerShell Year in Perspective<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/devblogs.microsoft.com\/scripting\/2014-a-powershell-year-in-perspective\/embed\/#?secret=VYytLAArSO\" width=\"600\" height=\"338\" title=\"&#8220;2014: A PowerShell Year in Perspective&#8221; &#8212; Scripting Blog [archived]\" data-secret=\"VYytLAArSO\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script type=\"text\/javascript\">\n\/* <![CDATA[ *\/\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/devblogs.microsoft.com\/scripting\/wp-includes\/js\/wp-embed.min.js\n\/* ]]> *\/\n<\/script>\n","thumbnail_url":"https:\/\/devblogs.microsoft.com\/scripting\/wp-content\/uploads\/sites\/29\/2020\/10\/dr_scripto.jpg","thumbnail_width":102,"thumbnail_height":150,"description":"Summary: Richard Siddaway discusses the growth of Windows PowerShell in 2014. Microsoft Scripting Guy, Ed Wilson, is here. Today, Honorary Scripting Guy and Windows PowerShell MVP, Richard Siddaway looks at the world of Windows PowerShell in 2014&#8230; The Scripting Guy asked me if I&rsquo;d like to review 2014 from a Windows PowerShell perspective. This is [&hellip;]"}