wspbuilder Work Item Rss Feed

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

rexlallatajr — Fri, 26 Apr 2013 15:55:49 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: rexlallatajr **

Or in the case of Sharepoint 2010, it's in Start > Control Panel > Administration Tools > Services, then locate Sharepoint 2010 Administration service and click Start the Service.

Commented Issue: Replacement parameters from command line [17425]

pranavkothare — Sun, 27 May 2012 03:37:52 GMT

Replacement parameters are not replaced when running wspbuilder.exe from command line
Comments: ** Comment from web user: pranavkothare **

Sorry I didn't mention this in the above comment, I was specifically interested in getting the following replacement parameter to work:

$SharePoint.Project.AssemblyFullName$

I have not tested any other replacement parameters.

Commented Issue: Replacement parameters from command line [17425]

pranavkothare — Sun, 27 May 2012 03:34:31 GMT

Replacement parameters are not replaced when running wspbuilder.exe from command line
Comments: ** Comment from web user: pranavkothare **

Don't know if anyone was facing the same issue, but the workaround in the mean time for me was to add the projectassembly flag.

For those using MSBuild you could do something like:

"C:\Program Files (x86)\WSPTools\WSPBuilderExtensions\WSPBuilder.exe" -projectassembly "$(TargetPath)"

Hope it helps :)

Commented Issue: Could not load file or assembly errors in version 1.0.9.1118 [15136]

Rockie — Thu, 23 Feb 2012 10:32:46 GMT

I can build the WSP but if I try and deploy I get the an error. NOthing in event logs, only seem to be able to report this to you.

I'm using VS2008 SP1 + Team Explorer on SharePoint 2007 SP2 on Server 2008 R2 x64-bit.

Oddly, creating the deployment package works, so doing that...but you do get used to use the context menu ;-)

Error message in output window as below:

Deploying to SharePoint!
WSPBuilder

Version: 1.0.9.1118
Created by Carsten Keutmann
GPL License 2007

Could not load file or assembly 'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
Inner exception(1): Could not load file or assembly 'Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
Comments: ** Comment from web user: Rockie **

trentfoley's solution helped me, thanks!

Commented Issue: Short cut keys are reset on visual studio startup [17440]

SanderdeKoning — Thu, 08 Dec 2011 08:31:46 GMT

When changing the default short cut keys for "Copy to GAC" and "Attach To Process" (plus probably all the other ones) the keys only work until visual studio is closed. Apun next startup the keys have been set back to the rather difficult combinations starting with CTRL+ALT+SHIFT+B
Comments: ** Comment from web user: SanderdeKoning **

Same here!

Created Issue: Missing WSPBuilder Templates (VS 2008 and SP 2010) [21817]

Starcrossed — Tue, 22 Nov 2011 23:54:26 GMT

We recently upgraded from WSS 3.0 to SP 2010 Foundation. I am still developing with VS 2008 while I wait on a copy of VS 2010 to be purchased. I seem to be able to build and deploy projects made in VS 2008 for WSS 3.0, but I cannot find the templates for new projects, though. I am using Visual Studio 2008 Standard with WSPBuilder 2010 Beta 4 on Windows 7 with SP 2010 Foundation.

Any suggestions?

Commented Issue: Error "Value does not fall within the expected range" on non english Visual Studio [11301]

Rockie — Wed, 16 Nov 2011 13:03:40 GMT

If you try to use the wspbuilder VS addin menu on a non english version of visual studio an error "Value does not fall within the expected range" (in french : "la valeur n'est pas comprise dans la plage attendue") occur.
After setting logging level to "verbose" in the configuration file, i saw that this error came from the property "BuildWindow" of the class "DTEHandler". Here, the name of the Build output panel is hard coded "Build". On a french installation this panel's name is "Générer".

To workaround this problem, i added an output panel named "Buid" thanks to the folowing macro :

Sub AjoutPanneauBuid()
' Create a tool window handle for the Output window.
Dim win As Window = DTE.Windows.Item(EnvDTE.Constants.vsWindowKindOutput)
' Create handles to the Output window and its panes.
Dim OW As OutputWindow = win.Object
Dim OWp As OutputWindowPane

' Add a new pane to the Output window.
OWp = OW.OutputWindowPanes.Add("Build")
' Add a line of text to the new pane.
OWp.OutputString("Nouveau panneau")

End Sub

The error message doesn't appear anymore.
Comments: ** Comment from web user: Rockie **

Thank You very much!

Replace helped! Cheers!

Created Issue: Exception on Right click on project > Build > Build WSP > Deploy [21583]

somnathpanja — Wed, 28 Sep 2011 13:14:47 GMT

Right click on project. > Build > Build WSP > Deploy
throws the following exceptions.

Commented Issue: Error while installing the setup package built [21032]

PerrySharePoint — Tue, 27 Sep 2011 15:47:58 GMT

not installed in this farm, and cannot be added to this scope”
Feature xxx is not installed in this farm, and cannot be added to scope.. everytime i install the build setup project i get this error.. but the solution is getting installed ... what might be the problem
Comments: ** Comment from web user: PerrySharePoint **

WSPBuilder doesn't produce build setup projects. WSPBuilder produces wsps. So I wonder if it is possible you are mixing WSPBuilder up with some other project, which makes build setup projects?

Commented Issue: Error while installing the setup package built [21032]

PerrySharePoint — Tue, 27 Sep 2011 15:46:55 GMT

