Web Parts and Personalization

Re: Multiple Webparts on shared profile

mharder — Fri, 04 Jun 2004 17:41:35 GMT

All WebParts are parented to the WebPartManager, and all WebParts are required to have an ID.

For a static WebPart (a WebPart in the ZoneTemplate of a WebPartZone), you must specify the ID in the persistence format, so the UniqueID of the WebPart is the ID of the WebPartManager, plus the ID of the WebPart itself.

When you add a dynamic WebPart, we generate a random ID for the WebPart. However, this ID will stay the same as long as the WebPart is on the page. We need the ID to stay constant, since the WebPart ID is used as the key for storing Personalization data.

Re: Multiple Webparts on shared profile

Fredrik N — Sun, 30 May 2004 23:02:50 GMT

Basically yes, but you can't if you add a WebPart dynamically, for example, if you create a WebPart that inherits the WebPart class, the Unique ID will be changed every time for the WebPart if you add it dynamically to a Zone in your server code. But if you add the WebPart to the WebPartZone in the ASP.Net page (Source view) it will always have the same Unique ID if you don't change the WebPartManger ID or the WebParts ID in the future. If you add a server control or a user control to a WebPartZone (controils that doesn’t inherit the WebPart class), the WebPartZone control will create a GenericWebpart that will have the same UniqueID, as long as the ID of the control is the same.

Multiple Webparts on shared profile

dcanevet — Sun, 30 May 2004 20:26:49 GMT

Hi,

I have a webform having multiple WebPartZones. I designed a custom personalizable webpart that I put this webpart many times in my page. This configuration is stored in the shared profile.
Can I be sure each instance of my custom webpart will always have the same Unique ID? (independently of other controls on my page, of other webparts in my zone, and independently of the logged-in profile!)

Regards,
Denis