In a word, no. <\/p>\n
I’m sure some of my fellow PowerShell MVP recipients and other enthusiasts will disagree. Certainly, you can<\/b> use the Framework from within PowerShell, and that’s a great capability to have. Sitting here today, there are many things which are most easily achieved using the Framework – not "easy," mind you, just "most easily" – such as pinging other computers, resolving DNS names, and so forth.<\/p>\n
But as support for PowerShell grows, more and more functionality will be exposed as consistently-named, easy-to-use cmdlets (in fact, both examples I just gave can be achieved using cmdlets from the PowerShell Community Extensions<\/a> – a perfect example of the evolution I’m talking about). Microsoft’s intent is that .NET is for developers; admins get cmdlets, which map .NET functionality to real-world admin tasks.<\/p>\n WMI is in a similar position. Today, there’s a lot you can ONLY do by using WMI directly. Over time, that will change as WMI becomes a more developer-centric API, and cmdlets become the way administrators work. Those cmdlets may use WMI behind the scenes, but you won’t really care.<\/p>\n So – can you be a PowerShell Super User, today, without the Framework? Well, probably not. But you can accomplish a heck of a lot, especially in PowerShell-ed products like Exchange, SCOM, SCVMM, and more. Over time, you’ll be able to administer AD, IIS, probably DNS and DHCP, and who knows what else, all using PowerShell cmdlets – not the Framework, and eventually not even WMI. So if you’ve heard that PowerShell is based on .NET and that you MUST learn .NET to be effective with PowerShell – well, that’s just not true. So jump in and start learning PowerShell<\/a> today – it’s just a shell, not a .NET Framework tool. <\/p>\n","protected":false},"excerpt":{"rendered":" In a word, no. I’m sure some of my fellow PowerShell MVP recipients and other enthusiasts will disagree. Certainly, you can use the Framework from within PowerShell, and that’s a great capability to have. Sitting here today, there are many things which are most easily achieved using the Framework – not "easy," mind you, just […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2,25],"tags":[169,170,28],"class_list":["post-428","post","type-post","status-publish","format-standard","hentry","category-general","category-windows-powershell","tag-net-framework","tag-learn","tag-powershell"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t