![Web Parts – Custom Web Parts (cont.) public class MyWebPart : WebPart { public override WebPartVerbCollection Verbs { get { EnsureChildControls (); WebPartVerb verb = new WebPartVerb (new WebPartEventHandler (OnClearResults)); verb.Text = "Clear Results"; WebPartVerb[] verbs = new WebPartVerb[] { verb }; return new WebPartVerbCollection (base.Verbs, verbs); } } void OnClearResults (object sender, WebPartEventArgs args) { ... } ... }](https://image.slidesharecdn.com/aspnet2overview-100126122429-phpapp01/85/Aspnet2-Overview-37-320.jpg)
Aspnet2 Overview
- 1. ASAP to ASP.NET 2.0 Noam King CTO Sela youniversity
- 2. Agenda Introduction Architecture Master Pages Personalization Building a site with Web Parts. Skins and Themes Administration & Management Site Navigation (Optional) Handling data with ASP.NET 2.0 (Optional) Summary
- 3. Introduction to ASP.NET 2.0 Data Controls Login Controls Web Parts Other New Controls Master Pages Themes and Skins Mobility and Localization Compilation Membership Role Management Profiles Configuration Site Maps Health Monitoring Other Services Controls Page Framework Services and APIs
- 4. Architecture
- 5. Architecture – Code Model ASP 1.1 ASP 2.0
- 6. Architecture – Coding Model (cont.) Reduced Inheritance Complexity No need for declaration code Code is linked by VS2005 and the runtime Reduced Compilation Complexity Code-behind automatically synchronized with aspx page More compilation models
- 7. Architecture – Coding Model (cont.) Compilation Normal Similar to Asp 1.1 Batch Compilation Like in asp1.1 <compilation batch ="true|false" batchTimeout ="number of seconds" maxBatchSize ="maximum number of pages per batched compilation" maxBatchGeneratedFileSize ="maximum combined size (in KB) of the generated source file per batched compilation“ </compilation>
- 8. Architecture – Coding Model (cont.) Compilation (cont.) Deployment pre-compilation aspnet_compiler /v /<websitename> –p <source> HTML pages, resources, configuration files, and ASPX pages are copied separately. Stub files for the various aspx pages. Increased performance and increased security.
- 9. Architecture – Coding Model (cont.) Compilation (cont.) In Place Compliation http:// localhost/mywebsitename/precompile.axd Eliminate performance hit of batch compilation Let you find compilation errors before your users do. Full Runtime Compilation (The Code Directory) the \Code directory is designed for storing class files to be compiled dynamically at run time. Simple deployment
- 10. Architecture – Page LifeCycle Constructor Construct TestDeviceFilter AddParsedSubObject DeterminePostBackMode OnPreInit LoadPersonalizationData InitializeThemes OnInit ApplyControlSkin ApplyPersonalization OnInitComplete LoadPageStateFromPersistenceMedium (PB) LoadControlState (PB) LoadViewState (PB) ProcessPostData1 OnPreLoad OnLoad ProcessPostData2 (PB) RaiseChangedEvents (PB) RaisePostBackEvent (PB) OnLoadComplete OnPreRender OnPreRenderComplete SavePersonalizationData SaveControlState SaveViewState SavePageStateToPersistenceMedium Render OnUnload PB = Post Back
- 11. Architecture – Code Page Posting If Page.IsCrossPagePostBack Then Label1.Text = “Hello “ & PreviousPage.pp_Textbox1.Text & “<br />” & _ “ Date Selected: “ & _ PreviousPage.pp_Calendar1.Sele ctedDate.ToShortDateString() Else Response.Redirect(“Page1.aspx”) End If
- 12. Architecture - Extensibilty New HttpModules SessionID Role Management Anonymous Identification Profile Page Counters New Handlers WebAdminHandler TraceHandler WebResourcesHandler PrecomHandler More…
- 13. Architecture – Performance Improved Request Pipeline Up to 30% percent improved request stack Improved Memory management with IIS6 Working set for the worker process reduced by around 50%. General improvements on II6 More to come in the release
- 14. Master Pages
- 15. Master Pages - Basics Masters define common content and placeholders (<asp:ContentPlaceHolder>) Content pages reference masters and fill placeholders with content (<asp:Content>) <%@ Master %> <asp:ContentPlaceHolder ID="Main" RunAt="server" /> <%@ Page MasterPage- File="Site.master" %> <asp:Content ContentPlaceHolderID= "Main" RunAt="server" /> </asp:Content> Site.master default.aspx http://.../default.aspx
- 16. Master Pages – Defining and applying Defining <%@ Master %> <%@ Page MasterPageFile="~/Site.master" %> <asp:Content ContentPlaceHolderID="Main" RunAt="server"> This content fills the place holder "Main" defined in the master page </asp:Content> Applying
- 17. Master Pages Applying to a site <configuration> <system.web> <pages masterPageFile="~/Site.master" /> </system.web> </configuration> Sub Page_PreInit (ByVal sender As Object,ByVal e As EventArgs) Page.MasterPageFile = "~/Site.master" End Sub Applying Programmatically
- 18. Master Pages – Weak Typing (CType(Master.FindControl ("Title"), Label).Text = "Orders" In the content page… <asp:Label ID="Title" RunAt="server" /> In the master page…
- 19. Master Pages – Strong Typing Master.TitleText = "Orders" In the content page… <asp:Label ID="Title" RunAt="server" /> . . . <script language=“VB" runat="server"> Public Property TitleText as string Get return Title.Text End Get Set Title.Text = value End Set End Property </script> In the master page…
- 20. Master Pages - Nesting Master Page IDF (idf.master) Master Page IDF North (idfnorth.master) Master Page IDF South (idfsouth.master) Content page1 (default.aspx) Content Page2 (default2.aspx) Content Page3 (default3.aspx) Content Page4 (default4.aspx)
- 21. Master Pages – Nesting (cont.) Master pages that have masters must contain only Content controls, but Content controls can contain ContentPlaceHolders <!-- Orders.Master --> <%@ Master MasterPageFile="~/Site.Master" %> <asp:Content ContentPlaceHolderID="..." RunAt="server"> <asp:ContentPlaceHolder ID="..." RunAt="server"> ... </asp:ContentPlaceHolder> <asp:Content>
- 22. Master Pages - Container-Specific <%@ Page Language=”VB” MasterPageFile=”~/Sela.master” Mozilla:MasterPageFile=”~/SelaMozilla.master” Opera:MasterPageFile=”~/SelaOpera.master” %> <asp:Content ID=”Content1” ContentPlaceHolderId=”ContentPlaceHolder1” Runat=”server”> Hello World </asp:Content>
- 23. Master Pages – Event order Master page child controls initialization Content page child controls initialization Master page initialization Content page initialization Content page load Master page load Master page child controls loadContent page child controls load
- 24. Personalization
- 25. Personalization - Overview Automatic association between the end user viewing the page and any data points stored for that user. The personalization properties that are maintained on a per-user basis are stored on the server and not on the client. The end user can access these personalization properties on later site visits. Ideal way to start creating highly customizable and user-specific sites without massing with all the underlined code.
- 26. Personalization – Defining & Using <configuration> <system.web> <profile> <properties> <add name=”FirstName” /> <add name=”LastName” /> </properties> </profile> </system.web> </configuration> Profile.FirstName = TextBox1.Text Configuration Using
- 27. Personalization - Groups <group name=”MemberDetails”> <add name=”Member” /> <add name=”DateJoined” /> <add name=”PaidDuesStatus” /> <add name=”Location” /> </group> Label1.Text = Profile.MemberDetails.DateJoined Configuration Using
- 28. Personalization - Types Define types to the fields Use default values to the fields Define readonly for fields Create custom types for fields and serialization type. <add name=”Field name” type=”FieldType” serializeAs=”Binary” />
- 29. Web Parts
- 30. Web Parts Orchestrates operation of Web Parts Maintains list of Web Parts and zones Manages page state (e.g., display mode) and fires events when page state changes Facilitates communication between Web Parts Manages personalization and much more One instance per page; not a visible control. <asp:WebPartManager ID="WebPartManager1" RunAt="server" />
- 31. Web Parts - WebPartZone Defines zones on a Web Parts page Defines default layout and appearance of Web Parts within each zone <asp:WebPartZone ID="WeatherZone" DragHighlightColor="244,198,96" RunAt="server" > <PartTitleStyle BackColor="#2254B1" ForeColor="White" /> <PartStyle BorderColor="#81AAF2" BorderStyle="Solid" BorderWidth="1px" /> <ZoneTemplate> <!-- Web Parts declared here --> </ZoneTemplate> </asp:WebPartZone>
- 32. Web Parts - Controls Controls defined in a WebPartZone Web controls, user controls, custom controls Controls that don't implement IWebPart are internally wrapped in GenericWebParts Adds properties: Title, Description, etc. <ZoneTemplate> <asp:Calendar Title="Calendar" ID="Calendar1" RunAt="server" /> <user:Weather Title="Weather" ID="Weather1" RunAt="server" /> <custom:Search Title="Search" ID="Search1" RunAt="server" /> </ZoneTemplate>
- 33. Web Parts – WebPartManager & WebPartPage Menu Gets and sets the page's display mode Value Description BrowserDisplayMode "Normal" display mode; no editing (default) EditDisplayMode Permits editing of Web Parts' appearance and behavior DesignDisplayMode Permits drag-and-drop layout editing CatalogDisplayMode Permits Web Parts to be added to the page ConnectDisplayMode Permits connections to be established between Web parts <asp:WebPartPageMenu ID=”Webpartpagemenu1” Runat=”server”> </asp:WebPartPageMenu>
- 34. Web Parts – Catalog Zone <asp:CatalogZone ID="CatalogZone1" Runat="server"> <ZoneTemplate> <asp:PageCatalogPart ID="PageCatalogPart1" Runat="server" /> <asp:DeclarativeCatalogPart ID="DeclarativeCatalogPart1" Runat="server"> <WebPartsTemplate> <!-- Declarative Web Parts go here --> </WebPartsTemplate> </asp:DeclarativeCatalogPart> <asp:ImportCatalogPart ID="ImportCatalogPart1" Runat="server" /> </ZoneTemplate> </asp:CatalogZone> DeclarativeCatalogPart
- 35. Web Parts - EditorZone <asp:EditorZone ID="EditorZone1" Runat="server"> <ZoneTemplate> <asp:AppearanceEditorPart ID="AppearanceEditorPart1" Runat="server" /> <asp:BehaviorEditorPart ID="BehaviorEditorPart1" Runat="server" /> <asp:LayoutEditorPart ID="LayoutEditorPart1" Runat="server" /> </ZoneTemplate> </asp:EditorZone>
- 36. Web Parts – Custom Web Parts Any control can serve as a Web Part, but… Controls that derive from WebPart can better leverage the Web Parts infrastructure Control Title and other UI-related properties Control AllowClose, AllowZoneChange, AllowMinimize, and other behavioral properties Apply role-based security (authorization filters) Add custom verbs, export Web Parts, and more
- 37. Web Parts – Custom Web Parts (cont.) public class MyWebPart : WebPart { public override WebPartVerbCollection Verbs { get { EnsureChildControls (); WebPartVerb verb = new WebPartVerb (new WebPartEventHandler (OnClearResults)); verb.Text = "Clear Results"; WebPartVerb[] verbs = new WebPartVerb[] { verb }; return new WebPartVerbCollection (base.Verbs, verbs); } } void OnClearResults (object sender, WebPartEventArgs args) { ... } ... }
- 38. Skins And Themes
- 39. Skins and Themes - Overview Mechanism for theming controls, pages, and sites by group-initializing control properties Skin = Visual attributes for control(s) Physically stored in .skin files Default skins and named skins Theme = Collection of one or more skins Physically stored in Themes subfolders Global themes and local themes
- 40. Skins and Themes - Applying <%@ Page Theme="BasicBlue"> <configuration> <system.web> <pages theme="BasicBlue" /> </system.web> </configuration> Sub Page_PreInit (ByVal sender As Object, ByVal e As EventArgs) Page.Theme = "BasicBlue" End Sub On a page On a Site Programmatically
- 41. Skins And Themes – Global Themes BasicBlue Smoke-AndGlass SKIN SKIN SKIN SKIN ASP.NET-ClientFiles Theme name = Subdirectory name
- 42. Skins and Themes - Local Themes Shocking-Pink Autumn-Leaves SKIN SKIN SKIN SKIN vroot Theme name = Subdirectory name
- 43. Skins and Themes – Named Skins Skins without SkinIDs are default skins Skins with SkinIDs are named skins SkinIDs must be unique per control type Can be defined in same SKIN file as default skins or in separate files Use controls' SkinID properties to apply named skins
- 44. Skins and Thems – Named Skins (Defining and Using) <!-- Default look for DropDownList controls --> <asp:DropDownList runat="server" BackColor="blue" ForeColor="white" SkinID="Blue" /> <!-- Default look for DataGrid conotrols --> <asp:DataGrid runat="server" BackColor="#CCCCCC" BorderWidth="2pt" BorderStyle="Solid" BorderColor="#CCCCCC" GridLines="Vertical" HorizontalAlign="Left" SkinID="Blue"> <HeaderStyle ForeColor="white" BackColor="blue" /> <ItemStyle ForeColor="black" BackColor="white" /> <AlternatingItemStyle BackColor="lightblue" ForeColor="black" /> </asp:DataGrid> ... <asp:DropDownList ID="Countries" SkinID="Blue" RunAt="server" />
- 46. A&M - Overview Administrative tools ASP.NET MMC snap-in Web Site Administration Tool (Webadmin.axd) Configuration API Read/write access to configuration settings Simplified custom configuration sections Instrumentation Perf counters, health monitoring, and more
- 47. A&M – ASP.NET MMC Snap-In GUI for applying configuration settings
- 48. A&M – Web Site Administration Tool (WAT) Browser-based admin GUI Invoked by requesting Webadmin.axd or using the "ASP.NET Configuration" command in Visual Studio's Website menu
- 49. A&M – Configuration class Gateway to the configuration API Provides merged view of configuration settings for machine or application AppSettings and ConnectionStrings properties provide access to <appSettings> and <connectionStrings> sections Sections and SectionGroups properties provide access to all other sections
- 50. A&M – Configuration Class Methods Name Description GetExeConfiguration Returns a Configuration object representing config settings for a managed EXE GetMachineConfiguration Returns a Configuration object representing configuration settings for the specified server GetWebConfiguration Returns a Configuration object representing configuration settings for the specified Web application GetSectionGroup Returns a ConfigurationSectionGroup object representing the specified section group Update Records changes in the relevant configuration file GetSection Returns a ConfigurationSection object representing the specified section (e.g., <appSettings>
- 51. A&M – Configuration class properties Name Description AppSettings Returns an AppSettingsSection object representing the <appSettings> section ConnectionStrings Returns a ConnectionStringsSection object representing the <connectionsStrings> section HasFile True if there's a corresponding configuration file, false if not SectionGroups Returns a ConfigurationSectionGroupCollection representing all section groups Sections Returns a ConfigurationSectionCollection representing all sections Path Path to the app represented by this Configuration object
- 52. A&M – Configuration example (Reading Connection String) ‘ Read a connection string from <connectionStrings> Dim connect As string = ConfigurationSettings.ConnectionStrings("Northwind“).ConnectionString ‘ Add a connection string to <connectionStrings> Dim config As Configuration = Configuration.GetWebConfiguration (Request.ApplicationPath) config.ConnectionStrings.ConnectionStrings.Add (new ConnectionStringSettings ("Northwind", "server=localhost;database=northwind;integrated security=true") config.Update () // Important!
- 53. A&M – ASP.NET Instrumentation Name Description Performance counters New peformance counters supplement the ones introduced in ASP.NET 1.x Windows event tracing Integration with ETW subsystem to support low-overhead tracing of HTTP requests through the system Application tracing ASP.NET trace facility upgraded with new features and to allow coupling to System.Diagnostics.Trace Health monitoring New provider-based subsystem for logging notable events ("Web events") that occur during an application's lifetime
- 54. Handling Data
- 55. Handling Data – DataSource control SqlDataSource Enables you to work with any SQL-based database, such as Microsoft SQL Server or Oracle. AccessDataSource Enables you to work with a Microsoft Access file (.mbd). ObjectDataSource Enables you to work with a business object or a Visual Studio 2005 data component. XmlDataSource Enables you to work with the information from an XML file or an XML source (for example an RSS feed). SiteMapDataSource Enables you to work with the hierarchical data represented in the site map file (.sitemap). DataSetDataSource Enables you to work with data that is represented in a DataSet object .
- 56. Handling Data – Data Bound Server controls <asp:GridView> <asp:DataGrid> <asp:DetailsView> <asp:TreeView> <asp:Menu> <asp:DataList> <asp:Repeater> <asp:DropDownList> <asp:BulletedList> <asp:CheckBoxList> <asp:RadioButtonList> <asp:ListBox> <asp:AdRotator>
- 57. Site Navigation
- 58. Site Navigation - Overview Navigation UIs are tedious to implement Especially if they rely on client-side script New controls simplify site navigation TreeView and Menu - Navigation UI SiteMapDataSource - XML site maps SiteMapPath - "Bread crumb" controls Public API provides foundation for controls Provider-based for flexibility
- 59. Site Navigation - Schema Site Navigation API Site Maps Web.sitemap Other Data Stores Controls Menu TreeView SiteMapPath SiteMap- DataSource SiteMap SiteMapNode SiteMapNode SiteMapNode XmlSiteMapProvider Other Site Map Providers Providers
- 60. Site Navigation – TreeView Example <asp:TreeView ShowLines="true" Font-Name="Verdana" Font-Size="10pt" ... > <SelectedNodeStyle BackColor="Yellow" /> <HoverNodeStyle BackColor="LightBlue" /> <Nodes> <asp:TreeNode Text="Not selectable" SelectAction="None" RunAt="server"> <asp:TreeNode Text="Selectable" SelectAction="Select" RunAt="server" > <asp:TreeNode Text="Click to expand or collapse" SelectAction="Expand" Runat="server"> <asp:TreeNode Text="Click to select and expand or collapse" SelectAction="SelectExpand" Runat="server"> <asp:TreeNode Text="Check box node" ShowCheckBox="true" Runat="server"> <asp:TreeNode Text="Click to navigate" NavigateUrl="..." Runat="server" /> </asp:TreeNode> </asp:TreeNode> </asp:TreeNode> </asp:TreeNode> </asp:TreeNode> </Nodes> </asp:TreeView>
- 61. Site Navigation – Menu Control <asp:Menu Orientation="Horizontal" RunAt="server"> <Items> <asp:MenuItem Text="Training" RunAt="server"> <asp:MenuItem Text="Programming .NET" RunAt="server" Navigateurl="Classes.aspx?id=1" /> <asp:MenuItem Text="Programming ASP.NET" RunAt="server" NavigateUrl="Classes.aspx?id=2" /> <asp:MenuItem Text="Programming Web Services" RunAt="server" NavigateUrl="Classes.aspx?id=3" /> </asp:MenuItem> <asp:MenuItem Text="Consulting" RunAt="server" NavigateUrl="Consulting.aspx" /> <asp:MenuItem Text="Debugging" RunAt="server" NavigateUrl="Debugging.aspx" /> </Items> </asp:Menu>
- 62. Site Navagation - SiteMap <siteMap> <siteMapNode title="Home" description="" url="default.aspx"> <siteMapNode title="Training" url="Training.aspx" description="Training for .NET developers"> <siteMapNode title="Programming .NET" url="Classes.aspx?id=1" description="All about the .NET Framework" /> <siteMapNode title="Programming ASP.NET" url="Classes.aspx?id=2" description="All about ASP.NET" /> <siteMapNode title="Programming Web Services" url="Classes.aspx?id=3" description="All about Web services" /> </siteMapNode> <siteMapNode title="Consulting" url="Consulting.aspx" description="Consulting for .NET projects" /> <siteMapNode title="Debugging" url="Debugging.aspx" description="Help when you need it the most" /> </siteMapNode> </siteMap>
- 63. Site Navigation – TreeView and SiteMap <siteMap> <siteMapNode title="Home" description="" url="default.aspx"> <siteMapNode title="Training" url="Training.aspx" description="Training for .NET developers"> <siteMapNode title="Programming .NET" url="Classes.aspx?id=1" description="All about the .NET Framework" /> <siteMapNode title="Programming ASP.NET" url="Classes.aspx?id=2" description="All about ASP.NET" /> <siteMapNode title="Programming Web Services" url="Classes.aspx?id=3" description="All about Web services" /> </siteMapNode> <siteMapNode title="Consulting" url="Consulting.aspx" description="Consulting for .NET projects" /> <siteMapNode title="Debugging" url="Debugging.aspx" description="Help when you need it the most" /> </siteMapNode> </siteMap> Web.sitemap <asp:SiteMapDataSource ID="SiteMap" RunAt="server" /> <asp:TreeView DataSourceID="SiteMap" RunAt="server" />
- 64. Site Navigation – Menu and SiteMap <asp:SiteMapDataSource ID="SiteMap" RunAt="server" /> <asp:Menu DataSourceID="SiteMap" RunAt="server" /> <siteMap> <siteMapNode title="Home" description="" url="default.aspx"> <siteMapNode title="Training" url="Training.aspx" description="Training for .NET developers"> <siteMapNode title="Programming .NET" url="Classes.aspx?id=1" description="All about the .NET Framework" /> <siteMapNode title="Programming ASP.NET" url="Classes.aspx?id=2" description="All about ASP.NET" /> <siteMapNode title="Programming Web Services" url="Classes.aspx?id=3" description="All about Web services" /> </siteMapNode> <siteMapNode title="Consulting" url="Consulting.aspx" description="Consulting for .NET projects" /> <siteMapNode title="Debugging" url="Debugging.aspx" description="Help when you need it the most" /> </siteMapNode> </siteMap> Web.sitemap
- 65. Site Navigation – SiteMap API Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Hyperlink1.Text = SiteMap.CurrentNode.ParentNode.ToString() Hyperlink1.NavigateUrl = SiteMap.CurrentNode.ParentNode.Url Hyperlink2.Text = SiteMap.CurrentNode.PreviousSibling.ToString() Hyperlink2.NavigateUrl = SiteMap.CurrentNode.PreviousSibling.Url Hyperlink3.Text = SiteMap.CurrentNode.NextSibling.ToString() Hyperlink3.NavigateUrl = SiteMap.CurrentNode.NextSibling.Url End Sub <html xmlns=”http://www.w3.org/1999/xhtml” > <head runat=”server”> <title>SiteMapDataSource</title> </head> <body> <form id=”form1” runat=”server”> Move Up: <asp:Hyperlink ID=”Hyperlink1” Runat=”server”></asp:Hyperlink><br /> <-- <asp:Hyperlink ID=”Hyperlink2” Runat=”server”></asp:Hyperlink> | <asp:Hyperlink ID=”Hyperlink3” Runat=”server”></asp:Hyperlink> --> </form> </body> </html>
- 66. Summary – ASAP.Net New features to simplify repetitive coding tasks New provider model offers extra extensibility New compilation model fixes old base/derived class problem It’s stronger, faster, prettier and with a better engine. Wouldn’t you like to give it a test drive ?