Why use SPPersistedObject instead of property bag for Farm and WebApp?

Jun 13, 2012 at 11:21 PM


I just plummeted down the valley of despair when I realized the CodePlex “SharePoint Property Bag Settings 2010” [editor] could not be used to set my Farm and Web Application settings, because those are based on the SPPersistedObject child object.

So unless someone has made a generic SPPersistedObject editor for the PnP Settings Manager this just got a whole lot harder (and the framework - less valuable).

First, what was the technical basis for the inconsistency in implementation between Web and WebApp/Farm settings storage techniques?