WSPBuilder (SharePoint WSP tool)

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.

New Post: I Have the Solution to Make WSP Builder work with Visual Studio 2012 and SharePoint 2013

Portalmonkey — Sat, 16 Mar 2013 05:11:51 GMT

I already know how to do it...and the solution in your post only covers part of the issue. WSPBuilder does not support .net 4 framework, which is the main issue because you need .net 4 framework for SharePoint 2013.

From: Matt_Bezanson [email removed]
Sent: Friday, March 15, 2013 5:45 PM
To: willzworld2@msn.com
Subject: Re: I Have the Solution to Make WSP Builder work with Visual Studio 2012 and SharePoint 2013 [wspbuilder:404783]

From: Matt_Bezanson

Here is a post that talks about how to do this:

http://gblsharepoint.blogspot.com/2013/01/using-wspbuilder-with-visual-studio-2012.html

Note the path in Win 2008 R2 is: C:\ProgramData\Microsoft\MSEnvShared\Addins

New Post: WSPBuilder for Visual Studio 2012

Matt_Bezanson — Fri, 15 Mar 2013 21:46:16 GMT

New Post: I Have the Solution to Make WSP Builder work with Visual Studio 2012 and SharePoint 2013

Matt_Bezanson — Fri, 15 Mar 2013 21:45:00 GMT

New Post: WSPBuilder does not include my assembly in the WSP

AhmedAli786 — Sun, 10 Mar 2013 09:47:25 GMT

thanks robin_meure. It worked perfectly for me.

New Post: Clean, Build, Build WSP and Deploy Macro!

Exploseph — Fri, 01 Mar 2013 16:53:54 GMT

I couldn't find this anywhere, it is useful to me and thought someone else might like it. Not that you couldn't create it yourself, anyway. VS 2010 SP2007

Option Strict Off
Option Explicit Off
Imports System
Imports EnvDTE
Imports EnvDTE80
Imports EnvDTE90
Imports EnvDTE90a
Imports EnvDTE100
Imports System.Diagnostics

Public Module RecordingModule

Sub WSP()
    DTE.Solution.SolutionBuild.Clean(True)
    DTE.Solution.SolutionBuild.Build(True)
    DTE.ExecuteCommand("WSPTools.VisualStudio.VSAddIn.Connect.BUILDPROJECTWSP")
    Threading.Thread.Sleep(5000)
    DTE.ExecuteCommand("WSPTools.VisualStudio.VSAddIn.Connect.DEPLOYWSP")
End Sub

End Module

New Post: WSPBuilder for Visual Studio 2012

pfgoncalves — Fri, 08 Feb 2013 16:46:48 GMT

The will be a WSPBuilder version for Visual Studio 2012 ?

I'm working on a MOSS 2007 site but wan't to use latest version of visual studio...

New Post: .net 4.0 Support

portalmonkey — Tue, 27 Nov 2012 21:24:55 GMT

I have a solution for this problem...see my discussion dated 11/27/2012

New Post: I Have the Solution to Make WSP Builder work with Visual Studio 2012 and SharePoint 2013

Portalmonkey — Tue, 27 Nov 2012 21:20:16 GMT

