WSPBuilder

New Post: feature.xml

gab — Tue, 01 Jul 2008 14:02:14 GMT

Hi All,
we are developing web part and template with Visual Studio 2005 extensions for Windows SharePoint Services 3.0 (version 1.1)
we would like to use WSPBuilder.exe to automate build process.
We follow the step described on manual, created "12" dir and copy folder (mywebpart) and files (myperpart.webpart, mywebpart.xml)
Then run WSPBuilder. If we don't copy feature.xml in new folder under "12\MyWebFolder" the WSP is not correct.
Is there a way to automate the creation of feature.xml?
Thanks in advance

New Post: include license file into 80/bin folder

phils — Tue, 01 Jul 2008 07:57:22 GMT

We have to integrate a license file of a third party dll in the folder 80/bin (license.lic). Is there a possibility to deploy the file with wspbuilder into the 80/bin folder? thanks for your answer.

Source code checked in, #18890

keutmann — Tue, 01 Jul 2008 01:12:43 GMT

Command bug in VS Addin fixed. Some clean up.

New Post: Third party dll's

wozzle — Sun, 29 Jun 2008 20:13:59 GMT

Hello
I have the following challenge. I have a third party dll which my features requires. The name is MyThirdPartyDll.dll
I want it to be installed in the gac along with my MyFeature.dll
I know that a assembly tag should be added to the manifest file and I can do so manualy. But is there a way to
have wspbuilder do it ?

<Solution SolutionId="4AFC1350-F354-4439-B941-51377E845F2B"
xmlns="http://schemas.microsoft.com/sharepoint/">
<FeatureManifests>
    <FeatureManifest Location="Calls\feature.xml"/>
    <FeatureManifest Location="ServiceRequest\feature.xml"/>
    <FeatureManifest Location="Customers\feature.xml"/>
    <FeatureManifest Location="HelpDeskCore\feature.xml"/>
</FeatureManifests>
<TemplateFiles>
    <TemplateFile Location="Mobile\HelpDeskHomePage.ascx"/>
    <TemplateFile Location="1033\xml\webtemphd.xml"/>
    <TemplateFile Location="SiteTemplates\HelpDesk\onet.xml"/>
    <TemplateFile Location="SiteTemplates\HelpDesk\default.aspx"/>
</TemplateFiles>
<Assemblies>
    <Assembly DeploymentTarget="GlobalAssemblyCache"
      Location="MyThirdPartyDll.dll"/>
    <Assembly DeploymentTarget="GlobalAssemblyCache"
      Location="MyFreature.dll"/>

</Assemblies>
</Solution>

New Post: Deploying PDB's when compiled in debug mode

ronn_mcqueen — Fri, 27 Jun 2008 20:28:49 GMT

We had a need to deploy the .PDB files into the bin directory with our .dlls, for the purpose of reporting exceptions with a custom exception handling class.
The way that we accomplished this was to recompile WSPBuilder with the following code change to AssemblyFileReference.cs, this may work for GAC deployment also, although I've not tested that.

private void FindAssembliesInDirectory(DirectoryInfo parentDir, SolutionDeploymentTargetType targetType, Dictionary<string, AssemblyInfo> assembliesFound)
{
    FileInfo[] dllFileInfoDLLs = parentDir.GetFiles("*.dll") as FileInfo[];
    FileInfo[] dllFileInfoPDBs = parentDir.GetFiles("*.pdb") as FileInfo[];
    FileInfo[] dllFileInfoCombined = new FileInfo[dllFileInfoDLLs.Length + dllFileInfoPDBs.Length];
    dllFileInfoDLLs.CopyTo(dllFileInfoCombined, 0);
    dllFileInfoPDBs.CopyTo(dllFileInfoCombined, dllFileInfoDLLs.Length);
    foreach (FileInfo dllFileInfo in dllFileInfoCombined)
    {
        if (FileProvider.IncludeFile(dllFileInfo))
        {
            AddCandidateAssembly(dllFileInfo, targetType, assembliesFound);
        }
}

foreach (DirectoryInfo childDir in FileProvider.GetDirectories(parentDir))
{
FindAssembliesInDirectory(childDir, targetType, assembliesFound);
}

}

Productions the following xml in the manifest file.

<Assembly Location="[YourAssemblyName].pdb" DeploymentTarget="WebApplication" />

It would be very nice to get this behaviour via a configuration setting in a future version of WSPBuilder.
Hope that helps!

New Post: Deploying PDB's when compiled in debug mode

ronn_mcqueen — Fri, 27 Jun 2008 20:28:49 GMT

foreach (DirectoryInfo childDir in FileProvider.GetDirectories(parentDir))
{
FindAssembliesInDirectory(childDir, targetType, assembliesFound);
}

}

Productions the following xml in the manifest file.

