wspbuilder Work Item Rss Feed

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?

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?

Commented Issue: Error: Microsoft SharePoint Services Administration is not running [11340]

Wartickler — Mon, 02 Nov 2009 22:39:25 GMT

I'm developing a simple web part in Visual Basic. My dev machine, MAXSVR01 (With Visual Studio.NET 2008 installed) is running Windows Server 2003 with MOSS 2007. I've installed WSPBuilder, and have successfully used the Tools | WSPBuilder | Build WSP command. However, when I attempt to use the Deploy command, I receive the following error in output:

Upgrading the solution!
WSPBuilder
Version: 0.9.8.0830
Created by Carsten Keutmann
GPL License 2007
Microsoft SharePoint Services Administration is not running on MAXSVR01
Preflight requirements failed.

Please advise; any help would be greatly appreciated.
Comments: ** Comment from web user: Wartickler **

This may be a dumb question here:
Should this be set to automatic?

Commented Issue: Error: Microsoft SharePoint Services Administration is not running [11340]

Wartickler — Mon, 02 Nov 2009 22:39:21 GMT

This may be a dumb question here:
Should this be set to automatic?

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

pwalke — Sun, 01 Nov 2009 23:53:15 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?
Comments: ** Comment from web user: pwalke **

I also just encountered this. It turned out that the location where I was trying to create my WSP did not have enough free disk space. Make sure you have enough free disk space for your WSP.

Created Issue: Error when trying to Copy to GAC [14575]

steven455 — Thu, 29 Oct 2009 13:04:37 GMT

Hi

When attempting to copy my DLL to GAC, I get an error about System.RunTime.InteropServices.COMException... System.DirectoryServices.DirectoryEntry.Bind();

I'm running the latest version (1.0.6 @ time of writing) on WinXP x86. Is there a fix for this?

Tks

Commented Issue: ssocli.dll problem with "Copy to GAC" command [13468]

vbarwick — Thu, 08 Oct 2009 21:19:30 GMT

I had a problem with the copy to GAC command and after some investigation, I have seen that it comes when the command copy to GAC tries to copy to GAC ssocli.dll. This dll is not in the references of any of my projects of my current solution but it appears in the build folder (debug/release) so I guess it is indirectly referenced by one of the dlls that I reference.

I have seen this issue on Windows 2008 SP2 x64.

To correct it, I simply added a filter for the dll in the project VSAddIn in CopyToGAC.Execute() , line 86

the lines :

if (dllPath.EndsWith("Microsoft.SharePoint.Search.dll", StringComparison.InvariantCultureIgnoreCase) ||
dllPath.EndsWith("Microsoft.Office.Server.Search.dll", StringComparison.InvariantCultureIgnoreCase)
)

should be changed to:

if (dllPath.EndsWith("Microsoft.SharePoint.Search.dll", StringComparison.InvariantCultureIgnoreCase) ||
dllPath.EndsWith("Microsoft.Office.Server.Search.dll", StringComparison.InvariantCultureIgnoreCase) ||
dllPath.EndsWith("ssocli.dll", StringComparison.InvariantCultureIgnoreCase)
)
Comments: ** Comment from web user: vbarwick **

It would be nice to make this more generic and have the code check if the assembly is "GAC'able" before trying to copy to the GAC, or at least, catch the error and continue copying the other assemblies to the GAC. That way the list in the code doesn't have to keep growing everytime there's a new assembly to worry about.

Commented Issue: Need some modifications to deployment scripts [13944]

pseale — Fri, 02 Oct 2009 20:13:29 GMT

Hello!

It would be nice if deployment scripts work like VSeWSS ones. I can use same script to deploy and undeploy my solution. I need this feature for my project. We have Visual Studio solution with many projects and we are using build and deployment scripts to automate our work. We need also some easy way to call WSPBuilder batches to remove deployed solutions.
Comments: ** Comment from web user: pseale **

Also in the meantime note that there is a "-CreateDeploymentFolder" command-line option, accessible from the context menu via WSPBuidler->Create Deployment Folder.

After running the command, inspect your newly-created bin/deploy folder. This may be just what you want.

Commented Issue: Need some modifications to deployment scripts [13944]

pseale — Fri, 02 Oct 2009 20:10:14 GMT

I'm working on an "outside of WSPBuilder" solution to this issue, I'll try to remember to follow up once I have my scripts worked out/debugged a little.

Created Issue: Crashes if a previously generated WSP file is in use. [14223]

dekimsey — Tue, 22 Sep 2009 20:52:45 GMT

During the build stage if the builder attempts to access the WSP file and it is currently in use (say, opened in a cab viewer) wspbuilder will crash. It'd probably be best to catch this and issue an appropriate error to the build log.

Created Issue: Support for linked items [14222]

dekimsey — Tue, 22 Sep 2009 20:49:58 GMT

I am developing WebPart solutions and I'd like to be able to use the design view built into VS. One of the references I have found is from MSDN How to: Wrap a User Control Inside of a Web Part for SharePoint [1]. It describes maintaining a web site project and the SharePoint project in the same solution. The important part is that it states one should add the ascx control files to the SharePoint project as links from the website project into the CONTROLTEMPLATES folder.

Unfortunately, it appears the WSPBuilder tool does not include these external references when building the WSP package. Thus making this particular method ineffective.
I'd like to see support added for pulling in these linked items into the wsp file.