Well, yes, of course, xxx represents the guid. But what is the guid, and what is the feature name, and how is it specified in the relevant feature.xml?

More importantly, see my other question -- what "build setup project" ?

Commented Issue: Error while installing the setup package built [21032]

sweetraskels — Tue, 27 Sep 2011 15:04:18 GMT

feature xxx is the feature name .... xxx represents the the guid

Commented Issue: Solution Installation Failed [19111]

PerrySharePoint — Tue, 27 Sep 2011 14:40:42 GMT

Hi,

I have created a simple wsp with 4 features.
1. Feature for site columns
2. Feature for lookup columns
3. Feature for Content Type1
4. Feature for Content Type2

i have organised the feature in correct folders structure within VS 2008.
Manifest.xml contains tag <FeatureManifest with 4 entries for all these features.

Whenever i try to add this wsp using stsadm, it throws an error on command propmt "The Solution installation failed".

Any ideas on how to resolve this issue.

All features are straight forward global level features and do not have any custom code along with them.

Regards,
Amit
Comments: ** Comment from web user: PerrySharePoint **

There was nothing in the event log or the SharePoint ULS logs?

Commented Issue: Error while installing the setup package built [21032]

PerrySharePoint — Tue, 27 Sep 2011 14:26:20 GMT

What "build setup project" ? What is "Feature xxx" ?

Commented Issue: Getting the error when trying to download msi file [19159]

PerrySharePoint — Tue, 27 Sep 2011 14:25:03 GMT

On my VISTA Business edition SP2, IE 8, I am getting the following error when I try to download the file "WSPBuilder Extensions 1.06 - x86 / x64 bit and IIS6 / IIS7 support" from http://wspbuilder.codeplex.com/releases/view/30858 :

"Your current security settings do not allow this file to be downloaded"

I tried to lower down the security settings of IE to Low, but noticed that it goes back to Medium.
I also tried the following "Go to your user settings and under the UAC (User Account Control) uncheck the box and I beleive you may have to reboot." as described in http://www.bleepingcomputer.com/forums/topic152302.html
But no luck so far.

Please help.

Thanks.
Comments: ** Comment from web user: PerrySharePoint **

You are having trouble with your web browser; this does not seem to be related to WSPBuilder.

I suggest you try a different web browser -- Firefox, Chrome, Opera...

Commented Issue: Name cannot begin with the '%' character [13572]

sebbas32 — Mon, 22 Aug 2011 15:09:21 GMT

I am trying to create a Site Defintion using WSPBuilder. The solution compiles but it gives an error when I try to deploy.
:
Install and deploying DemoProject.wsp
Unable to deploy solution
Inner exception(1): Name cannot begin with the ‘%’ character, hexadecimal value 0×25. Line 1, position 2.
:

Did anybody face a similar issue? I have attached the demo project with this post.
Comments: ** Comment from web user: sebbas32 **

I know this could be very old, but i want to help, maybe someone could have this problem too.

I had the same and mine was in the Feature.xml, i was naming <ElementManifest> the ones that should be named <ElementFile>, like the schema.xml, AllItems.aspx, etc.

So the solution was to put in the correct that the files and the manifest, the result was something like this:

I hope this helps.

Commented Issue: Beta: error CS0234: The type or namespace name 'TargetFrameworkAttribute' does not exist in the namespace 'System.Runtime.Versioning' (are you missing an assembly reference?) [18900]

DavidLozzi — Thu, 30 Jun 2011 13:42:05 GMT

I just downloaded and installed the beta. I opened my VS 2010 solution and added a new WSPBuilder project (no workflow). Then, I just did a build and I'm getting this error. Any idea what I'm doing wrong? Thanks.
Comments: ** Comment from web user: DavidLozzi **

I corrected the issue by selected v4 in the project properties, then going back and selecting v3.5

Created Issue: s not installed in this farm, and cannot be added to this scope” [21032]

sweetraskels — Mon, 27 Jun 2011 19:27:35 GMT

Feature xxx is not installed in this farm, and cannot be added to scope.. everytime i install the build setup project i get this error.. but the solution is getting installed ... what might be the problem

Created Issue: WSP Builder Deployment Issue - Microsoft SharePoint Services Administration is not running [20579]

shafaqat309 — Wed, 27 Apr 2011 07:38:10 GMT

Hi

I am using WSP Builder with SharePoint Foundation 2010 and Visual Studio 2008

when i deploy it says timer job is not running, i have checked it is running successfully.

Can anyone help me on this.

I have VS2010 too installed on my machine but same error with both versions of Visual Studios.

I have successfully worked with Wss3.0 and VS 2008 but this is happening with Foundation 2010.

Commented Issue: Beta: error CS0234: The type or namespace name 'TargetFrameworkAttribute' does not exist in the namespace 'System.Runtime.Versioning' (are you missing an assembly reference?) [18900]

OiDatsMyLeg — Mon, 21 Mar 2011 02:33:54 GMT

As a workaround, you can change the target framework to be another version and build the project. Then change the version back to v3.5 and rebuild. It worked for me when reloading the project/solution didn't but YMMV.

Created Issue: deploywithstsadm file [20218]

NISHIL — Sat, 12 Mar 2011 20:08:45 GMT

The file is referring old 12 hive of SP 2007.
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe"
..............

It should be as below for SP 2010.
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN\stsadm.exe" -o retractsolution
..............

Can someoen please update the code and fix it.
Its a minor issue.
Good work guys....WSP builder is a good tool.

Regards,
Nishil