My experience in SharePoint (2), sharepoint

My experience in SharePoint (2), sharepoint
Zookeeper

This article is the second part of my SharePoint experience. For the first part, see

My experience in SharePoint (1)

After finishing that project, I had some knowledge of SharePoint 2003. However, I have not been working on SharePoint for a few years. I have worked on many ASP. NET projects, all of which are outsourced projects.

 

Later, I left my company and wanted to earn more, so I changed to a bigger city. When I was looking for a job, I met a company. During the interview, I talked to the interviewer about my previous SharePoint project. He was very interested. Then I was admitted.

 

Some of the company's businesses are outsourced to SharePoint. At that time, SharePoint has released version 2007. The name is also changed. Previously called SharePoint Portal Server, which was defined as a Portal website and renamed MicrosoftSharePoint Office Server in version 2007. The positioning has been significantly improved. In addition, MCMS has never released a new version. Even if you search for MCMS on the Microsoft website, the link is linked to the SharePoint webpage.

 

I was assigned a customized project team for the customer. I slowly discovered that the development of SharePoint has been in full swing, and many foreign companies are using it, although almost no one knows about SharePoint in China. In addition, the comparison between version 2007 and Version 2003 has greatly changed, and the style of the entire GUI has changed. Some concepts in section 2003 are no longer available, such as Area Web.

 

However, I am surprised that although the two versions are quite different, the SharePoint API remains unchanged. Even today, the APIs in Microsoft. SharePoint. dll have not changed. It can be seen that the architecture of SharePoint itself is very good.

 

I have worked on a SharePoint 2003 project before, so it is faster to get started after entering the project team. At that time, we made some pages and webparts for our customers. At that time, SharePoint customization was completely different from the current one, because Visual Studio didn't have a template for SharePoint development at that time. Therefore, everything is done manually, including writing scripts to package them into a cab file, manually writing scripts to deploy solution, activating feature, and Restarting IIS. Every debugging is troublesome and inefficient.

(Unlike Visual Studio, simply press F5 ).

 

Later I came up with some tips. It was very difficult to create a WebPart in SharePoint 2007. Later I had a buddy on the Internet who developed a WPBuilder tool, which greatly improved the development speed. At that time, I also felt that foreign programmers would find a solution to the problem and then share it unselfishly. This may be the reason why open source is very popular outside China.

 

Since then, it has been in the SharePoint industry.