Timeline for Enable feature of SharePoint sandbox solution
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2012 at 8:16 | comment | added | Anders Rask | yeah you don’t want to swallow exceptions to determine flow control :-S At least its not expensive in newer versions of C# (as long as you dont throw) | |
| Jun 20, 2012 at 7:13 | comment | added | SPArcheon - on strike | ^_^'... aka the "try-catch-swallow" pattern... I don't know why, but I'm NOT surprised... Anyway, nice find @AndersRask | |
| Jun 19, 2012 at 10:30 | comment | added | Anders Rask | A little curiosity here for the interested: Since SPFeatureDefinition that is used by Enable-SPFeature uses SPFarm when it Read()'s the pipebind, it obviously cant really be used for sandboxed solutions. This triggered my curiosity to find out why it actually works (as it does) for -Identity <guid>. It turns out that in InternalValidate() of the cmdlet a SPCmdletPipeBindException is swallowed(!) and SPSitePipeBind is used to fetch site, and then a specific Read(SPSite siteScope, bool sandboxedFeatureDefinitions) is called. | |
| Nov 5, 2011 at 18:48 | vote | accept | Alexander | ||
| Oct 21, 2011 at 14:34 | history | answered | SPArcheon - on strike | CC BY-SA 3.0 |