WSPBuilder (SharePoint WSP tool)

Created Issue: Error when I try to setup WSPBuilder Extensions 1.0.6 [14936]

miha198206 — Fri, 20 Nov 2009 09:22:02 GMT

Hello.

I get an error message about invalid Windows Installer patch package when run WSPBuilderExtensions.msi file. My OS is Windows Server 2008, Visual Studio 2008.
How can I install the package?

Source code checked in, #41327

keutmann — Thu, 19 Nov 2009 01:06:56 GMT

Menifest.Config code bug fixed. VisualStudio ProjectTemplate updated. Test projects updated. VS function "Deploy" fixed!

Source code checked in, #41124

keutmann — Wed, 18 Nov 2009 00:37:00 GMT

Manifest.config handler bug fix.

Source code checked in, #41106

keutmann — Tue, 17 Nov 2009 23:19:59 GMT

Cleanup of test project. Manifest.config resource bug fixed. Added SafeControls empty bug fixed. Unit Test of Manifest.config

New Post: Visual Studio 2010

austegard — Tue, 17 Nov 2009 20:11:34 GMT

Based on advice from Bjørn Furuknap (@furuknap, http://furuknap.blogspot.com/2009/11/using-wspbuilder-for-sharepoint-2010.html) I was able to deploy to SP 2010 a rather complex WSPBuilder-based SharePoint solution that I first recompiled in VS 2010.

Steps were:

Download the commandline version, with the x64 cablib dll
Upgrade your VS 2008/2005 solution to VS 2010
Replace your 12 references with their 14 equivalents - most will be found in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI
Compile your VS solution - this SHOULD work
Use the wspbuilder command line tool to create, but not deploy your wsp (use wspbuilder -help for instructions)
Use stsadm -o addsolution -filename <yourwsp> to deploy the solution

Source code checked in, #40895

keutmann — Tue, 17 Nov 2009 00:57:24 GMT

RegistryKey bug fixed for Visual Studio 2010. WSPBuilderProject Wizard for VS updated. Work in progress!

Source code checked in, #40661

keutmann — Mon, 16 Nov 2009 01:51:22 GMT

Visual Studio 2010 Support implemented, registry not working. Work in progress!

Reviewed: WSPBuilder Extensions 1.0.6 (Nov 13, 2009)

wartickler — Fri, 13 Nov 2009 21:26:32 GMT

Rated 5 Stars (out of 5) - No question; after doing this for a while and complaining about how difficultly all of this blasted XML was behaving, I contemplated writing this exact piece of software. If you were a woman I would kiss my wife!

New Post: Accessing Resources from User Controls

emorgoch — Fri, 13 Nov 2009 18:59:07 GMT

I'm trying to create a web part that includes a user control that needs access to a couple images and a CSS file for formatting. I used these instructions to configure WSPBuilder to allow me to build the user control, and read this article about including resources for my web part. However, trying to access the resources from the wrapped user control is causing some errors. If the resources are embedded and the Page.ClientScript.GetWebResourceUrl() method is used from the user control, the WebResource.axd URL is returned, neither the images nor the CSS file actually loads. If I try using a linked resource, and accessing it with the SPWebPartManager.GetClassResourcePath() method, I get an error stating "A Web Part or Web Form Control on this Page cannot be displayed or imported. The type is not registered as safe."

As a workaround, I can create properties in my User Control to store the appropriate URLs, then from the web part class that calls Page.LoadControl(), I can execute the above methods successfully, and pass the returned results to the User Control.

Is this the appropriate path to take, or is there some configuration issue that I've missed?

Thanks,

Evan

Commented Issue: CabLib Compress ERROR: Could not flush cabinet: Could not create cabinet file [11556]

rshetwal — Fri, 13 Nov 2009 17:07:25 GMT

I have been unable to find documentation on this particular error while building a wsp.

Has anyone encountered any build errors within a SourceSafe project?

Commented Issue: CabLib Compress ERROR: Could not flush cabinet: Could not create cabinet file [11556]

rshetwal — Fri, 13 Nov 2009 16:55:47 GMT

I have been unable to find documentation on this particular error while building a wsp.

Has anyone encountered any build errors within a SourceSafe project?

Source code checked in, #40147

keutmann — Fri, 13 Nov 2009 15:34:23 GMT

Assembly BindingRedirects implemented. Work in progress!

Source code checked in, #40000

keutmann — Fri, 13 Nov 2009 01:23:28 GMT

Manifest.config implemented. Work in progress.

Reviewed: WSPBuilder Extensions 1.0.6 (Nov 12, 2009)

extdev — Thu, 12 Nov 2009 23:23:14 GMT

Rated 5 Stars (out of 5) - Great tool. Saves a lot of time and headache!

New Post: Linked Files Issue

keutmann — Thu, 12 Nov 2009 12:54:22 GMT

Its not possible to use Linked file in Visual Studio for WSPBuilder. The reason for this is that WSPBuilder do not read the Visual Studio .csproj file, but only the folder struture and the files within them. Therefore WSPBuilder will not build the files that are linked files, you have to copy the files in order to get them build.

New Post: Linked Files Issue

AliZaiter — Tue, 10 Nov 2009 20:21:24 GMT

Hello,

When you add linked files under some folder(like the GAC) in visual studio the wsp builder project they will be ignored and will not be packaged with the generated wsp.

Note that i am talking about linked files and not actual files. I need to use linked files because my webparts are created in a different project than the one used to generate the wsp and i don't need to keep copying them when they are updated.

Hope there is a solution for this problem.

Thanks,

New Post: How to include dlls of library projects in wsp?

JTummers — Tue, 10 Nov 2009 14:33:00 GMT

Hi,

This exact problem, I also encountered. It is because assemblies already in the GAC are not copied to the output directory by Visual Studio.

One possible solution is to create a post build script, which copies the required the assemblies to the directory WSPBuilder looks in.

Good luck!

New Post: Visual Studio 2010

fmuntean — Thu, 05 Nov 2009 21:11:59 GMT

Thank you for looking out for the poor souls that will be a whilestill developing on SP2007.

I am currently looking to upgrade to SP2010 but I relly too much on the WSP builder extensions during the development that I can't leave withouth it.

Please let us know if you need any help

Reviewed: WSPBuilder Extensions 1.0.6 (Nov 05, 2009)

cglessner — Thu, 05 Nov 2009 08:12:59 GMT

Rated 5 Stars (out of 5) - Best SharePoint Development Tool for Visual Studio 2008. Love it :)

Source code checked in, #38266

keutmann — Wed, 04 Nov 2009 23:11:14 GMT