Hot answers tagged

3

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.


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 http://slavensemper.blogspot.hr/2015/08/failed-to-load-...


3

I think this is what you looking for $listApps=Get-WmiObject -Class Win32_Product | Where {$_.IdentifyingNumber -like “*90150000-*”} $listApps | Sort -Property Name | ft -Autosize https://blogs.technet.microsoft.com/stefan_gossner/2015/04/20/powershell-script-to-display-version-info-for-installed-sharepoint-product-and-language-packs/ http://...


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

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

Actually, there's no such thing as "deploying a Web part to a site collection". You deploy a Web part with a WSP package; WSP packages (at least ones that contain Web parts) are deployed against specific Web applications. After that the feature containing the Web part is activated per site collection, but "activating a feature" is only a SharePoint logic (i....


2

The solution I came up with is a temporary fix. I created a shell script to retract, remove and redeploy the solution. So at first I would have a dedicated location to publish my .wsp file than a script using the new .wsp. Script is given below: $webApplicationUrl = "http://my-dev/" $siteUrl = "http://my-dev/site1" $solutionName = "...


2

Execute Get-ChildItem "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall" | where-object { $_.PsPath -like "*\Office*" } | foreach {Get-ItemProperty $_.PsPath} | fl DisplayName, DisplayVersion one-liner in SharePoint Management Shell and then look up build numbers at Todd Klindt's site. Adapted that from Stefan Goßner`s post long time ago. Refer to ...


1

I think these steps will help to update it. Complete Uninstall the Solution( deactivate, Uninstall and Remove) Reset IIS Reset the SharePoint admin and Timer Service. Deploy new Solution Test now.


1

You are right, there is no option to get verbose. I would say the only way to do that is to do it manually --> meaning you log each step to a text file from start to finish and this will get you a little bit of information on where it stopped (maybe try that on a DEV environment and once you figure the issue and fix it, trim the logging part and deploy to ...


1

there are couple of reasons for this error. if you have antivirus installed on the server, then make sure it is not blocking those dll to deploy. make sure SharePoint timer and Admin services running on all servers May be restart the time service and admin service on all sever, some time timer service lock the files on the server. also check if you package ...


1

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 And please refer this link it may help you Error occurred in deployment step 'Recycle IIS Application Pool'


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.


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

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

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


1

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



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