﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>  Karl Prosser(MVP)</title>
    <description>This blog covers an eclectic range of powershell related topics. Many are focused around getting the most out of the scripting language, object model and pipeline, but also I will venture into the world of C# cmdlets and PowerPhell Hosting, and from time to time cover aspects of our products - PowerShell Analyzer and PowerShell Plus</description>
    <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/BlogId/10/Default.aspx</link>
    <language>en-US</language>
    <webMaster>do-not-reply@powershellcommunity.org</webMaster>
    <pubDate>Tue, 06 Jan 2009 00:08:01 GMT</pubDate>
    <lastBuildDate>Tue, 06 Jan 2009 00:08:01 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>PowerShell Analyzer like execution hotkeys for PS CTP3 ISE.</title>
      <description>&lt;p&gt;PowerShell CTP3 ISE - Integrated Scripting environment has inherited many ideas and features from PowerShell analyzer including multiple runspaces,editors, a smaller immediate input area and output pane, however it doesn’t have the output visualizers of PSA nor the super fast RTS like execution control of PSA.&lt;/p&gt;
&lt;p&gt;However Microsoft in their wisdom has made ISE rather extensible through the $PSISE variable, and many people already have added some very cool functionality to ISE through these.&lt;/p&gt;
&lt;p&gt;When I first demo’d what was then MSH analyzer to Microsoft back in the first few months of 2006, the feature that seemed to stand out the most to the team was the ability to select an area of code and just run that. Thankfully that level of execution control is now in ISE as F6, but I wanted more, so i’m going to share with you a script that build a few months ago to add a couple of features.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;F7 run the current physical line.&lt;/u&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/95/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/95/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=95</guid>
      <pubDate>Sun, 04 Jan 2009 03:14:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=95</trackback:ping>
    </item>
    <item>
      <title>Help us decide which PowerShell tool to release next.</title>
      <description>&lt;p&gt;SURVEY: &lt;a href="http://spreadsheets.google.com/viewform?key=pgTpVBomNgDwUA9uQNRKAbw&amp;amp;hl=en"&gt;http://spreadsheets.google.com/viewform?key=pgTpVBomNgDwUA9uQNRKAbw&amp;amp;hl=en&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Taking an app from an internal application to a shrink-wrap ready for &lt;br /&gt;
the masses state is a lot of work, and updating/supporting/marketting &lt;br /&gt;
a product even more so. So after the huge sucess of PowerShell Plus &lt;br /&gt;
which is now safe in Idera's hands we need your help to decide what we &lt;br /&gt;
are going to release next. We plan to release some free projects, even &lt;br /&gt;
some opensource apps, but will likely look at productizing a project &lt;br /&gt;
so we can continue to feed our families. Please take the time to take &lt;br /&gt;
our survey &lt;br /&gt;
&amp;#160;&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/94/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/94/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=94</guid>
      <pubDate>Sat, 20 Dec 2008 00:58:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=94</trackback:ping>
    </item>
    <item>
      <title>Portable PowerShell - v1 and v2 side by side - even on Server Core.</title>
      <description>&lt;p&gt;So I've loved portable apps from time memorial and have valued making my own apps as portable as possible - XCOPY friendly.
&lt;div class="wlWriterSmartContent" id="scid:5737277B-5D6D-4f48-ABFC-DD9C333F4C5D:5e95055d-a592-48bb-9238-9d72349b123f" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px"&gt;&lt;embed src="http://www.vimeo.com/moogaloop.swf?clip_id=1185791&amp;amp;server=www.vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=&amp;amp;fullscreen=1" width="320" height="200" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" mce_src="http://www.vimeo.com/moogaloop.swf?clip_id=1185791&amp;amp;server=www.vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=&amp;amp;fullscreen=1"&gt;&lt;/embed&gt;&lt;br /&gt;
&lt;a href=&amp;quot</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/92/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/92/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=92</guid>
      <pubDate>Wed, 18 Jun 2008 05:15:00 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=92</trackback:ping>
    </item>
    <item>
      <title>Fast New PSCustomObject.</title>
      <description>&lt;p&gt;Given the context on the last few posts. I've made a simple helper method in C# that can take a simple powershell hashtable and create a PSCustomObject based on it. Here is an example of how you can call it.&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/91/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/91/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=91</guid>
      <pubDate>Wed, 18 Jun 2008 05:12:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=91</trackback:ping>
    </item>
    <item>
      <title>generating a "PropertyBag" aka PScustomObject in C#</title>
      <description>&lt;p&gt;Based on the performance testing and work being done by &lt;a href="http://karlprosser.com/coder/2008/06/12/getting-serious-about-performance-in-powershell/"&gt;&lt;font color="#2153aa"&gt;myself&lt;/font&gt;&lt;/a&gt; , &lt;a href="http://thepowershellguy.com/blogs/posh/archive/2008/06/11/powershell-performance-series-part-1-warming-up.aspx"&gt;&lt;font color="#2153aa"&gt;mow&lt;/font&gt;&lt;/a&gt; , &lt;a href="http://bsonposh.com/"&gt;&lt;font color="#2153aa"&gt;Brandon Shell&lt;/font&gt;&lt;/a&gt; and others the question has come up what is the quickest way to generate a PSCustomObject, whether in script , on in C#, and how do you even do it in C#?&lt;/p&gt;
