WSPBuilder (SharePoint WSP tool)

A patch adds the files *.SVC to replacement parameters process. See more details http://msdn.microsoft.com/en-us/library/ee231545.aspx and https://wspbuilder.svn.codeplex.com/svn/WSPTools/App/WSPBuilder/WSP/ReplaceableParameters.cs.

A patch adds the files *.SVC to replacement parameters process. See more details http://msdn.microsoft.com/en-us/library/ee231545.aspx and https://wspbuilder.svn.codeplex.com/svn/WSPTools/App/WSPBuilder/WSP/ReplaceableParameters.cs.

A patch adds the files *.SVC to replacement parameters process. See more details http://msdn.microsoft.com/en-us/library/ee231545.aspx and https://wspbuilder.svn.codeplex.com/svn/WSPTools/App/WSPBuilder/WSP/ReplaceableParameters.cs.

Any assembly file that is on the root of Config.Current.DirBin and ends with ".Resources.dll" will end up in a subfolder with the name Config.Current.DirBin.Name.

Ex.:
ProjFolder\80\bin\somename.Resources.dll
ends up in
WebApplicationFolder\bin\Bin\somename.Resources.dll

This patch corrects this situation.

Patch that adds support for deploying to a specific url
Example:
WSPBuilder -WSPName WebPart1.wsp -BuildWSP false -deploy true -DeploymentUrl http://sharepoint.localhost.local:3636

The ddf is not created properly when the line lengths are greater than 256 characters. The line feeds to not get generated.

The following files updates the code to ALWAYS assume it is longer than 256 characters, and generate the SOurceDir and DestinationDir lines.

Excludepaths was not working, because it was trying to compare the whole path. I needed it just compare subdirectories to eliminate .svn subdirectories. I modified three functions, see that attached file. I copied the functions that I modified and included liberal comments. I hope this can be of use to you.

Satellite DLLs were not correctly found.