Tag Info

New answers tagged

0

I'm pretty sure I used similar code not that long ago and didn't encounter any issues. Will have to get home and spin up my test VMs to confirm. Thanks for this clear code sample - it should come in handy for quite few people out there :)


0

Ideally you should leverage feature upgrade functionality. Take a look at this example: http://spblog.net/post/2011/05/02/How-to-upgrade-feature-in-SharePoint-2010.aspx Also, a bit closer to your situation (if you use content types to provision list/library fields): ...


1

The feature activated event will not fire again as it is already activated. However, the webpart will get updated because new dll, control templates and other components get deployed properly.


1

The feature will also need to be activated in order for web part to show up. The next time you deploy a WSP, the feature will remain activated/deactivated depending on its state. That is, if the feature is activated and you deploy the WSP again, you won't need to activate the feature. However, if it is deactivated, it need to be activated again.


1

As is evident from the first error there is an issue with finding assembly information. This may mean you may have changed namespace, class name etc. Normally AlwaysForceInstall = true should take care of the feature which is not uninstalled. Value TRUE specifies that the Feature is installed by force during installation even if the Feature is already ...


0

Try this free tool from community! Using this tool you can remove faulty features. I hope that the error will disappear. May be solve your trouble!


1

The Event Receivers can only be Scope at Site or Web. http://msdn.microsoft.com/en-us/library/office/ms431081(v=office.14).aspx I believe you would need to use a Feature Stapler. For existing sites, you will need to activate the feature manually, either using the UI, or powershell loop that activates the feature everywhere. Then you need a feature ...


2

There is a more fail-safe approach than what @lwbecker2 suggests Get-SPSolution | ? { $_.JobExists } | % { Write-Host "Deployment job is currently running" } This has the benefit of not having a race condition. If you only look for the timer job, it may be that a deployment has already been initiated, but a timer job was not yet created when you check for ...


0

There is no direct equivalent for stsadm -o enumdeployments, but since the deployments are run by Timer Jobs you can query and filter the running timer jobs to achieve your desired result: From : Enumberate(sic) running Deployments using PowerShell $list = Get-SPTimerJob | ?{$_.Name.IndexOf("solution-deployment") -ne -1) If you know the name of ...



Top 50 recent answers are included