<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Features on Matt Thornton</title>
    <link>http://localhost:1313/tags/features/</link>
    <description>Recent content in Features on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 05 Aug 2015 12:14:15 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/features/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint Features &#43; Renaming</title>
      <link>http://localhost:1313/tech/sharepoint/sharepoint-features-renaming/</link>
      <pubDate>Wed, 05 Aug 2015 12:14:15 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/sharepoint/sharepoint-features-renaming/</guid>
      
        <description>&lt;p&gt;This is a fun one. In some of our Visual Studio solutions we use the period character - “.” - for project naming which broadly reflects the namespaces in use.&lt;/p&gt;
&lt;p&gt;However, this causes issues for Visual Studio namely in the ability to rename features. So when you create a feature, it will adopt a default name of Feature1 and it&amp;rsquo;s not possible to rename it directly from within the solution.&lt;/p&gt;
&lt;p&gt;Fortunately, there&amp;rsquo;s a nifty workaround that does appear to work, without having to redo your solution/project structure and naming convention. Found via &lt;a href=&#34;http://stackoverflow.com/questions/7168852/visual-studio-2010-sharepoint-dev-tools-can-feature1-feature-be-renamed&#34;&gt;this post&lt;/a&gt;:&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>