12

There is a related question on SharePoint StackExchange: How to remove orphaned features Remove all the orphaned features: Get-SPFeature | ? { !$_.Scope } | % { $_.Delete() }


12

You can tell the status of a deployment by observing the combined values of the Deployed and JobExists properties of the SPSolution object. SPSolution.Deployed True - Solution is deployed False - Solution is not deployed SPSolution.JobExists True - A retract/deploy job exists for this solution. False - No job It's important to check both of these ...


10

As a short answer: No You can't add two different versions of the same solution name in the same environment. Workarounds You have 2 workarounds Redploy the same solution with a different name. In UAT and Production farms, Try to do the following: Back up the current solution as mentioned here. Retract and remove the old version using PowerShell. ...


9

Install-SPSolution -Identity <solution.wsp> -WebApplication <name or guid of web app> -GacDeployment the above should work! what is your solution scoped to? farm webapp site web? It should be scoped to site to be deployed to a specific webapp! under central admin look at the wsp list and see where its currently deployed to, is it global or to ...


8

I think This is especially the case if you have just done a retract/uninstall and you try to add straight away. If you try again in a few seconds it will work. Basically this is because when you delete a wsp from solution management and then immediately run this stsadm command, there will still be clean up operations going on in the background. So just leave ...


8

Open solution in Visual Studio. Right click on the solution and deploy or build the solution. Now check your solution configuration If your are in debug mode, then find your .wsp in the following folder PathOfYourSolution\bin\Debug If your are in release mode, then find your .wsp in the following folder PathOfYourSolution\bin\Release


8

Solution id is identity of Solution package (.wsp file). If you are deploying wsp file, it will check solution id. If exists, it will update solution. Solution contains all the features, assembly, resources, etc. One .wsp package can contain multiple features Feature id is identity of particular single feature which is web/site/web application/farm scoped ...


7

Following are the powershell commands to deploy a wsp to single web application: Add-SPSolution <wsp file name>.wsp Install-SPSolution –Identity <wsp file name>.wsp –WebApplication <Site URL> –GACDeployment


7

Package a WSP Right click your project in the right column. Then click "Publish". A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking "Publish" your project will be build and then packaged in the selected location. Make sure to have the Solution configuration set to Release when building for production. ...


7

You can have multiple SharePoint projects (.csproj) in the same Visual Studio solution (.sln). Each SharePoint project builds into a WSP (right-click on the project and select "Package" or "Publish" depending on your version of VS). "Package" (or "Publish") will first build the project and then create the .wsp. A Visual Studio Solution (.sln) is not at all ...


6

Just changed the files extension of your wsp from .wsp to .cab and open it. If you would like to open the file contents of your wsp to visual studio, create a new project in visual studio with "Import SharePoint 2010/2013 Solution Package" project type and choose your wsp to load all its files structure to solution explorer. OR if you want to make use of ...


5

Your point is actually about comparing two binary files. First, obviously, you can compare exact size of the files: if they don't match, you know they're different. But the best would be to use any binary file comparator, like seen in https://stackoverflow.com/questions/8166697/tool-for-comparing-2-binary-files-in-windows. That would immediately tell ...


4

make sure the solution deployment job was finished before you activate the feature. have a look at this blog: Programmatically waiting on SharePoint Solutions to deploy


4

If you get an error adding SharePoint DLL which states Could not load file or assembly 'microsoft.sharepoint, Version=12.0.0.0 you can try using this script instead [Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") and you can continue exporting the WSP from your 2007 environment $farm = [microsoft.sharepoint.administration....


4

It doesn't matter. Once a solution is deployed, the timer job will propagate the changes to all other servers. That is the reason for packaging everything as a solution. One the other hand, people tend to make direct changes to server (by editing files etc.) those changes will never get propagated. Major steps to farm solution installation: Adding: A ...


4

