Wspbuilder install

Instead of having to manually create a manifest. For this article, I will be downloading the Visual Studio Add-In, since that is the easiest way to use the tool. Installation of the tool is straightforward and consists of clicking the Next button a few times. You should now see some new options available within the Tools menu as illustrated below:. This folder represent the 12 hive in SharePoint. With this two files we will be building a custom content type. Replace the contents of feature.

We are now ready to build the WSP file. You should see some text in the output window and when all is done, we should have a WSP file in the root folder of our project. Fire up a command prompt and head over to that directory.

So if your solution builds 9 WSP's you need to do this 9 times. Usually there will be just one WSP per solution and just one post-build action code snippet written. Create a new build in TFS. Add additional reference paths. Open the TFSBuild. Then you can set this folder up as a network share and drop referenced assemblies in there as required.

Add a pre-build action if more than one WSP file in solution. With multiple WSP's you will find that if you don't follow Brian's instructions that the DLL's from the first projects that are build will make their way into the second and subsequent WSP files. With just one WSP you can skip this step. Mission accomplished. Below is a typical project hierarchy for a feature with some custom pages in Visual Studio:.

This allows WSPBuilder to build a. While building your feature project is fodder for another article in the interest of direction, you can see by the image that there are several sections for content. There are several ways to build a WSPBuilder-centric project, this is only one of many. To build your project, once you have completed development, you must have installed the Visual Studio plugin for WSPBuilder located here.

This builds a Sharepoint solution file in the root directory of your project.