Web Parts and ASP.NET 2.0

Dino Esposito has a nice summary article over at TheServer.NET on his thoughts around ASP.NET 2.0, the Web Part framework it offers, and ideas around where SharePoint could/should go. In the article he designs a realistic component and build it as a SharePoint WebPart (an Amazon search tool) then he builds the same component as an ASP.NET 2.0 WebPart. For awhile we'll have to be playing catchup as ASP.NET 2.0 comes out, then an update to SharePoint to match. In the end they'll be a convergence, just hard to see where or when that will happen so in the meantime we just struggle along our way.

1 Comment

  • The only thing I hope for is that they pay a bit more attention to the resultant html that comes from the web part framework. We have a wss sharepoint portal working as a public internet site for anonymous users. It took a lot of hacking, but it is working great except for some major issues:

    no chance of xhtml, and massive massive client code bloat. The javascript file to do all that fancy drag and drop adds some 100+kb to the download, when we aren't even letting anonymous users modify the web parts. On top of that, the resultant html is packed with a sludge of nested tables.



    I'm not interested in working with sharepoint again until they've resolve these issues - anonymous-user-friendly xhtml and not including the fat .js file when not logged in as admin. In .net 2.0 beta 1 (last time I checked) this had not been fixed.



    If only Sharepoint acted a bit more like PHP's MamboServer on the front end - where getting a valid xhtml site is possible - I'd have the company I consult for using it for everything.

Comments have been disabled for this content.