[1] http://msdn.microsoft.com/en-us/library/dd206945.aspx

Commented Issue: Cablib.dll included in wsp-File because of deploy-Folder [13865]

wensveen — Mon, 21 Sep 2009 14:40:42 GMT

It seems that WSPBuilder now includes all dll-Files it finds in the project-Folder. Normally that should not be a problem. However, If you create the Deployment Folder, it copies also the cablib.dll into the Deployment Folder (bin/deploy). After that, when the WSP-File is rebuilt, it also includes the cablib.dll into the wsp-File, because it finds it in the Deployment-Folder (bin/deploy).

Maybe in next release, the bin/deploy Folder should be excluded from the search for dll-Files to include them in the wsp-File.

Usually that would not be a problem, but, in my case, I have a mixed environment of x64 and x86 Machines (for testing and production, ...). And of course, there I get error messages, because for example, the x86 machines have problems with the cablib.dll for x64, ...

Until this is resolved, I have to delete the deploy-Folder before every new Build.
Comments: ** Comment from web user: wensveen **

Thanks for this! I had the same problem and this fixed it for me.
Maybe the deploy directory shouldn't be a subdirectory of the bin directory.

Commented Issue: How to set the group/category for a webpart? [14116]

Bijuva — Fri, 18 Sep 2009 08:30:25 GMT

Hi,

I have developed an event handler,called TaskListEventHandler, for the Task list ((ItemAdding, ItemDeleting, ItemUpdating) as feasture using the WSP Builder project template, and I have also added a web part, called RegisterEventHandler, which could be used to bind(register) the events to a list. The webpart is WSP Builder template "Webpart without feature".

Currently, on deployment, my feature and the webpart is getting deployed sucessfully. The web part is available in the web part gallery.

Now i need to make the web part available in a particular category/group in the gallery using the WSP Builder?

I tried setting the group in the RegisterEventHandler.webpart file (which is automatically created by WSP builder on adding the webpart template inot the project), but still it doesn't show up :(

<webParts>
<webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
<metaData>
<type name="Test.EventHandler.RegisterEventHandler, TaskListEventHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9cfae6f598922b94" />
<importErrorMessage>Cannot import RegisterEventHandler Web Part.</importErrorMessage>
</metaData>
<data>
<properties>
<property name="Title" type="string">RegisterEventHandler</property>
<property name="Description" type="string">This webpart is used to register or unregister the event handler to the task list - By Biju (09 Sep 2009)</property>
<property name="Group" type="string">Biju Webparts</property>
</properties>
</data>
</webPart>
</webParts>

Could anyone please help or suggest me some solution or sample code?With regardsBiju
Comments: ** Comment from web user: Bijuva **

Hi
Could anyone please look into my query?

Created Issue: How to set the group/category for a webpart? [14116]

Bijuva — Fri, 11 Sep 2009 10:28:29 GMT

Created Issue: Still builds WSP even if project build fails [14084]

gregandmarg — Wed, 09 Sep 2009 00:57:00 GMT

If you select Build WSP, it will do a build of the project and then build the WSP, but it will still build the WSP without reporting any errors even if the project build fails. Worse, it clears the output window after the project build so it can be hard to spot.

So the workaround is to build the project manually first, and keep an eye on the error list window while doing WSP builds.

This has only been tested on 32 bit systems so far.

Created Issue: Copy to GAC in 1.0.6 [14083]

jthake — Tue, 08 Sep 2009 23:55:10 GMT

I'm getting an error in Windows Server 2008 R2 with Visual Studio 2008 SP1 when running copy to GAC:

---------------------------
WSPBuilder AddIn Error
---------------------------
System.IO.FileLoadException: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

at System.GACManagedAccess.AssemblyCache.UninstallAssembly(String assemblyName, InstallReference reference, AssemblyCacheUninstallDisposition& disp)

at WSPTools.VisualStudio.VSAddIn.Library.Commands.CopyToGAC.Execute()

at WSPTools.VisualStudio.VSAddIn.VSMenuHandler.Execute(String commandName)

at WSPTools.VisualStudio.VSAddIn.Connect.Exec(String commandName, vsCommandExecOption executeOption, Object& varIn, Object& varOut, Boolean& handled)
---------------------------
OK
---------------------------

I even tried an IISRESET and command again and still occurs...any suggestions?

Created Issue: Generated classes not marked as "public"

stingray — Thu, 03 Sep 2009 13:20:53 GMT

It seems that (all) the class files WSPBuilder generates aren't marked as "public". They should be, otherwise they cannot be called from SharePoint, can they?

Created Issue: Editing a macro causes WSPBuilder to crash

arangas — Fri, 28 Aug 2009 10:05:12 GMT

When editing a macro, WSPBuilder dies. I can work around this by restarting once finishing editing a macro. Any ideas or how to provide more debugging info? Error message is:

---------------------------
Microsoft Visual Studio Macros
---------------------------
The Add-in 'WSPBuilder' failed to load or caused an exception.
Would you like to remove this Add-in?
If you choose yes, the file it was loaded from, 'C:\Documents and Settings\All Users\Application Data\Microsoft\MSEnvShared\Addins\WSPTools.VisualStudio.VSAddIn.AddIn', will be renamed.

Error Message: Unspecified error

Error number: 80004005
---------------------------
Yes No
---------------------------

Created Issue: Need some modifications to deployment scripts

gpeipman — Sat, 22 Aug 2009 21:38:59 GMT