Building SharePoint Web Parts? Then this post (excerpted below) from Dino Esposito is a must read:

WebParts: From SharePoint to ASP.NET 2.0

In the Windows world, SharePoint products and technologies simplify and support various forms of collaboration between partners within a company or an organization. The pages of a Web site based on SharePoint can contain special components named WebParts which are specifically designed to provide personalized and customizable windows of information to users. In the end, Web Parts are ASP.NET controls with an extra layer of code that make them interact with the SharePoint framework. So far so good. What about Whidbey and the next version of the .NET Framework?


   Update (03/21/2005): Here's the official word on SharePoint Web Parts vs. ASP.NET 2.0 Web Parts from Mike Fitzmaurice:

Keep Writing SharePoint Web Parts Until (at least) 2006


ASP.NET 2.0 Web Parts rock. We in SharePoint-land love them. We’re building “v3” on ASP.NET 2.0. But none of that matters right now if you have to deliver code for today’s SharePoint sites and portals. And this advice comes from both me in WSS/SPS-land and the Whidbey Program Manager responsible for ASP.NET 2.0 Web Parts. Here’s the official word on Whidbey/WSS interoperability and compatibility:

  • WSS “v3” (and anything built on top of it like SPS) is being written with ASP.NET 2.0, and will use, natively, ASP.NET 2.0 Web Parts.
  • WSS “v3” (and anything built on top of it like SPS) will carry forward the object models used for SharePoint Web Parts, so it will continue to run anything being written today.  Natively. Anything you write today will still work tomorrow.
  • ASP.NET 2.0–only sites that do not involve SharePoint technology will only run ASP.NET 2.0 Web Parts.


   Also, here’s one of the best articles that I’ve seen (ever) about SharePoint. It’s both insightful and accurate (at least based on my field experience in successfully selling SharePoint against the competition and consistently seeing the rapid growth of SharePoint deployments in practically all of my customer accounts).


Microsoft Watch Uncovers the Secrets behind SharePoint Portal Server’s Success


Microsoft Office SharePoint Portal Server 2003 provides low total cost of ownership and an elegant solution to a complicated problem. Its true strength, however, may lie in its XML-driven integration capabilities. Microsoft Watch reporter, Mary Jo Foley, goes behind the scenes with business portal group general manager Jeff Teper to uncover the keys to the success of SharePoint Portal Server 2003 and figure out why it’s one of the fastest selling products in Microsoft history.