<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sharepoint-2010 on When Pigs Fly</title><link>http://derekcp.com/tags/sharepoint-2010/</link><description>Recent content in Sharepoint-2010 on When Pigs Fly</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 30 Nov 2012 00:00:00 +0000</lastBuildDate><atom:link href="http://derekcp.com/tags/sharepoint-2010/index.xml" rel="self" type="application/rss+xml"/><item><title>Provisioning files in a feature in the root directory</title><link>http://derekcp.com/posts/provisioning-files-in-a-feature-in-the-root-directory/</link><pubDate>Fri, 30 Nov 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/provisioning-files-in-a-feature-in-the-root-directory/</guid><description>&lt;p&gt;I was recently tasked with migrating code that was written for 2007 in a feature. The files that were originally provisioned in the feature we deployed to the root folder of the feature. The code had already been upgraded to SharePoint 2010. I needed to create a wsp using Visual Studio 2010 and package it as a feature. Out of the box when you create a new Module in VS 2010 you get a subfolder so for example you create the feature called Feature1 and a module called Mod1. The default deployment path is 14\templates\features\feature1\mod1\file.txt. What I needed was feature1\mod1\file.txt. I tried modifying all the attributes in the elements.xml file and was not able to get the files to the correct location.&lt;/p&gt;</description></item><item><title>SharePoint Saturday New Hampshire Deck Posted</title><link>http://derekcp.com/posts/sharepoint-saturday-new-hampshire-deck-posted/</link><pubDate>Mon, 24 Sep 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/sharepoint-saturday-new-hampshire-deck-posted/</guid><description>&lt;p&gt;The deck for my SharePoint Saturday New Hampshire has been posted to &lt;a href="http://www.slideshare.net/derekcashpeterson/intro-tospia-branding"&gt;SlideShare&lt;/a&gt;. Thanks to everyone who came to my session.&lt;/p&gt;</description></item><item><title>Custom Search MasterPage for SharePoint 2010</title><link>http://derekcp.com/posts/custom-search-masterpage-for-sharepoint-2010-5/</link><pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/custom-search-masterpage-for-sharepoint-2010-5/</guid><description>&lt;p&gt;I wish I could say that I was smart enough to have figured this one out for myself but I can&amp;rsquo;t. I was working on my first custom branded SharePoint 2010 site and the search screen was all messed up. The navigation was displaying doubled. It turns out that the search center out of the box used minimal.master. This uses the placeholders that are in v4.master in different way so the search box ends up in the breadcrumb pull down. At any rate, &lt;a href="http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html"&gt;Randy Drisgill&lt;/a&gt; wrote a great and very easy to follow post about how to modify your custom masterpage to the search center. It took me longer to create the feature to deploy the new search masterpage than it did to make the modifications.&lt;/p&gt;</description></item><item><title>Defaulting Preview Pane To First Item in List</title><link>http://derekcp.com/posts/defaulting-preview-pane-to-first-item-in-list/</link><pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/defaulting-preview-pane-to-first-item-in-list/</guid><description>&lt;p&gt;A client of ours wanted to use the preview pane for a list view. The default view of the preview pane has the right hand pane blank. You need to select an item or hover an item from the left pane to populate the right pane. The client wanted the right hand pane to have the right hand pane default to first item in the list.&lt;/p&gt;
&lt;p&gt;UPDATE 10/21/2013: It looks like when people are doing a copy and paste of the code that the double quotes &amp;quot; are getting converted to smart quotes. When you copy and paste make sure that you change any of the single or double quotes to plain text.&lt;/p&gt;</description></item><item><title>Powershell Commands for Installing Solutions and Features</title><link>http://derekcp.com/posts/powershell-commands-for-installing-solutions-and-features/</link><pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/powershell-commands-for-installing-solutions-and-features/</guid><description>&lt;p&gt;As a SharePoint 2007 developer I have many of the common stsadm commands committed to memory. While stsadm still works in SharePoint 2010 in favor of moving to proficiency in the latest version of the technology here are some of the powershell commands that I use on a daily basis. With that said, I usually create a batch file that runs these commands so that I only need to run one command to get the features updated and features activated.&lt;/p&gt;</description></item><item><title>Themes for your SharePoint 2010 environment</title><link>http://derekcp.com/posts/themes-for-your-sharepoint-2010-environment-4/</link><pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/themes-for-your-sharepoint-2010-environment-4/</guid><description>&lt;p&gt;I spend most of my time working on custom branding projects using SharePoint. These are great projects and tend to be large custom dev projects. They also tend to have larger budgets. But what about those clients that want a different look and feel but don&amp;rsquo;t have the large budget. Use a custom theme or template. There are several packaged themes out there for SharePoint 2010 that provide you with a look and feel that while not unique does change the way that SharePoint looks. The themes also provide some level of customization either during the purchase process or after. One of the key things to take into account is that there is probably going to be some level of customization to be done after the fact.&lt;/p&gt;</description></item><item><title>When Pigs Fly...</title><link>http://derekcp.com/posts/when-pigs-fly-2/</link><pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/when-pigs-fly-2/</guid><description>&lt;p&gt;“Good design is obvious. Great design is transparent.” - Joe Sparano&lt;/p&gt;
&lt;p&gt;I have had the good fortune to work with some very talented designers in my career. They have taught me about the difference between good design and great design. The good is something that when you look at it makes you say wow. The great is when you don’t even realize that it was designed well; when something is so intuitive that you instantly know how to find what you are looking for or know how it works. As a web developer it was my job to translate the vision of the designer into SharePoint and make sure that what is great in PhotoShop is great in SharePoint. It is that pixel perfect philosophy that I bring to my work integrating design into SharePoint.&lt;/p&gt;</description></item></channel></rss>