New Post: Deploying PDB's when compiled in debug mode

FeL0niOuSmOnK — Fri, 27 Jun 2008 13:47:09 GMT

Keutmann,

Thanks for the reply -- This method works great if you have all the development tools on the SharePoint server. Unfortunately, I have a remote SharePoint server which is used for our development purposes, and without the .pdb in the GAC, it will not debug.

No harm, though. I've got the nuisance of copying down to an art at this point :)

New Post: Failure due to Assemblies in the GAC

hristopavlov — Fri, 27 Jun 2008 03:57:21 GMT

We had the same problem. It looks like it happens when you have two assemblies, both included in the solution and one of them referencing the other one plus having the referenced assembly deployed to the GAC at the time you try to run wspbuilder.

Things were even worse for us as we have the WSPBuilder as a post build action in VS.NET and even that wspbuilder didn't succeeed, VS would still report that the build was successful.

To resolve the issue we added calls in the post build actions to gacutil.exe to remove the assembly from the GAC before running wspbuilder and then optionally adding it back in the GAC after that. Also you could check whether %ERRORLEVEL% == 0 in after wspbuilder call returns. A non zero value will indicate an error and you could make the VS build to fail in that case.

Hope this helps someone.

Cheer,
Hristo Pavlov

Source code checked in, #18847

keutmann — Thu, 26 Jun 2008 23:24:13 GMT

Addin refactored and fixed. WebPartTemplate updated. Setup project updated.

New Post: Prevent WSPAddin Log in project folder

keutmann — Thu, 26 Jun 2008 16:39:24 GMT

This is actually something that should not have been there, so it will be removed in the next version of WSPBuilder.

New Post: Please put link to demo code on Home page

keutmann — Thu, 26 Jun 2008 16:36:42 GMT

The demo project is kept in the source code of the WSPBuilder project.
However I will create a separate project for this in the future.

New Post: Context menu item for WSPBuilder disappears when a WSPBuilder project is in a solution folder.

keutmann — Thu, 26 Jun 2008 16:34:32 GMT

I'll look into this issue and make sure that it will be fixed in the next version of WSPBuilder Extensions.

New Post: Cablib failure

keutmann — Thu, 26 Jun 2008 16:30:58 GMT

The CABLIB.DLL is a C++ library and therefore you have to use the right version of it when you are using 32 or 64 bit windows server systems.
You should be able to find previous version of wspbuilder on codeplex where the cablib.dll can be found in 32 / 64 bit versions.
The cablib.dll have not changed since the start of the wspbuilder project and therefore it can be used for all versions of wspbuilder.

New Post: Deploying PDB's when compiled in debug mode

keutmann — Thu, 26 Jun 2008 16:26:16 GMT

Please see this post : http://www.elumenotion.com/Blog/Lists/Posts/Post.aspx?ID=23
Just be sure to copy your debug build dll.

New Post: Having trouble adding safe controls to manifest.xml

keutmann — Thu, 26 Jun 2008 16:22:43 GMT

The WSPBuilder ignores the Microsoft dll's when creating the SafeControls tags.
However if you inherit from any webpart class in your own code, then the WSPBuilder should pickup your webpart class (must be public) and add a SafeControl tag in the manifest.xml file.
If this do not solve your problem please specify your project in more detail.
Be sure to use the WSPBuilder ver. 0.9.8.0406.

New Post: deploy to port 443?

keutmann — Thu, 26 Jun 2008 16:02:30 GMT

WSPBuilder builds the wsp package (CAB format), just like winrar builds a zip file.
There are deployment functions within WSPBuilder, but they are only meant to be used on the developing environment.
Use the stsadm.exe to install the wsp package on production servers.
You have to be on the front-end server to deploy a wsp package on a farm.
It does not matter what port the WebApplication runs with.

New Post: Using WSPBuilder with Team foundation Build

keutmann — Thu, 26 Jun 2008 15:55:35 GMT

Hi

WSPBuilder Extensions is an addin that works fine with TFS 2008. It gives you build options from the Project Context menu and so on.
It uses the WSPBuilder console application to build the WSP package.

The WSPBuilder (console app) can be used for build servers and do not need to run within TFS 2008.

New Post: Using WSPBuilder with Team foundation Build

Indyy66 — Thu, 26 Jun 2008 12:53:21 GMT

Hi,

I'm create Build with TFS 2008 and I'm looking for information on whether WSPBuilder works well with it? Or are ther some gotcha's that I should be looking out for?

Thanks,

James

Source code checked in, #18821

keutmann — Wed, 25 Jun 2008 23:18:34 GMT

Work in progress.. "Copy to GAC" added.

New Post: deploy to port 443?

bobchauvin — Wed, 25 Jun 2008 15:18:28 GMT

Does WSPBuilder support deploys to an entire farm, or ports other than 80?