17

It's called "Publish" now. Functionality is basically the same.


12

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


11

Ok, for the wsp part follow laurie, or if your lazy add wspbuilder to visual studios to build the wsp for you. now to add the masterpage and css: create an empty project add module as you can see above, remove the sample.txt, right click styles and add your masterpage and add another module for css :) for the css, click on the elements.xml and add the ...


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

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 ...


8

2007 version stsadm -o upgradesolution -filename "drag drop the file here" -name "copy the name here including the wsp" -immediate -allowgacdeployment just replace the writing in quotes with what is says! plus put them in quotes. DONT copy past the code above as it will execute and only throw an error, just write it out! that should do the trick ;) hope ...


8

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

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

DON'T There is no way this is going to turn out well. Changing the name of the WSP isn't going to change anything. You'll still have the same: Solution Id Feature Folders and Ids Dlls (including the codebehind for your application pages) SharePoint Root files (including your application pages) So in order for the new solution not to overwrite the old you ...


6

The best solution is to use the SPSolution.LastOperationResult and SPSolution.LastOperationDetails properties. $solution = Get-SPSolution -Identity:$file while ($solution.JobExists -eq $true) { Write-Host '.' -NoNewline sleep -Seconds:1 $solution = Get-SPSolution -Identity:$file } $lastOperationResult = $solution.LastOperationResult return ($...


6

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


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

This tutorial worked fine for me: http://knowledge.zomers.eu/SharePoint/Pages/How-to-prevent-SharePoint-2010-solutions-from-globally-deploying.aspx


5

This is how it really works: If you have updated just your logic (code) and only need to update your DLL then you can do as @thantos suggests and use Update-SPSolution This command also works for updating your files (_layouts), as long as they are not stored in the database (unghosted). If you have made any changes to any of these: Features, Package, ...


5

If you don't want other people to be able to Reverse Engineer the source code to DLLs you're giving them, then you should obfuscate the DLL. See .Net Obfuscation for some suggestions. But before going in that direction I have a couple of comments: The only people who can get the DLL is the people with access to WSP (or the farm where it's installed). Not ...


5

.webpart files are XML. Open it with Notepad or your favorite XML editor. See Web Part Properties - part 3 - the .webpart file by Wictor Wilen for an example.


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

You can use the Package Designer to create and customize a package (.wsp). For example, you can add SharePoint project items and Features, specify if the Web server is reset when the solution is deployed, and set the deployment server type. it contains all the files for deployment like xml, dll, wsp ect... http://msdn.microsoft.com/en-gb/library/...


4

Yes it is. You create a module which points to the corresponding articfact. More about it here: http://blogs.msdn.com/b/vssharepointtoolsblog/archive/2009/11/23/how-to-deploy-a-style-sheet-into-content-library-using-visual-studio-2010-beta-2.aspx //M


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]).


3

What you suggest is actually going to break your warranty with Microsoft but there is a safe way of doing it. You can use an event receiver for Site Provisioned / feature stapling, and set the master page in there for the new site. Previous answer that should give you what you need to know: Apply custom master for new site collection and sites under


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