Tag Info

New answers tagged

0

Maybe you received the TypeLoadException because you forgot to add the referenced assembly to the "Additional Assemblies" of your package. To do this double click the package item in your SharePoint project -> "Advanced" -> "Add" -> "Add Assembly from Project Output...".


2

Make sure to not use SPContext.Current in the FeatureReciever, this will be NULL in powershell (due to lack of HttpContext basically). This is one of the most common cause of errors in FeatureReceivers


2

I would suggest that you break the whole thing into two features, first one to deploy the List Template and second one to create the instance of the list based on template.. On the later one, you will need to define Feature Activation Dependency of List Template feature.. Both features can be hidden and you just need to activate the Feature that creates ...


2

function Deactivate-SPFeature { param ($FeatureID, $SiteUrl, $WebApplicationUrl) $Feature = Get-SPFeature -Identity $FeatureID -ErrorAction SilentlyContinue $IsActiveFeature If ($Feature -eq $null) { Write-Warning "The specified feature ($FeatureID) was not found." return } If ($Feature.Scope -eq ...


1

Usually when you have to do a deploy (install, upgrade, enable/disable features, and so on) you want do that with a Powershell script written before. In this way you will be able to check your feature (hidden or not), disable it (if you can), upgrade, and etc.


0

Is the publishing feature enabled at the site collection level? A publishing site normally starts at the site collection level and that is also where the Style Library should live, which holds files that apply to all sites in the site collection. A publishing site uses page layouts and other things that are also defined at the site collection level, not in ...



Top 50 recent answers are included