Comments on: JSON from PowerShell (but why?) http://huddledmasses.org/json-from-powershell-but-why/ You can do more than breathe for free... Fri, 27 Apr 2012 12:40:09 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Joel 'Jaykul' Bennett http://huddledmasses.org/json-from-powershell-but-why/comment-page-1/#comment-213771 Joel 'Jaykul' Bennett Tue, 08 Dec 2009 17:06:48 +0000 http://huddledmasses.org/?p=1353#comment-213771 Well, the thing is, I didn't have to do much work to convert JSON to XML, because the JSON parser in the .Net framework is actually an implementation of the XmlReader class. So considering how easy (relatively speaking) it is to work with XML in PowerShell, that conversion is a no-brainer. Outputting a hashtable or a custom object would actually require me to ... you know ... parse stuff myself. Well, the thing is, I didn’t have to do much work to convert JSON to XML, because the JSON parser in the .Net framework is actually an implementation of the XmlReader class. So considering how easy (relatively speaking) it is to work with XML in PowerShell, that conversion is a no-brainer. Outputting a hashtable or a custom object would actually require me to … you know … parse stuff myself.

]]> By: Hal Rottenberg http://huddledmasses.org/json-from-powershell-but-why/comment-page-1/#comment-213761 Hal Rottenberg Tue, 08 Dec 2009 03:30:40 +0000 http://huddledmasses.org/?p=1353#comment-213761 Generally, I agree with you that bolt-ons for JSON are pretty silly. KISS, that's what JSON is about. Of course, I think that you are crazy for converting JSON to XML, that is overkill, too. :) I'd be happy with just a hashtable. Well, I can imagine that a PSObject would be cool if you planned on writing some ETS methods or something. Otherwise, a hashtable is fine. Generally, I agree with you that bolt-ons for JSON are pretty silly. KISS, that’s what JSON is about. Of course, I think that you are crazy for converting JSON to XML, that is overkill, too. :) I’d be happy with just a hashtable. Well, I can imagine that a PSObject would be cool if you planned on writing some ETS methods or something. Otherwise, a hashtable is fine.

]]>