SharePoint solution package

Before answering this question, let me explain what isSharePoint solution package(Solution pack ).

When developing on SharePoint, we will find that a developed function or set of functions can be divided into the following aspects:

1. customized Sharepoint list templates and Their instances

SharePoint provides flexible data storage containers: lists, so we often use these lists (or document libraries) to implement our functions.

In addition, sometimes the feature we are developing is used to manage some lists or document libraries.

2. customized Website templates

It is possible that the features we develop are very large, so a special SharePoint website is required for presentation.

3. Web Components

We can place functional web components on the desired page to assemble and present the final UI to the user.

4. Event Processing Program

In addition to using Web Components for UI interaction with users, we may also need to monitor changes in website data, so event handlers are sometimes indispensable.

5. Custom operations

SharePoint provides a large number of management operation buttons, menus, and links on its own interface. The developed content may also need to load its own operations in it.

6. other things ............

In summary, we can see that a self-developed SharePoint solution may contain a variety of features (this feature refers to SharePoint's "Features", that is, feature ), assembly, Web Part attribute description file, list or website template, etc. How can I install a large amount of content in a Sharepoint environment at one time without having to deploy it one by one?

The answer is: SharePoint solution pack)

A SharePoint solution package is a file suffixed with. WSP. This file is actually a. cab file, which includes all the small aspects of a major function mentioned above.

During deployment, you only need to execute the command line operation:

Stsadm-O addsolution-filename <path> \ yoursolution. WSP

This solution package is added to the Sharepoint Server Farm.

Go to the SharePoint management center and select solution management on the "operations" tab to deploy the solution, all the functions and programs contained in them are published to the SharePoint website. Very convenient.

Back to the title of this article, how can we package our development project into a Sharepoint solution package to generate this. WSP file?

There are many examples. I often refer to the example of andrew. use vs2005and makecab.exe to generate the WSP file:

Http://www.andrewconnell.com/blog/articles/UsingVisualStudioAndMsBuildToCreateWssSolutions.aspx

However, this method is a little more complicated.

Du Wei often uses the method of writing the heap configuration file by himself, or using some third-party cab generation tools for packaging.

However, this cannot avoid directly operating on XML files that are not complex but complicated.

Yesterday, I searched randomly and found a recently released open-source command line tool wspbuilder. its author is Carsten keutmann (but it seems that sharepointblogs and sharepointu have crashed together)

I tried it today and it is very useful. With this command line tool, you only need to arrange all the files involved in your solution according to the final deployment path, and then run the command line program, the WSP file is automatically generated.

Example:

I developed a small feature that involves a Web component and a list of custom fields.

First, compile the DLL of the Web part and describe the webpart file of the Web Part attribute.

Then generate the feature that can automatically generate the custom list (this process will be introduced to you in the next blog article)

The packaging process is as follows:

1. Create a folder named "favouriteresult ".

2. Create the "12" and "80" directories under this folder.

3. Under the "80" directory, I placed the bin directory with the above DLL and the wpcatalog directory with the webpart file.

4. Under the "12" directory, create the "template \ features" path and put the self-developed feature in this path.

5. Copy two wspbuilder files (one EXE and one DLL) to the favouriteresult folder.

6、double-click wspbuilder.exe.

7. the WSP file I need is generated.

The next operation is to use the command line to add the WSP file, and then deploy this solution in the management center.

Note: Because this command line tool is developed by a foreigner (like a German tool), the path used to generate the WSP file (in this example, the favouriteresult folder) cannot contain Chinese characters. However, this is an open-source project. If you are interested, you can also improve it.

In short, this program is the best SharePoint tool I have recently encountered. If you need to create a Sharepoint solution package, try it.

From: http://blog.csdn.net/wendy1001/archive/2007/08/14/1743031.aspx