<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>SPoshMod Issue Tracker Rss Feed</title><link>http://www.codeplex.com/SPoshMod/WorkItem/List.aspx</link><description>SPoshMod Issue Tracker Rss Description</description><item><title>Created Task: Modify functions to use patterns &amp; practices</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=775</link><description>Some example&amp;#58;&lt;br /&gt;&lt;br /&gt;For cmdlets that handle persisted objects&amp;#58;&lt;br /&gt;Use only - Get, Set, New, and Remove verbs&lt;br /&gt;&lt;br /&gt;Get cmdlet can retrieve one or more objects.&amp;#160; If no parameters are specified, Get cmdlet should return all available instances of the object.&lt;br /&gt;There are three&amp;#160;&amp;#91;optional&amp;#93; parameters&amp;#58;&lt;br /&gt;-Identity&amp;#58;&amp;#160; returns the object with the specified Identity value.&amp;#160; Should allow user to specify object identity such as GUID AND URL &amp;#40;use can send either&amp;#41;.&amp;#160; Parameter should also accept partical string inputs like &amp;#39;&amp;#42;&amp;#39; where possible matches are returned.&lt;br /&gt;-Filter&amp;#58; Typically for Cmdlets that return more than a 1000 items.&amp;#160; Limits results to those that match specified query expression.&amp;#160; Used for server-side queries only, client side should use Where-Object &lt;br /&gt;-Limit&amp;#58; sets the maximum number of objects to be returned.&amp;#160; When limit is reached, user should see warning.&amp;#160; &amp;#34;ALL&amp;#34; should return all possible values&lt;br /&gt;&lt;br /&gt;Cmdlet nonuns&amp;#58;&amp;#160; should be singluar&amp;#160;and reflect the object that is returned&amp;#160; e.g.&amp;#160; Get-SPSite&amp;#160;&amp;#160; &amp;#40;instead of Get-SPSites&amp;#41;.&amp;#160; &lt;br /&gt;Use prefixes &amp;#38; suffixes to indicate value property&amp;#58;&amp;#160; MaxConnectionTimeOut&amp;#160;&amp;#160; or SiteBandwidthLimit&lt;br /&gt;&lt;br /&gt;Cmdlets should also have a supporting help entry &amp;#40;more on this later&amp;#41;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;More patterns &amp;#38; practices details later...but this is a rough idea of how the cmdlets should be built.&lt;br /&gt;</description><author>erickraus</author><pubDate>Mon, 02 Feb 2009 13:30:12 GMT</pubDate><guid isPermaLink="false">Created Task: Modify functions to use patterns &amp; practices 20090202013012P</guid></item><item><title>Closed Task: Create module manifest</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=747</link><description>Any experience with this&amp;#63;&lt;br /&gt;</description><author>erickraus</author><pubDate>Mon, 02 Feb 2009 05:19:36 GMT</pubDate><guid isPermaLink="false">Closed Task: Create module manifest 20090202051936A</guid></item><item><title>Commented Task: Create module manifest</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=747</link><description>Any experience with this&amp;#63;&lt;br /&gt;Comments: &lt;P&gt;Yes.&amp;nbsp; I moved this to Active/High.&amp;nbsp; I autogenerated a manifest with New-ModuleManifest cmdlet.&amp;nbsp; I added in Microsoft.SharePoint.dll as an Assembly dependency.&amp;nbsp; Do we want to keep this as a dependency?&amp;nbsp; I think there could be *some* people who may want to just use it for web services?&lt;/P&gt;&lt;br /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;br /&gt;&lt;P&gt;SPoshMod.psd1 has been added to my project&lt;/P&gt;</description><author>erickraus</author><pubDate>Mon, 02 Feb 2009 05:19:08 GMT</pubDate><guid isPermaLink="false">Commented Task: Create module manifest 20090202051908A</guid></item><item><title>Created Task: Create module manifest</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=747</link><description>Any experience with this&amp;#63;&lt;br /&gt;</description><author>cglessner</author><pubDate>Sun, 01 Feb 2009 12:44:24 GMT</pubDate><guid isPermaLink="false">Created Task: Create module manifest 20090201124424P</guid></item><item><title>Created Task: Figure out a Testing Approach</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=536</link><description>Figure out how to test this thing in a way that&amp;#39;ll work on multiple envs.  My first pass is probably to create a script that builds us a &amp;#39;test&amp;#39; site that we can perform actions on to validate the code works.&lt;br /&gt;</description><author>romangeeko</author><pubDate>Fri, 23 Jan 2009 12:51:07 GMT</pubDate><guid isPermaLink="false">Created Task: Figure out a Testing Approach 20090123125107P</guid></item><item><title>Created Issue: Support for CheckIn/Out</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=534</link><description>Add Checkin&amp;#47;out support for SPListItems&lt;br /&gt;</description><author>romangeeko</author><pubDate>Fri, 23 Jan 2009 12:47:39 GMT</pubDate><guid isPermaLink="false">Created Issue: Support for CheckIn/Out 20090123124739P</guid></item><item><title>Created Issue: Add IDispose Code</title><link>http://www.codeplex.com/SpoSh/WorkItem/View.aspx?WorkItemId=533</link><description>Add code to SPWeb, SPSite, ... to handle registering with the IDispose code&lt;br /&gt;</description><author>romangeeko</author><pubDate>Fri, 23 Jan 2009 12:44:09 GMT</pubDate><guid isPermaLink="false">Created Issue: Add IDispose Code 20090123124409P</guid></item></channel></rss>