<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Cory Peters</title>
	
	<link>http://corypeters.net</link>
	<description>Adventures with SharePoint</description>
	<lastBuildDate>Mon, 23 Jan 2012 17:12:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CoryPeters" /><feedburner:info uri="corypeters" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>CoryPeters</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Modifying WSP Files Directly / Manually</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/hspg1MG5smE/</link>
		<comments>http://corypeters.net/2012/01/modifying-wsp-files-directly-manually/#comments</comments>
		<pubDate>Fri, 20 Jan 2012 14:40:14 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Office 365 Grid]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Feature]]></category>
		<category><![CDATA[Office 365]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[SharePoint Server 2007]]></category>
		<category><![CDATA[Tip]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=1000</guid>
		<description>Here&amp;#8217;s a common issue: You export a site as a template, save down your WSP file, browse out to your client environment and prepare to upload your WSP but you receive an error that looks something like this: After some hunting you come to find out that your source environment had Project Server installed and ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/hspg1MG5smE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2012/01/modifying-wsp-files-directly-manually/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2012/01/modifying-wsp-files-directly-manually/</feedburner:origLink></item>
		<item>
		<title>Office 365 Root Site Collection Bug</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/APqR48xfKq0/</link>
		<comments>http://corypeters.net/2011/12/office-365-root-site-collection-bug/#comments</comments>
		<pubDate>Thu, 29 Dec 2011 15:44:52 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Office 365 Grid]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Office 365]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=986</guid>
		<description>Just a quick tip here. You cannot use the Publishing Portal to create root site collections in Office 365. According to Microsoft support this option may be removed in the future as the site collection provisioning process hangs. If you do happen to accidently use the Publishing Portal as your root site collection then you ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/APqR48xfKq0" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/12/office-365-root-site-collection-bug/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/12/office-365-root-site-collection-bug/</feedburner:origLink></item>
		<item>
		<title>The Windows PowerShell Command Builder</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/outjWpu0ZXM/</link>
		<comments>http://corypeters.net/2011/10/the-windows-powershell-command-builder/#comments</comments>
		<pubDate>Wed, 12 Oct 2011 22:52:17 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Office 365 Grid]]></category>
		<category><![CDATA[Office 365]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SharePoint Foundation 2010]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>
		<category><![CDATA[Tip]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=952</guid>
		<description>Have you learned PowerShell yet? If not, you&amp;#8217;re way behind. What if there was a tool that allowed you to view all of the commands that were available for SharePoint Foundation 2010, SharePoint Server 2010 and Office 365 in a way that was intuitive, task oriented and visual? What if this tool was web accessible ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/outjWpu0ZXM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/10/the-windows-powershell-command-builder/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/10/the-windows-powershell-command-builder/</feedburner:origLink></item>
		<item>
		<title>A Few JavaScript/jQuery Best Practices</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/_iNfWCjmKyU/</link>
		<comments>http://corypeters.net/2011/09/a-few-js-jquery-best-practices/#comments</comments>
		<pubDate>Thu, 29 Sep 2011 13:00:00 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[Thoughts]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=924</guid>
		<description>I recently completed a pretty good size HTML5, JavaScript, SharePoint 2010 application for mobile devices. I got the opportunity to use some fairly young technologies so had to dig or in some cases determine my own best practices. Here&amp;#8217;s where I ended up after the dust settled. 1. Use Frameworks Choose your poison but there ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/_iNfWCjmKyU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/09/a-few-js-jquery-best-practices/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/09/a-few-js-jquery-best-practices/</feedburner:origLink></item>
		<item>
		<title>Timer Jobs Not Working</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/ULtU3mYal_s/</link>
		<comments>http://corypeters.net/2011/06/timer-jobs-not-working/#comments</comments>
		<pubDate>Wed, 29 Jun 2011 03:04:18 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[SharePoint Server 2007]]></category>
		<category><![CDATA[SSP]]></category>
		<category><![CDATA[Timer Jobs]]></category>
		<category><![CDATA[Tip]]></category>
		<category><![CDATA[Windows SharePoint Services 3.0]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=917</guid>
		<description>We recently had a VERY strange issue with a client. This specifically was a disaster restore where the previous environment was poorly documented. Due to a total hardware failure new hardware was provisioned&amp;#8230; and that&amp;#8217;s where the fun begins. We were able to get SharePoint installed and get Reporting Services fully configured in integrated mode ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/ULtU3mYal_s" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/06/timer-jobs-not-working/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/06/timer-jobs-not-working/</feedburner:origLink></item>
		<item>
		<title>Nintex Workflow Tips &amp; Tricks</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/guZoobQrG34/</link>
		<comments>http://corypeters.net/2011/05/nintex-workflow-tips-tricks/#comments</comments>
		<pubDate>Mon, 23 May 2011 16:54:45 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Nintex Workflow]]></category>
		<category><![CDATA[SharePoint Foundation 2010]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=898</guid>
		<description>I&amp;#8217;ve been working with Nintex products for a few years now with great success. In my experience their workflow and reporting products are very solid but sometimes performing complex solutions can have a learning curve. Here are a couple of tips and best practices I&amp;#8217;ve learned over the years. During development disable Safe Looping Browse ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/guZoobQrG34" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/05/nintex-workflow-tips-tricks/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/05/nintex-workflow-tips-tricks/</feedburner:origLink></item>
		<item>
		<title>Managed Account Password Management</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/FFzOSMIJ90c/</link>
		<comments>http://corypeters.net/2011/03/managed-account-password-management/#comments</comments>
		<pubDate>Tue, 29 Mar 2011 23:03:55 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=892</guid>
		<description>I like the idea of SharePoint managing my passwords for me. I like the idea of no human knowing what the service account passwords are so that they are forced to log into their own admin account before modifying anything within SharePoint. The problem with this is that I just can&amp;#8217;t trust SharePoint to handle ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/FFzOSMIJ90c" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/03/managed-account-password-management/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/03/managed-account-password-management/</feedburner:origLink></item>
		<item>
		<title>Adding a View More Link to Web Parts</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/v_2J7klJl9c/</link>
		<comments>http://corypeters.net/2011/01/adding-a-view-more-link-to-web-parts/#comments</comments>
		<pubDate>Thu, 13 Jan 2011 04:33:02 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Branding]]></category>
		<category><![CDATA[Content Query Web Part]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[SharePoint Foundation 2010]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=741</guid>
		<description>When we&amp;#8217;re designing or mocking up a SharePoint Intranet, Extranet or Internet we always talk about content roll up. SharePoint does a great job with content roll up OOTB (within the same Site Collection at least) using the Content Query Web Part. However, any time you show the client the power of the Content Query ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/v_2J7klJl9c" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2011/01/adding-a-view-more-link-to-web-parts/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2011/01/adding-a-view-more-link-to-web-parts/</feedburner:origLink></item>
		<item>
		<title>Who is Rich Haddock?</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/zXS0jepUz0s/</link>
		<comments>http://corypeters.net/2010/12/who-is-rich-haddock/#comments</comments>
		<pubDate>Mon, 06 Dec 2010 16:14:10 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>
		<category><![CDATA[Thoughts]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=717</guid>
		<description>I was recently working on some new blog topics and a possible white paper when I stumbled across this little bit in SharePoint 2010. If you have worked in-depth with SharePoint publishing then you will undoubtedly be familiar with the Reusable Content capabilities within SharePoint. So, when playing around with Reusable Content in SharePoint 2010 I found ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/zXS0jepUz0s" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2010/12/who-is-rich-haddock/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://corypeters.net/2010/12/who-is-rich-haddock/</feedburner:origLink></item>
		<item>
		<title>Adding Links to Site Settings</title>
		<link>http://feedproxy.google.com/~r/CoryPeters/~3/KwaGEftvCWQ/</link>
		<comments>http://corypeters.net/2010/12/adding-links-to-site-settings/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 16:11:50 +0000</pubDate>
		<dc:creator>Cory Peters</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[CodePlex]]></category>
		<category><![CDATA[Feature]]></category>
		<category><![CDATA[Series]]></category>
		<category><![CDATA[SharePoint Foundation 2010]]></category>
		<category><![CDATA[SharePoint Server 2010]]></category>

		<guid isPermaLink="false">http://corypeters.net/?p=701</guid>
		<description>In part 1 I covered Adding Links to Central Administration but now it&amp;#8217;s time to take a look at how I added links to the site settings screen for my CodePlex creation SharePoint 2010 Site Styles. Note that the process is almost identical. So the final goal is something that looks like this: Just like ...&lt;img src="http://feeds.feedburner.com/~r/CoryPeters/~4/KwaGEftvCWQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://corypeters.net/2010/12/adding-links-to-site-settings/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://corypeters.net/2010/12/adding-links-to-site-settings/</feedburner:origLink></item>
	</channel>
</rss>

