The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

Rickee (15) [Avatar] Offline
#1
Section 5.1.8 int he PDF version (as of July 30th, 2010) implies that one might use both the WebPartStorage and the Personalizable attributes on the same property. Actually, the SharePoint developers tell me that there is only one situation in which one might have both: If you have a Web Part that was developed way back with Windows SharePoint Services 2.0 and it had the WebPartStorage attribute, then to update its serialization to the recommended ASP.NET system, the Personalizable attribute is added and the Web Part is rebuilt and re-deployed. The first time someone modifies the property the presence of the WebPartStorage attribute enables it to be deserialized using the old SharePoint method. Then when the change is saved, it is re-serialized by the ASP.NET method because the Personalizable attribute takes precedence over the WebPartStorage attribute. From then on, whenever the Web Part property is changed, the ASP.NET method is used to both serialize and deserialize. At that point, one could remove the WebPartStorage attribute and again rebuild and redeploy.