If you are like me, you hate the Visual Studio Templates for SharePoint and love WSPBuilder for creating your wsp's. I recently set up a new dev environment on Server 2008 R2 with a SQL Server 2008R2 backend. I installed SharePoint 2013 and Visual Studio 2012 on the frontend. While I was upgrading one of my old 2007 solutions to make it work on SP 2013, I realized I could no longer quickly build my solution package. I tried installing the SP 2010 version of WSPBuilder on VS 2012, but it didn't work. So, I manually copied the Visual Studio templates to the proper locations and modified the xml in the tools file and it worked--I could now see the WSPBuilder templates and the tools were showing (i.e. I could right click on my project and see the WSPBuilder > Build wsp in the context menu. I created the wsp and realized the dll in "GAC" folder was being excluded because of "unmanaged code"--that's because the builder was built to use the 3.5 framework--anything above that is considered unmanaged code. To fix this, I opened the source code for the the WSPTools and commented out the code in several places where unmanaged code was being excluded from the manifest. I then recompiled the project and copied the new WSPBuilder.exe into the program folder (in Program Files X86)--PRESTO!--Everything works now. The dll is added to the Global Assembly Cache in the manifest and all of the safe control tags are created. When you run the builder in VS, you get the "Could not resolve" message in the verbose output, but it still creates all of the tags in the Manifest and packages everything correctly in the .wsp.

If you would like more details on how to do this, feel free to email me at willzworld2@msn.com

New Post: [resolved] Got a problem with WSPbuilder for workflow

Ashik101 — Thu, 22 Nov 2012 13:12:23 GMT

Hi Mathis

I saw your link its too good.I have moss and tried the same .Everythin worked fine for me but after i created a List and added new item it says Failed on start(retrying)

any idea.Please help

Thanks

Ashik

New Post: WSPBuilder Activity

xavier1980 — Fri, 09 Nov 2012 07:40:35 GMT

I ended up creating a custom activity to create WSP. I changed the default dll setting for build so that they remain in bin folder and call wspbuilder. After wsp is created move all dll files to source folder where TFS would have copied the dlls with default settings.

New Post: WSPBuilder Activity

dylan_berry — Thu, 08 Nov 2012 18:03:46 GMT

I am looking at this as well, did you end up finding an example or tutorial?

New Post: SharePoint 2013

davidgemel — Thu, 08 Nov 2012 16:16:18 GMT

Are there any plans to modify WSPBuilder to support SharePoint 2013?

New Post: List of error codes?

idreamingreen — Wed, 10 Oct 2012 21:59:00 GMT

Is there a list of error codes that are output by wspbuilder? Specifically, is there any info about code 3?

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

New Post: Third party dll's

sharmilacodeplex — Fri, 14 Sep 2012 09:10:24 GMT

Hi,

I am also facing the same issue. I have modified the manifest.xml content to add the assembly reference. Re-creating wsp and then deploy. But i want to know whether wspbuilder installed to visual studio 2010 can do it automatically? I have created a folder names GAC in my projct and added the third party dll as an existing item. But in wsp manifest xml i dont find any assembly references added.

New Post: add referenced dll in wsp

sharmilacodeplex — Thu, 13 Sep 2012 12:42:57 GMT

Hi,

I have created a wspbuilder project for sharepoint 2010. I have also added reference of a third party dll in the project. Now I create the wsp. but the third party dll is missing in GAC(assembly folder of windows) which in turn is giving error in the project that the "file is not found". Can anyone tell me how can solve this issue. I tried manually embedding the third party dll to the manifest.xml but re-creating the wsp out of it is not making any changes. Can anyone tell me whether I am missing something? What are the steps to add the referenced dll to the wsp package?

Regards,

Sharmila

New Post: How can we set SafeAgainstScript attribute to true while adding SafeControl entries using WSPBuilder

bolandunited — Thu, 13 Sep 2012 08:53:21 GMT

Powershell to the rescue:

function SetSafeAgainstScriptTrue($url)
{
	$webapp = Get-SPWebApplication $url
	
	$path = $webapp.IisSettings.get_Item(0).Path.FullName + "\web.config"
	$now = [datetime]::now.ToString('yyyy-MM-dd')
	Copy-Item $path "$path.$now"	
	Write-Host "Backupped"
	Write-Host "Modifying web.config file in path $path"
	(Get-Content $path) | 
		Foreach-Object {$_ -replace "SafeAgainstScript=`"False`"", "SafeAgainstScript=`"True`""} | 
	Set-Content $path
		
}

New Post: How can we set SafeAgainstScript attribute to true while adding SafeControl entries using WSPBuilder

bolandunited — Tue, 31 Jul 2012 10:22:18 GMT

Any news on this subject?? We also need settings this property to true.

Only option we see is to migrate to the new Project standaard for SP2010 solutions in Visual Studio, but we have a sln with 90+ projects...