Hot answers tagged

3

The so-called "best practice" from MSoft is called "remote provisioning". This is basically using CSOM (or JSOM) to provision the site structure. Any environment that allows REST access and the proper permissions can be used to do this, including ConsoleApp, PowerShell, Javascript, provider-hosted app, et.al. I learned about this in the excellent MVA course ...


3

My solution to the problem was to change assembly version from 1.0.0.0 to 1.0.0.1 and build the SharePoint project. After that I deleted feature receiver and added feature receiver again so that feature manifest XML file gets updated with correct version of feature receiver assembly. More details on ...


2

Web application scoped features are automatically activated at WSP deployment. This is controlled by the ActivateOnDefault property you can find in the property window of the feature in VS. See https://msdn.microsoft.com/en-us/library/ms436075.aspx and the ActivateOnDefault attribute.


2

I'm also relatively new to SharePoint development, but will try share some of my experience. :) When I created new code/functionality to a site, I make sure that I 'deactivate' the webpart/feature, then under your Admin Settings I retract the solution from the farm. Before I package the solution in Visual Studio, I update both the .feature title and ...


2

You can add 'PreBuild' or 'Post-Deployment' command ECHO ------ %TIME% ------ or change verbosity option to 'Normal' in Options -> Project & Run -> Build & Run Refer this link for details and screen-shot.


2

I faced the same problem, but couldn't install Search Server Express (won't install on Windows 7) nor could I install SharePoint 2010 (not Foundation) to copy the required DLLs. OS: Windows 7 Professional VS: Visual Studio Professional 2013 SP: SharePoint Foundation 2010 My steps to get this working: Download Search Server Express Extract: ...


2

The instruction how to update an existing workflow if it’s necessary to make changes to the workflow, but all running workflows must keep going: Add ReplaceContent="TRUE" to Elements.xml files of workflow and workflow activities. Create a wsp package with updated workflow/workflow activities. Update the solution using the Update-SPSolution cmdlet. Force ...


2

I think I had success with this by using the Overwrite=True attribute (https://msdn.microsoft.com/en-us/library/office/aa544268.aspx). Also I believe once the content type is in use in a list instance it might be blocked from being removed. Try deleting the instance and then clearing it from both the first stage and second stage recycle bin then ...


2

Here is the powershell command to deploy WSP to particular web application only : Install-SPSolution your_solution_name.wsp –webapplication http://server1:123 –GACDeployment


2

SharePoint solutions (non-sandboxed) can be deployed at both two scopes "Globally" and "Web Application". As stated by bloger Jan Steenbeek at Deploying solutions to a specific Web Application: "SharePoint has the annoying" (Debatably) "habit of forcing you to deploy globally whenever possible. When you try to deploy a global solution to a specific url ...


1

I think I found an answer but not in powershell. Content Migration object model says: Content Migration object model: The object model provides the most control over your data migration scenarios. Using the object model, you can migrate anything, from a Web site to an item in a list, or a single document in a library. You can choose whether to include ...


1

Make sure SharePoint Timer Service is running on all servers.


1

I have resolved it!! As powershell did not help me. I have nothing left other than manually digging database. So I have searched WSS_Content database and found those entries in WSS_Content.dbo.CustomActions table. Removing those fixed the issue. We have deleted entries whose FeatureId is 00000000-0000-0000-0000-000000000000 Not sure if this is the ...


1

Short answer: a WSP cannot be deployed on a given Web app. First of all, a WSP can contain different artefacts: _layousts files (application pages, JavaScript, CSS, images...): those "resources" are by definition available to all the SharePoint farm. Features Features that embed a Web part or anything else that requires a web.config modification. In ...


1

I solved this in SharePoint(2013) Central Administration/Application Management/Manage Services on Server by starting the Microsoft SharePoint Foundation Sandboxed Code Service


1

https://books.google.co.in/books?id=q_L_jQ4VYpsC&pg=PT300&lpg=PT300&dq=create+features+elements+file,&source=bl&ots=2T5lGxMUfh&sig=D5G3Zp-_6rvt7Gs-XZHCoCjGMYQ&hl=en&sa=X&ved=0CEMQ6AEwBWoVChMIheak4vSbyAIVjFuOCh1RyASL#v=onepage&q=create%20features%20elements%20file%2C&f=false This may help. Gives an overview from ...


1

I was facing the same issue recently. To solve this, I just removed the entries in 'Safe Controls' and 'Class Resources' section and saved 'Edit Existing Assembly' form. Then, it got deployed without issue.


1

Did you try adding ReplaceContent="True" to your module XML? Maybe the problem lies in SharePoint ignoring the file as it already exists in the targeted folder.


1

Deactivate your features and delete the pages. Reactivate the features and they'll be provisioned again. My rule of thumb was if I was deploying assets, I had feature deactivation code to delete them. This made rapid development deployment possible by right clicking deploy in VS. The feature would retract, delete the deployed assets, be removed form the ...


1

I suggest you to try the GACUtil tool to try to deploy your assembly, just to test if it is deployable to the GAC at all. If the deployment still fails, this tool might provide you additional information about the reason of the error, that you can use to resolve the issue itself.


1

Select the project file in Solution Explorer and press F4 (or View, Properties Window). In the properties which appear in the new window, there is a Site URL:


1

The function “GetSPSolutionLastDeploymentSucceeded” is useful to find out whether the last solution deployment succeeded and to output the last operation details which includes error information if there was a failure. function GetSPSolutionLastDeploymentSucceeded([string]$solutionName) { # Get the solution again to make sure all deployment info is ...


1

You need something like the following: $solution = "example.wsp" Install-SPSolution -Identity $solution $deployed = $False while ($deployed -eq $False) { sleep -s 5 $s = Get-SPSolution -Identity $solution if ($s.Deployed -eq $True -And $s.JobExists -eq $False) { $deployed = $True } }


1

The restored workflow can be started by any user having the Edit Items permission on the list where the workflow is. To edit the workflow, users with Manage Lists permission can change the workflow. It doesn’t matter who created the workflow, it will still be in place and functioning even if your user doesn’t exist in the production environment. To add a ...


1

First, I would remove the "$Resources" part in the Display Name of your definitions (if you don't use resource files). Check this question : How can I provision a list with a calculated field? (there is a comment saying that InternalNames are required, and there is this link http://www.hekstra.org/how-to-deploy-a-calculated-field/ saying that Site Column = ...


1

It has been a while since I did this. I agree with taking out the $Resource part. And yes Formulas use DisplayName as references, I have never used the ID in the FieldRefs And try it with an existing field first <Field> ... <Formula>=Title</Formula> <FieldRefs> <FieldRef Name="Title" /> </FieldRefs> </Field> ...


1

From your project in Visual Studio, right click on the project name and click on Properties. From there choose the SharePoint tab and in the Active Deployment Configuration choose No Activation.



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