<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>How we use XPath in IIS PowerShell namespace</title><link>http://blogs.iis.net/sergeia/archive/2008/08/28/use-of-xpath-in-iis-powershell-namespace.aspx</link><description>IIS 7 configuration API's were designed as DOM: you always have to start from top level data structure and work your way to the data you need, either collection element or child element attributes. It is quite annoying model when you are building generic</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Extension cmdlets for IIS – done right way</title><link>http://blogs.iis.net/sergeia/archive/2008/08/28/use-of-xpath-in-iis-powershell-namespace.aspx#3011945</link><pubDate>Tue, 17 Mar 2009 05:06:57 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:3011945</guid><dc:creator>Blog:\&gt;_</dc:creator><description>&lt;p&gt;.body_text { font-family: arial, helvetica, sans-serif; font-size: small; } .code { font-size: small;&lt;/p&gt;
&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=3011945" width="1" height="1"&gt;</description></item></channel></rss>