Should my connected web parts support IWebPartField, IWebPartRow and IWebPartData?
Posted
by Javaman59
on Stack Overflow
See other posts from Stack Overflow
or by Javaman59
Published on 2010-05-21T02:45:28Z
Indexed on
2010/05/21
2:50 UTC
Read the original article
Hit count: 577
I've been writing some simple webparts, and they communicate via a custom interface type. That's working fine.
I've got one ConnectionProvider, with a variety of ConnectionConsumers.
I see that the OOTB SharePoint webparts provide many standard connections, apparently through IWebPartField and IWebPartRow (IWebPartData seems less supported).
I've tried to add a IWebPartRow interface to a provider, and found that it's not actually useful (apparently), unless it's shareing data that the OOTB components use, such as images, urls and users. Well, that's the impression I got, anyway... I've only done a quick experiment, and found it quite difficult to implement and test.
Is there any point in spending time trying to add support for the standard webpart interfaces?
© Stack Overflow or respective owner