Web Parts in Whidbey


I have been spending a little time recently looking at web parts in ASP.NET 2.0.  That's right, if you didn't know already the web part infrastructure becomes a fully fledged part of ASP.NET with the 2005 release of Visual Studio.  The really great thing about it is the superb developer support - but what more would you expect from the Developer Tools group?

In ASP.NET 2.0 any of the standard web server controls can be used as a web part.  Not only that, any user controls or custom server controls you have already written in previous versions of ASP.NET can be used as web parts too!  And if you want to make more extensive use of the web part infrastructure you can derive from the WebPart class in the .NET Framework.

If you want to go have a play yourself you'll need the Visual Studio 2005 Beta which you can get from the MSDN Developer Centre.

Comments (4)

  1. . says:

    Next they are going to ship a whole blog reader construction library as part of System.Web.dll in .NET Framework 3.0.

    The thing will finally be so big that no one wants to download it anymore 🙂

  2. Jan Tielens says:

    Hi Mark

    Can you use the Webparts in ASP.NET and Whidbey also in SharePoint (maybe a future version)? I would think so, because they are both named Webparts…

    Btw, you can use any ASP.NET 1.1 user control as a webpart already if you want to. Check out the SmartPart! 😉 http://workspaces.gotdotnet.com/smartpart

  3. Mark Bower says:

    Yes, you’ll be able to use Whidbey web parts in SharePoint, but you will need to wait for an updated version of SharePoint that adds support for ASP.NET 2.0 to do that. Web Parts you write today for SharePoint should be fully compatible with ASP.NET 2.0.

Skip to main content