<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Just Another Web Application : customisation</title><link>http://blogs.technet.com/jasbro/archive/tags/customisation/default.aspx</link><description>Tags: customisation</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>PSA: Are your customised site definitions supported?</title><link>http://blogs.technet.com/jasbro/archive/2007/12/19/psa-are-your-customised-site-definitions-supported.aspx</link><pubDate>Wed, 19 Dec 2007 06:06:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2658707</guid><dc:creator>jasbro</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.technet.com/jasbro/comments/2658707.aspx</comments><wfw:commentRss>http://blogs.technet.com/jasbro/commentrss.aspx?PostID=2658707</wfw:commentRss><description>&lt;P&gt;We (Microsoft) have lots published guidance on customising SharePoint for your own specific needs. We provide lots of built-in site definitions for various purposes, but sometimes you need to tweak those to suit your own scenario. But are your tweaks supported?&lt;/P&gt;
&lt;P&gt;Well that depends.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If you've modified a built-in site definition directly, &lt;STRONG&gt;you are in an unsupported state&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;If you've copied an existing site definition, &lt;EM&gt;then modified the copy&lt;/EM&gt;, &lt;STRONG&gt;you're supported&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Why is this important? Well, a couple of reasons.&lt;/P&gt;
&lt;P&gt;One: we may want to release an update to an existing site definition as part of a service pack or feature pack. This will stomp all over your changes and no doubt you'll be an unhappy bunny about it.&lt;/P&gt;
&lt;P&gt;Two:&amp;nbsp;every so often a case trickles&amp;nbsp;into support&amp;nbsp;where a customer has tried to run an upgrade or migration, and it's failing because of a tweaked&amp;nbsp;built-in site defintion. Eseentially, the upgrade program is utterly baffled that the site def doesn't just upgrade the way it expects. Yes, you will most likely have big problems upgrading a site in which&amp;nbsp;built-in site definitions have been customised.&lt;/P&gt;
&lt;P&gt;So you may find it prudent to check KB 898631&amp;nbsp; when planning custom site or area definitions:&lt;/P&gt;
&lt;P&gt;&lt;A class="" title="KB 898631 on sharepoint customisation support" href="http://support.microsoft.com/kb/898631/en-us" mce_href="http://support.microsoft.com/kb/898631/en-us"&gt;Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services, in SharePoint Portal Server 2003, and in Office SharePoint Server 2007&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;PS: Premier Support here in Sydney &lt;STRONG&gt;IS HIRING&lt;/STRONG&gt;. We're after SharePoint Support Engineers for both development and admin&amp;nbsp;- please feel free to get in touch through the blog and I can get you referred. When I have a public link I'll update to reflect that.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2658707" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jasbro/archive/tags/sharepoint/default.aspx">sharepoint</category><category domain="http://blogs.technet.com/jasbro/archive/tags/development/default.aspx">development</category><category domain="http://blogs.technet.com/jasbro/archive/tags/customisation/default.aspx">customisation</category><category domain="http://blogs.technet.com/jasbro/archive/tags/site+definitions/default.aspx">site definitions</category><category domain="http://blogs.technet.com/jasbro/archive/tags/supportability/default.aspx">supportability</category></item></channel></rss>