Retract Solution fires off the Uninstall process of the WSP package from the farm. It's equivalent to the Uninstall-SPSolution PowerShell command and the opposite of the Install-SPSolution command. Remove Solution is the equivalent of the Remove-SPSolution PowerShell command and is the opposite of the Add-SPSolution command. It can be seen as deleting the ...


4

Yes, you can build and publish WSP without deploying solution.There is 'Publish' option in visual studio 2012, click on it & specify hard drive folder path to publish WSP. First bulid your solution then Right click on project in solution explorer-->Publish


4

You can easily do that either from the Central Administration (System Settings, Farm Solution, click on your solution, and then "Deploy": you can select the ttarget Web application), or from a SharePoint PowerShell console (Install-SPSolution -Identity <WSP_NAME> -WebApplication <Web_App_URL> [-GACDeployment]).


4

try below steps to get the files. First of all, locate the WSP package that needs to be investigated. you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell: $frm = Get-SPFarm $file = $frm.Solutions.Item("nameof.wsp").SolutionFile $...


3

Try this code,it will donwload it from the site collection $spWeb = Get-SPWeb -Identity http://SPServer $listTemplate = [Microsoft.SharePoint.SPListTemplateType]::SolutionCatalog $solGallery = $spWeb.Site.GetCatalog($listTemplate) $solGallery.Items | ForEach-Object { if($_["Title"] -eq "the title of the solution") { [System.IO.FileStream]$outStream = ...


3

1) Open your manifest file of Package 2) (+ Edit Options) Expand it. Click on Overwrite generated XML and edit manifest in the XML editor link. > Edit manifest in the XML editor. 3) In Edit mode node look like. <Assemblies> <Assembly Location="SharePointProject1.dll" DeploymentTarget="GlobalAssemblyCache" /> </Assemblies> 4) Just ...


3

Here is a generic idea Using stsadm -o enumsolutions get all installed solutions on the farm Then for each solution you need to download it using following technique [Enable Powershell] (http://support.microsoft.com/kb/968930) [System.Reflection.Assembly]::Load("Microsoft.SharePoint, Version=12.0.0.0, Cult ure=neutral, PublicKeyToken=71e9bce111e9429c") [...


3

In SharePoint 2013, sites can be created either in SP 2010 mode or SP 2013 mode. So, SP 2010 compatible WSPs can be deployed to 14 hive by specifying the compatibility mode in SP 2013. Therefore a SP 2010 mode site will work properly. However, if the idea is to use SP 2013 based site, then the custom solutions should be upgraded. If you have VS 2012 or 2013 ...


3

This solved my problem: remove-spsolution -identity {name of wsp file.wsp} -force


3

Go to Package.package in your project and double-click it. Click the "Advanced" tab Click "Add" and "Add Existing Assembly.." Click the "triple-dots (...)" Navigate to your project folder and then to the .dll in the bin-folder and click "Open" That should be it


3

Open The Package.Package file and change then Name attribute. Example <package xmlns:dm0="http://schemas.microsoft.com/VisualStudio/2008/DslTools/Core" dslVersion="1.0.0.0" Id="d3150724-5644-479c-99f3-fc99af5bfdc6" solutionId="d3150724-5644-479c-99f3-fc99af5bfdc6" resetWebServer="true" sharePointProductVersion="15.0" name="NEWNAME" xmlns="http://...


3

You cannot make changes to a already compiled WSP file. You need to have the Visual Studio Project instead. This Visual Studio Project packages all the assets to a WSP add the compiled dlls and every thing else. I highly recommend tho read the basic information on the MSDN Create SharePoint Solutions first.


3

It depends on what resources does Your wsp contain. If there are images or pages, url paths are different in 2013, so links will be broken(by example /_layouts/ should become /_layouts/15, and so /images/). And imho it is not necessary to change all references to .Net 4.0, but only sharepoint dlls, which have different version in 2013. So 1) If You have ...


3

Please verify following things Current logged in user is in Administrator group of SharePoint server. Please try once Recycling IIS by IISRESET it worked for me in past


Only top voted, non community-wiki answers of a minimum length are eligible