Cheers,
yep.. asp.net based webpart looks the way to go.
On Mon, Jun 21, 2010 at 11:25 AM, Joseph Clark jcl...@atlassian.com wrote:
Hi Ajay,
The literature I have read suggests that you should use the vanilla
ASP.NET base web part, unless you have a specific need for the additional
functionality exposed by the SharePoint base web part. They are basically
the same, except that the SP WebPart exposes a couple of extra convenience
functions for SharePoint that are difficult to do otherwise (for example,
serializing web part properties directly to the Content DB).
Unfortunately the book didn't go in to any additional detail about *why*this
was the preferred approach. I suspect that, as the
ASP.NET base web part is the newer of the two, that the SharePoint base
web part may eventually be folded in to it.
Hope this helps,
Joe.
On Sat, Jun 19, 2010 at 3:50 PM, Ajay akhanna...@gmail.com wrote:
I have to create a SP 2010 web part with a custom toolpart.
Which one should I use -- asp.net webparts class or
Sharepoint.webcontrols.webpart.
Since both are inside the project template created by VS.
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
