Web forms I'm still alive


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Enabling Dynamic Data Advantages1. Setting default values for data fields. Dynamic Data enables you to provide default values at run time for fields in a data control.2. Interacting with the database without creating and registering a data model. Data-bound controls that support Dynamic Data can interact with the database by using any data source, without scaffolding. This avoids having to configure a LINQ to SQL or Entity Framework data model and use the LinqDataSource and EntityDataSource controls.3. Automatically validating the data that is entered by the user without writing any code.
  • - you to use URLs that do not have to map to specific files in a Web site. Because the URL does not have to map to a file, you can use URLs that are descriptive of the user's action and therefore are more easily understood by users.- In an ASP.NET application that does not use routing, an incoming request for a URL typically maps to a physical file that handles the request, such as an .aspx file. For example, a request for http://server/application/Products.aspx?id=4 maps to a file that is named Products.aspx that contains code and markup for rendering a response to the browser. The Web page uses the query string value of id=4 to determine what type of content to display.- For example, in the request for http://server/application/Products/show/beverages, the routing parser can pass the values Products, show, and beverages to the page handler. In this example, if the route is defined by using the URL pattern server/application/{area}/{action}/{category}, the page handler would receive a dictionary collection in which the value associated with the key area is Products, the value for the key action is show, and the value for the key category is beverages. In a request that is not managed by URL routing, the /Products/show/beverages fragment would be interpreted as the path of a file in the application
  • AddingContraints:routes.MapPageRoute("", "Category/{action}/{categoryName}", "~/categoriespage.aspx", true, new RouteValueDictionary {{"categoryName", "food"}, {"action", "show"}}, -- Default Valuesnew RouteValueDictionary {{"locale", "[a-z]{2}-[a-z]{2} "},{"year", @"\\d{4}"}} ); -- Constraintshttp://server/application/Products/Beverages/Coffee.aspx is not handled by routing if a physical file exists at Products/Beverages/Coffee.aspx. Routing does not handle the request even if it matches a defined pattern, such as {controller}/{action}/{id}.If you want routing to handle all requests, even requests that point to files, you can override the default behaviour by setting the RouteExistingFiles property of the RouteCollection object to true.When you set this value to true, all requests that match a defined pattern are handled by routing.When the CheckPhysicalUrlAccess property is set to true (which is its default value), a user must have permission to access both the route URL and the physical URL. When the CheckPhysicalUrlAccess property is set to false, a user requires only permission to access the route URL, and permissions for the physical URL are not checked.<location path=“collegepage.aspx"> <system.web> <authorization> <allow roles="admin"/> <deny users="*"/> </authorization> </system.web> </location> <location path=“CollegePage"> <system.web> <authorization> <allow users="*"/> </authorization> </system.web> </location> </configuration>
  • Enable View State:, three settings:The EnableViewState property for the page is set to true.The EnableViewState property for the control is set to true.The ViewStateMode property for the control is set to Enabled or inherits the Enabled setting
  • Web forms I'm still alive

    1. 1. Web Forms - I'm still alive<br />AmanGarg<br />MCT, MCITP, MCSD .NET<br />
    2. 2. Dynamic Data<br />Routing<br />Web Form Additions<br />Predictable Client IDs<br />Programmable Meta Data<br />Better control over ViewState<br />Persist selected rows<br />Web Deployment<br />Not Included in this session<br />Any UI Performance Improvements<br />JS & CSS Enhancements<br />Ajax<br />Agenda<br />
    3. 3. Distribution<br />
    4. 4. A RAD experience for quickly building a data-driven Web site<br />Fully Customizable<br />Quickly build data-driven applications based on LINQ to SQL and Entity Framework Data Model<br />Automatic validation that is based on constraints defined in the data model<br />The ability to easily change the markup that is generated for fields in the GridView and DetailsView controls by using field templates that are part of your Dynamic Data project<br />Dynamic Data<br />
    5. 5. Demo – Dynamic DataCreate an Admin Data-Driven Website<br />
    6. 6. Enabling Dynamic Data for Existing Projects<br />Declarative DynamicDataManager Control Syntax<br />Entity Templates<br />New Field Templates for URLs and E-mail Addresses<br />Creating Links with the DynamicHyperLinkControl<br />Support for Many-to-Many Relationships (Entity Framework Only)<br />New Attributes to Control Display and Support Enumerations<br />Dynamic Data – Additions<br />
    7. 7. Use an existing webpage to enable Dynamic Data<br />Entity Templates<br />New Field Templates<br />Many-to Many Relationship<br />DemoIn-Depth Dynamic Data<br />
    8. 8. Enables Descriptive URLs<br />Easy to understand<br />SEO friendly<br />The ASP.NET Dynamic Data extends routing<br />ASP .NET Routing vs URL Rewriting<br />Routing<br />
    9. 9. Imperative WebForms Routing <br />Declarative WebForms Routing <br />Outbound WebForms Routing <br />Various ways to achieve Routing<br />
    10. 10. Default Values for URL Parameters<br />URL Patterns<br />Add Constraints to Routes<br />Explicitly Disable a URL Pattern<br />Use Routes.Ignore method to disable a pattern<br />Routing does not handle requests that map to an existing physical file on the Web server<br />Security Concerns with ASP .NET Routing<br />Routing Features<br />Demo<br />
    11. 11. The ability to set metatags<br />More control over view state<br />Easier ways to work with browser capabilities<br />More control over generated IDs<br />The ability to persist selected rows in data controls<br />More control over rendered HTML in the FormView and ListView controls<br />Permanently redirecting a Page<br />Introduction to IIS Express<br />WebForm Additions<br />
    12. 12. Web Form Additions<br />Demo<br />
    13. 13. Web Packaging<br />Web.config transformation<br />Database deployment<br />One-click publish for web applications<br />ASP .NET 4 Web Deployment<br />
    14. 14. Deployment Scenarios<br />Publish to Test/Staging Environment<br />Package for Prod Environment<br />Deploy Database Scripts along with<br />
    15. 15. MS-Build Based Deployment<br />Package all Web Components<br />Script IIS-Settings<br />Configure App Pool<br />SQL DB<br />Script Schema and/or data<br />Deploy Database Scripts along with the web code<br />IIS7 Import<br />Web Deployment<br />Demo<br />
    16. 16. ?<br />Q & A<br />
    17. 17. amandeepgarg@hotmail.com<br />http://www.geekswithblogs.net/amangarg<br />Twitter: @amangarg_sg<br />Thank You<br />