13. August 2010 09:55
I like using WSPBuilder for my SharePoint projects and if you do much SharePoint development, it is an absolute must have tool. One of the issues I ran into with the IDE in Visual Studio 2008 is when you create the WSP it was giving it a name that I did not care for. If you renamed it and then try using the deploy command you will get an error. Thanks to “Bill Simser | Name that WSP” blog, it turns out it very simple to define the naming of the file.
He does it a bit different and probably explains it better than me; the concept is the same. I keep a folder of code that I often reuse (i.e. config files). I copied over the WSPBuilder.exe.config file to this folder; my root config file was at “C:\Program Files\WSPTools\WSPBuilderExtensions”. I added the key
<add key="WSPName" value="myName.Space.Project.wsp" />
to inside the app settings node. Now when I start a new project, I just use the Add Existing file dialog in Visual Studio to add the file to root of the project. Like most config files, the local will append/override the parent file. Now I just edit the value to get the name I want. By the way you will see some other options in the config file that are commented out; that may prove to be usefull.
Thanks Bill for this so very important piece of information.