Prepare for a new SharePoint Project

The proposal of a Sharepoint-related project was sent out last Friday, waiting for the result... Whether or not you can win the bid is unknown. But you have already started to make some preparations. Although there were many contacts with SharePoint before. However, experience is mainly concentrated in features development and webpart development. There are not many intersections with this project. So we should make some preparations before that.

This project implements an Intranet website for internal use by a company. To use SharePoint as the basis, you must implement the following content:

• The interface is consistent with the existing website Style
• Several Simple workflows
• Forum
• Investigation
• Create a page for each Department (page content to be determined)
• CMS

The content is quite simple. Although we made suggestions based on wss3.0 and moss2007 in proposal, I estimate that the customer will choose wss3.0. Because at present, they do not see any need to use the special features of moss2007. Even if they are available in the future, they can also port the sites based on wss3.0 to moss2007.

The content of the entire site is not much, and the functions are not complex. Most of the content can be satisfied by the internal features of WSS. The discussion provided by WSS is insufficient for the Forum.
Because SharePoint-based webpart development is too inefficient and cannot be visualized, it will lead to a longer development period. In addition, there is no requirement for page components to be reused in the demand. Therefore, we should adopt SharePoint designer + Visual Studio to directly develop webpage.
Sharepoint is also advanced. It runs Based on ASP. NET. So we will use SharePoint designer to directly create a page on the SharePoint site, design the page, and then create a new class library project in Visual Studio to serve as the background of the self-built WebCode.

The following is what we have learned today:
1. design the page with SharePoint designer and write the page background code with Visual Studio. It is feasible and can be combined perfectly.
2. to use this method, you must use "inherit =" in the @ page command at the front-end of the page to specify the fully qualified name of the background class inherited from the class library.
3. to use this method, copy the Program set of the Class Library to the bin directory or GAC of the corresponding site.
3. to use this method, you must go to the Web. add the class library to the safe control list in the config file
4. to use this method, each time you add a control on the page, you must declare a control object with the same name in the background without initialization during the declaration. But must be declared as protected or public.
5. by using this method, you can add a Sharepoint control on the page and operate the control in the background code.
6. to use this method, you must Reference System in the class library project. web assembly and SharePoint assembly.
7. with this method, you can directly declare the protected void page_load function to perform some operations during page loading.
8. by using this method, you can override the onerror function to avoid the default SharePoint exception page. However, you must use the server. call context after the getlasterror () function gets the error content. clearerror () to identify the previous exception
9. no large and common ASP.. NET development. Only the page and background code are put in different editors.