Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 898631 - Last Review: May 13, 2010 - Revision: 5.0
Supported and unsupported scenarios for working with custom site definitions and custom area definitions in SharePoint 2003, 2007 and 2010
This article contains information about custom site definitions in Microsoft Windows SharePoint Services 2.0,Windows SharePoint Services 3.0, and SharePoint Foundation 2010. It also contains information about custom area definitions in Microsoft Office SharePoint Portal Server 2003,Microsoft Office SharePoint Server 2007 and SharePoint Server 2010. This article lists scenarios that are supported and scenarios that are not supported when you customize site definitions and area definitions.
Supported scenarios
When you work with custom site definitions or custom area
definitions, the following scenarios are supported:
- To create a custom site definition or a custom area
definition, you copy an existing site definition or an existing area
definition, and then you rename and modify the new site definition or the new
area definition. For more information about this supported method, visit the
following Microsoft Web site:
- You modify the .xml files and the .aspx files in a custom
site definition or in a custom area definition before you create new sites or
new portal areas by using the custom site definition or the custom area
definition.
- You deploy the custom site definition or the custom area
definition. That is, you create new sites or new portal areas by using the
custom site definition or the custom area definition. To modify the new sites
or the new portal areas that you created, you use one or more of the following
three supported methods:
- You modify the site or the portal area by using Microsoft Office FrontPage 2003, SharePoint Designer 2007, or SharePoint Designer 2010.
- You programmatically modify the site or the portal area
by using the SharePoint Portal Server object model or the Windows SharePoint
Services object model.
- You modify the site or the portal area by using
Microsoft Office FrontPage 2003.
Note These three methods are also supported methods to use if you want
to modify the Default.aspx page in the portal site. Microsoft does not support
using other methods to modify the Default.aspx page in the portal
site.
Unsupported scenarios
When you work with custom site definitions or custom area
definitions, the following scenarios are not supported:
For more information about the best practices for ensuring
application reusability and upgrade in SharePoint, visit the following Microsoft Web site:
For more information about templates and site definitions, visit
the following Microsoft Web sites:
For more information about schema files in site definitions,
visit the following Microsoft Web site:
For more information about custom templates, click the following article number to view the article in the Microsoft Knowledge Base:
825217Â
(http://kbalertz.com/Feedback.aspx?kbNumber=825217/
)
Overview of custom templates in SharePoint Portal Server 2003 and Windows SharePoint Services
For migration and upgrade information for SharePoint Server 2007 developers, visit the following Microsoft Web site:
For more information about the SharePoint Portal
Server object model and the Windows SharePoint Services object model, see the
Microsoft SharePoint Products and Technologies Software Development Kits
(SDKs). To view the SharePoint Products and Technologies 2003 SDK, visit the
following Microsoft Web site:
To view the SharePoint Products and Technologies 2007 SDK, visit the
following Microsoft Web site:
APPLIES TO
- Microsoft Office SharePoint Server 2007
- Microsoft Office SharePoint Portal Server 2003
- Microsoft Windows SharePoint Services 2.0
- Microsoft Windows SharePoint Services 3.0
- Microsoft SharePoint Foundation 2010
- Microsoft SharePoint Server 2010
| kbxml kbasp kbtshoot kbinfo KB898631 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate