Tag Info

Hot answers tagged

1

In this scenario you can actually use the -force attribute on Enable-SPFeature, since it will reenable the feature. But I normally uses your approach, but I use the ID of the feature and not the actual $Feature object: $FeatureId = $Feature.Id Disable-SPFeature $FeatureId -URL $oneweb.URL -Confirm:$False Enable-SPFeature -$FeatureId -URL $oneweb.URL ...


1

Proper way to remove the feature is Restract from the Site collections /Sites. i,e powershell Disable-SPFeature Uninstall it i.e powershell UUninstall-SPSolution Remove it. i.e powershell Remove-SPSolution Now as it become orphan, you can remove either way use this SharePoint Feature Administration and Clean Up Tool to identify and remove them You can ...


1

You should structure your features in a way that makes sense to your project. The key aspect of features is that they can be turned on and off on a site. The simplest thing to do is to put all your stuff in one feature, but that may or may not be the best solution in your case. Whether a feature is automatically activated on deployment depends on a few ...


1

There is nothing call Install Feature. When you deploy a new solution this is what happens. It first add the solution to farm. Then deploy the solution. If you have set the features to activate on the deployment in the Feature settings, it activates. You do not need to have one feature per webpart. It depends on the requirement. You can even handle with ...



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