Initially, the web part development
model was based on VBScript, which is not what most developers would call their favorite
development language or environment. In SharePoint Server 2003, Microsoft more closely
integrated SharePoint with ASP.NET, providing namespaces for supporting web part development
in .NET. With .NET Framework 2.0, the ASP.NET team integrated the web part infrastructure
and development model within ASP.NET itself. However, the two web part models remained
separate. Building web parts that targeted both ASP.NET 2.0 and SharePoint Server 2003 required
custom compilation, since different namespaces and base classes where required. In Microsoft
Office SharePoint Server (MOSS) 2007, SharePoint is completely integrated with and built on
ASP.NET 2.0. This means that you can build web parts for MOSS using the ASP.NET WebPart
base class.
?– Note Microsoft recommends inheriting from the ASP.NET WebPart base class whether developing for
pure ASP.NET or SharePoint.
The next section provides a brief overview of the ASP.NET web part infrastructure to set
the state for building web parts that take advantage of this framework.
Web Part Infrastructure
One of the features of WebPart-based applications is personalization.
Pages:
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574