<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://k2underground.com/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/"><channel><title>PowerShell Wizard</title><link>http://k2underground.com/groups/powershell_wizard/default.aspx</link><description>The PowerShell wizard allows you to run PowerShell commands from your K2 process. The PowerShell commands are run on the K2 server itself. PowerShell must be installed on the K2 Server and on the K2 machine designing the K2 workflow (this is because of the assemblies required). The wizard allows users to specify input variables and output variables. With the normal Run-As feature, you can run the powershell in another users&amp;#39; context. Installation (if you build yourself): Build the solution i</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>V1.2 of PowerShell Wizard</title><link>http://k2underground.com/groups/powershell_wizard/media/p/41654.aspx</link><pubDate>Sat, 21 Jan 2012 12:19:41 GMT</pubDate><guid isPermaLink="false">1c9bda6b-c6e6-4e79-8d32-b70ad0011ef7:41654</guid><dc:creator>_cyclops_</dc:creator><description>&lt;p&gt;The V1.2 release improves the following:&lt;/p&gt;
&lt;p&gt;- System.Management.Automation assembly was taken from a directory on disk, this was changed when we &amp;#39;added&amp;#39; 32-bit support and was actually wrong in the first place. Now, it takes the assembly from the GAC, where it will be located. This also means the designer tools do not need the SDK anymore.&lt;/p&gt;
&lt;p&gt;- Upgrade AssemblyVersion to 1.2&lt;/p&gt;
&lt;p&gt;- Moved the CodeExtender files into another directory as the directory name was wrong.&lt;/p&gt;
&lt;p&gt;- Improved icons.&lt;/p&gt;
&lt;p&gt;- Very simple syntax error checking was added. This will now note very simple powershell errors. Because any word (or even a single character) can be a commandlet, it&amp;#39;s still looks very stupid if you enter &amp;quot;X&amp;quot; into the script dialog and it validates correctly.&amp;nbsp; X could be a commandlet (that you load at runtime) and can thus be valid powershell script. The script checking does however check if you had your quote&amp;#39;s correctly etc. Powershell simply does not provide more options to do better checking.&lt;/p&gt;
&lt;p&gt;- Error handling at runtime has been improved a little bit.&lt;/p&gt;</description></item><item><title>V1.0 - OLD - PowerShell Wizard Source Code</title><link>http://k2underground.com/groups/powershell_wizard/media/p/41564.aspx</link><pubDate>Thu, 05 Jan 2012 19:55:25 GMT</pubDate><guid isPermaLink="false">1c9bda6b-c6e6-4e79-8d32-b70ad0011ef7:41564</guid><dc:creator>_cyclops_</dc:creator><description>&lt;p&gt;The powershell wizard source code. Can be used to change or update the code. The source is compiled as well in release mode, so you can also use this to just install the project.&lt;/p&gt;</description></item></channel></rss>