Tag Info

New answers tagged

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


1

I'd had a similar idea to @RJ Cuthbertson's answer regarding the GAC, but it would not let me uninstall anything from there. Until I found this: IMPORTANT! Never ever do this on a production system, and always turn it back on afterwards. Open Local Security Policy MMC Goto Security Settings -> Local Policies -> Security Options Locate "User Account ...


1

Have you tried commenting out the offending code, rebuilding/repackaging, and then running an Update-SPSolution command? The FeatureUninstalling event occurs on removal, and, I believe, it will not be called when upgrading (that's what the FeatureUpgrading event is for). If you can upgrade successfully and replace the offending code, you would then be able ...



Top 50 recent answers are included