&lt;p&gt;Some typical ways of doing in PowerShell have been either something like the following trick:&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/90/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/90/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=90</guid>
      <pubDate>Wed, 18 Jun 2008 05:08:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=90</trackback:ping>
    </item>
    <item>
      <title>Getting serious about performance in PowerShell.</title>
      <description>&lt;p&gt;I've spend a lot of time in the past looking at the performance of PowerShell but have never gotten around to blogging about it. However it has become quite a hot button among MVPs and others in recent days and we've been busy testing and comparing the speeds different techniques in PowerShell in both V1 and V2.&lt;/p&gt;
&lt;p&gt;In V1 there seems to be extreme slowdowns when invoking cmdlet, functions, any type of scriptblock and when using the pipeline. If you...&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/89/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/89/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=89</guid>
      <pubDate>Thu, 12 Jun 2008 05:23:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=89</trackback:ping>
    </item>
    <item>
      <title>SnapInini - Lite portable SnapIns with no need of registration/installation.</title>
      <description>&lt;p&gt;One thing that has bothered me about true cmdlets in contrast scripts is that they lived in SnapIns and couldn't be deployed with xcopy as scripts can because SnapIns required Registration/Installation. I build my own way to deal with this need some time ago, and thought that I'd start a blog series covering it. I call them Snapininis or SnapIn-Lites. A good thing is you can achieve the same end result in PowerShell V2 with modules - but that is V2 and a while away from being released, and then even further away from being fully deployed.&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/88/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/88/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=88</guid>
      <pubDate>Sat, 07 Jun 2008 08:32:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=88</trackback:ping>
    </item>
    <item>
      <title>Determining what version of PowerShell your script is running in.</title>
      <description>&lt;p&gt;Many people recently have asked how to determine programatically what version of PowerShell their script is running in. Well in version two there is a $psversiontable variable, but this sadly isn't in V1. All is not lost though, as you can write a simple function to return a version object for v1. Below is a quick function that I wrote that I have been using for the last year or so.&amp;#160;&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/87/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/87/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=87</guid>
      <pubDate>Wed, 04 Jun 2008 06:40:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=87</trackback:ping>
    </item>
    <item>
      <title>PowerShell Analyzer 1.0 and PowerShell Plus Beta Available for free.</title>
      <description>PowerShell Analyzer 1.0 is finally released. For a week or two we consider this a "soft" launch, just in case there is some major issue that eluded our testing, but we are pretty confident its stable. 
Additionally, if you have already used your 45 Day trial, we have EXTENDED it another 45 days.
PowerShell Plus is now available with a 45 Day trial as well, and Additionally its available fully free for Non Commercial use as well.
</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/50/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/50/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=50</guid>
      <pubDate>Sat, 08 Dec 2007 09:52:49 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=50</trackback:ping>
    </item>
    <item>
      <title>Back in BlogLand</title>
      <description>Finally my main blog is back in Business. I had gotten discouraged with my previous web host and abundant comment spam, and just plain being busy. But now with the help of an updated WordPress, new Host and Windows Live Writer all should be good.</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/49/Default.aspx</link>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/49/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=49</guid>
      <pubDate>Sat, 08 Dec 2007 09:21:29 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=49</trackback:ping>
    </item>
  </channel>
</rss>