From: http:// OS .51cto.com/art/201006/206561.htm
However, after some time of Sharepoint development, Sharepoint is still a new thing for me. In retrospect, when I first came into contact with Sharepoint, I found a lot of information everywhere, however, I still don't know how to start Sharepoint development, and I have searched many articles on Cnblog. However, for a newbie like me, I am still confused by the cloud. so I came up with a series of getting started with Sharepoint. this series will start from the most basic, so that even a person who never knows Sharepoint knows how to do Sharepoint development through reading this series.
Tip: I am a newbie to Sharepoint (not humble here), so there may be many shortcomings in the article. I hope the Sharepoint guys can correct me and I will keep updating it.
This article describes how to design and create your own Sharepoint Site.
Through Microsoft documents, we know there are many ways to create a custom Sharepoint site. But which method do we choose? What do we choose?
Purpose is the Purpose. purpose is the most critical factor. based on your intention, you can choose whether it is a simple custom site or an advanced custom site. for example, if you use a site for a group or to manage a small Project, you can choose a simple custom site, however, if a website is used by a company of thousands of people and has a large access volume every day, you can choose a highly-customized Site. In this case, if the functions provided by Sharepoint Server 2007 cannot be implemented, you need additional development functions. We can use other development tools, such as Visual Studio 2005.
Resources. resources include the Software section (Microsoft Office SharePoint Designer 2007 and Microsoft Visual Studio 2005) and hardware section. simple websites do not require a lot of additional resources. Sharepoint itself provides the ability to add web parts, customize view lists, and change the images on the home page. with Sharepoint Designer, you can also perform more complex customization, such as modifying Master pages and LayOut. however, the advanced website requires a lot of resources, such as more Farm to complete development and testing, and other development tools such as VS2005 to complete more functions.
In general, Personnel is about people. The larger the site, the more complicated the features require more people. It is easy to understand.
Next, let's take a look at the development approaches and advantages and disadvantages of various levels of websites.
Simple and customized websites
For simple Sharepoint Site. you can customize it directly in the browser. for example, a website used by a group includes: Team Logo, Calendar, Shared Documents, announcements, shared contacts, and some simple web parts. you can use all these functions provided by the site.
Intermediate custom site
For some simple functions, you can operate like customizing a simple Site. In addition, you can also use Sharepoint Designer 2007 (a tool for processing Sharepoint site) to process more advanced customization. for example, a website of an enterprise uses the home page to display the latest company News, and the Child site to display human resources information and some business data. this requires you to do more extra work:
. Custom Master Page
. Custom layouts to display different pages
. Custom CSS style
. Custom Data Display web part to display personal data
There are also some examples such as workflow, document management, and business intelligence.
Advanced website Customization
The target readers of this series are those who want to develop workflow, web part, document management, CSS, Master Page, layouts pages, and so on. the advanced Sharepoint site is some Internet sites that are widely used, have a large access volume, and have many businesses. these sites generally require user verification to customize site elements and special sites. therefore, developing such websites may require complex development, testing, and deployment environments. for example, develop and deploy data in another place. this requires a large team of requirement analysts, designers, developers, and testers.
This Guide describes two custom methods:
Author-centered method: In this method, the website elements created (including projects such as master pages and layout pages) you can use different methods to maintain and deploy website elements. This method accelerates content delivery.
A developer-centered method in which website elements (such as Web Components and workflows) and website projects (such as master pages, la S, and Cascading Style Sheets) are developed) use similar methods for maintenance and deployment. This provides a more rigorous maintenance method for typical website projects associated with software development.
In the author-centered method, the methods for creating, maintaining, and deploying website elements are different from those for developing websites.
The website elements created by using client applications running in a Web browser (such as Office SharePoint Designer 2007, Office Word 2007, or Office SharePoint Server 2007) create a website project (master page, layout, Web and Cascading Style Sheets) and its content pages, graphics, and other files. Content management (such as version control, check-in/checkout, and content approval) is based on the default document management feature in Office SharePoint Server 2007. Use the Web publishing feature (such as content deployment and website variants) in Office SharePoint Server 2007 to deploy all created website elements (including project and content pages ).
The developed website elements usually use Microsoft Visual Studio 2005 and Microsoft. NET Framework 3.0 to create custom development website elements for the website. Source code management and configuration management are processed by programs such as Visual Studio 2005 Team System. Pack custom development elements into functions and deploy them using the packaging and deployment functions of the Office SharePoint Server 2007 solution.
The author-centered method has the following advantages:
Use the content deployment feature in Office SharePoint Server 2007 to deploy custom projects, such as the master page and layout.
Accelerated content delivery because all content is directly managed in Office SharePoint Server 2010, not in a separate configuration management system. You can use the built-in content version control, check-in/check-out, and approval functions of Office SharePoint Server 2007.
It is usually easier to configure and deploy, because this method requires a low degree of customization of the development environment.
For an introduction to the use of author-centered methods, including examples of the various environments in use, see custom solutions.
Developer-centric approach
In the developer-centered method, you use different methods to create the website elements created and developed, but maintain the created and developed projects in the same configuration management system, and deploy it in a similar way.
The website elements created by the website element are divided into two types: the project (such as the master page and layout) and the website content (the webpage and image of the website) created by the framework in which the website content is displayed ). In a developer-centered approach, the project is developed in the development environment and maintained in the configuration management system that is the same as the Code website element. The project and encoding elements are packaged into the solution package, and then deployed to the production site, creation site, and test site. Website content is maintained by default using the document management function provided by Office SharePoint Server 2010 in the Creation Field. Both the project and website content use the content deployment function from the creation site deployment to the production site and test site.
The developed website elements are the same as those in the author-centric method. Generally, Microsoft Visual Studio 2005 and Microsoft. NET Framework 3.0 are used to create custom development elements for the website. You can use Visual Studio 2005 Team System or equivalent configuration management System to manage source code, binary files, and solution files. Pack custom development elements into functions and deploy them using the packaging and deployment functions of the Office SharePoint Server 2010 solution.
The developer-centric method has the following advantages:
Project and code are managed in the same configuration management system.
All custom elements of the website can be rebuilt and deployed from the configuration management system. This is useful in geographically distributed websites and disaster recovery.
A benchmark environment can be maintained for disaster recovery or rollback from program errors.
The test/integration environment and test environment can be deployed using production-level projects.
The developed and created elements are maintained using similar tools and processes.
The above is the development method selection in the Sharepoint development process.