Skills measured by Exam 70-562
F7. Configuring and Deploying Web Applications (10 percent) (Exam 70-562)
F7.1. Configure providers. -- May include but is not limited to:
F7.1a. personalization, --
F7.1b. membership, -- you can manage authentication using your own user database using ASP.NET forms authentication and ASP.NET membership.
F7.1c. data sources, --
F7.1d. site map, -- The simplest way to create a site map is to create an XML file named Web.sitemap that organizes the pages in the site hierarchically. This site map is automatically picked up by the default site-map provider for ASP.NET.
F7.1e. resource, --
F7.1f. security --
F7.2. Configure authentication, authorization, and impersonation. - May include but is not limited to:
F7.2a. Forms Authentication, -- Forms authentication enables you to authenticate the user name and password of your users using a login form that you create. Unauthenticated requests are redirected to a login page, where the user provides credentials and submits the form. If the application authenticates the request, the system issues a ticket that contains a key for reestablishing the identity for subsequent requests.
F7.2b. Windows Authentication -- Windows Authentication treats the user identity supplied by Microsoft Internet Information Services (IIS) as the authenticated user in an ASP.NET application. IIS provides a number of authentication mechanisms to verify user identity, including anonymous authentication, Windows integrated (NTLM) authentication, Windows integrated (Kerberos) authentication, Basic (base64 encoded) authentication, Digest authentication, and authentication based on client certificates.
F7.3. Configure projects, solutions, and reference assemblies. - May include but is not limited to:
F7.3a. local assemblies,
F7.3b. shared assemblies (GAC),
F7.3c. Web application projects,
F7.3d. solutions
F7.4. Configure session state by using Microsoft SQL Server, State Server, or InProc. - May include but is not limited to:
F7.4a. setting the timeout;
F7.4b. cookieless sessions
F7.5. Publish Web applications. - May include but is not limited to:
F7.5a. FTP, File System, or HTTP from Visual Studio
F7.6. Configure application pools.
F7.7. Compile an application by using Visual Studio or command-line tools. - May include but is not limited to:
F7.7a. aspnet_compiler.exe, -- ASP.NET pre-compilation tool
F7.7b. Just-In-Time (JIT) compiling,
F7.7c. aspnet_merge.exe -- The ASP.NET merge tool (Aspnet_merge.exe) lets you combine and manage assemblies that are created by the ASP.NET pre-compilation tool (Aspnet_compiler.exe).
F8. Consuming and Creating Server Controls (20 percent) (Exam 70-562)
F8.1. Implement data-bound controls. -- May include but is not limited to:
F8.1a. DataGrid, -- A data bound list control that displays the items from data source in a table. The DataGrid control allows you to select, sort, and edit these items.
F8.1b. DataList, -- A data bound list control that displays items using templates. With property RepeatLayout, you can choose whether to show the list in table structure or in a steady stream.
F8.1c. Repeater, -- A data-bound list control that allows custom layout by repeating a specified template for each item displayed in the list.
F8.1d. ListView, -- Displays the values of a data source by using user-defined templates. The ListView control enables users to select, sort, delete, edit, and insert records.
F8.1e. GridView, -- Displays the values of a data source in a table where each column represents a field and each row represents a record. The GridView control enables you to select, sort, and edit these items.
F8.1f. FormView, -- Displays the values of a single record from a data source using user-defined templates. The FormView control allows you to edit, delete, and insert records.
F8.1g. DetailsView, -- Displays the values of a single record from a data source in a table, where each data row represents a field of the record. The DetailsView control allows you to edit, delete, and insert records.
F8.1h. TreeView, -- Displays hierarchical data, such as a table of contents, in a tree structure.
F8.1i. DataPager -- Provides paging functionality for data-bound controls that implement the IPageableItemContainer interface, such as the ListView control.
F8.2. Load user controls dynamically.
F8.3. Create and consume custom controls. -- May include but is not limited to:
F8.3a. registering controls on a page,
F8.3b. creating templated controls
F8.4. Implement client-side validation and server-side validation. -- May include but is not limited to:
F8.4a. RequiredFieldValidator, -- Makes the associated input control a required field.
F8.4b. CompareValidator, -- Compares the value entered by the user in an input control with the value entered in another input control, or with a constant value.
F8.4c. RegularExpressionValidator, -- Validates whether the value of an associated input control matches the pattern specified by a regular expression.
F8.4d. CustomValidator, -- Performs user-defined validation on an input control.
F8.4e. RangeValidator -- Checks whether the value of an input control is within a specified range of values.
F8.5. Consume standard controls. -- May include but is not limited to:
F8.5a. Button, -- Represents a Windows button control, which reacts to the ButtonBase..::.Click event.
F8.5b. TextBox, -- Represents a control that can be used to display or edit unformatted text.
F8.5c. DropDownList, -- Represents a control that allows the user to select a single item from a drop-down list.
F8.5d. RadioButton, -- Represents a radio button control.
F8.5d. CheckBox, -- Displays a check box that allows the user to select a true or false condition.
F8.5e. HyperLink, -- A control that displays a link to another Web page.
F8.5f. Wizard, -- Provides navigation and a user interface (UI) to collect related data across multiple steps.
F8.5g. MultiView -- Represents a control that acts as a container for a group of View controls.
F9. Working with Data and Services (17 percent) (Exam 70-562)
F9.1. Read and write XML data. -- May include but is not limited to:
F9.1a. XmlDocument, -- Represents an XML document.
F9.1b. XPathNavigator, -- Provides a cursor model for navigating and editing XML data.
F9.1c. XPathNodeIterator, -- Provides an iterator over a selected set of nodes.
F9.1d. XPathDocument, -- Provides a fast, read-only, in-memory representation of an XML document using the XPath data model.
F9.1e. XmlReader, -- Represents a reader that provides fast, non-cached, forward-only access to XML data.
F9.1f. XmlWriter, -- Represents a writer that provides a fast, non-cached, forward-only means of generating streams or files containing XML data.
F9.1g. XmlDataDocument, -- Allows structured data to be stored, retrieved, and manipulated through a relational DataSet.
F9.1h. XmlNamespaceManager -- Resolves, adds, and removes namespaces to a collection and provides scope management for these namespaces.
F9.2. Manipulate data by using DataSet and DataReader objects.
F9.3. Call a Windows Communication Foundation (WCF) service or a Web service from an ASP.NET Web page. -- May include but is not limited to:
F9.3a. App_WebReferences; -- Contains reference contract files (.wsdl files), schemas (.xsd files), and discovery document files (.disco and .discomap files) defining a Web reference for use in an application. For more information about generating code for XML Web services, see Web Services Description Language Tool (Wsdl.exe).
F9.3b. <system.serviceModel> configuration
F9.4. Implement a DataSource control. – May include but is not limited to:
F9.4a. LinqDataSource, -- Enables the use of Language-Integrated Query (LINQ) in an ASP.NET Web page through markup text to retrieve and modify data from a data object.
F9.4b. ObjectDataSource, -- Represents a business object that provides data to data-bound controls in multitier Web application architectures.
F9.4c. XmlDataSource, -- Represents an XML data source to data-bound controls.
F9.4d. SqlDataSource -- Represents an SQL database to data-bound controls.
F9.5. Bind controls to data by using data binding syntax.
F10. Troubleshooting and Debugging Web Applications (16 percent) (Exam 70-562)
F10.1. Configure debugging and custom errors. – May include but is not limited to:
F10.1a. <customErrors mode="Off|On|RemoteOnly" />,
F10.1b. <compilation debug="true"/>
F10.2. Set up an environment to perform remote debugging.
F10.3 Debug unhandled exceptions when using ASP.NET AJAX. – May include but is not limited to:
F10.3a. client-side Sys.Debug methods; -- provides methods for displaying objects in readable form at the end of a Web page.
F10.3b. attaching a debugger to Windows Internet Explorer
F10.4. Implement tracing of a Web application. – May include but is not limited to:
F10.4a. Trace.axd,
F10.4b. Trace=True on @Page directive,
F10.4c. <trace enabled="true"/>
F10.5. Debug deployment issues. – May include but is not limited to:
F10.5a. aspnet_regiis.exe;
F10.5b. creating an IIS Web application;
F10.5c. setting the .NET Framework version
F10.6. Monitor Web applications. – May include but is not limited to:
F10.6a. health monitoring by using WebEvent,
F10.6b. performance counters
F11. Working with ASP.NET AJAX and Client-Side Scripting (15 percent) (Exam 70-562)
F11.1. Implement Web Forms by using ASP.NET AJAX. – May include but is not limited to:
F11.1a. EnablePartialRendering,
F11.1b. Triggers,
F11.1c. ChildrenAsTriggers,
F11.1d. Scripts,
F11.1e. Services,
F11.1f. UpdateProgress,
F11.1g. Timer,
F11.1h. ScriptManagerProxy
F11.2. Interact with the ASP.NET AJAX client-side library. – May include but is not limited to:
F11.2a. JavaScript Object Notation (JSON) objects;
F11.2b. handling ASP.NET AJAX events
F11.3. Consume services from client scripts.
F11.4. Create and register client script. – May include but is not limited to:
F11.4a. inline,
F11.4b. included .js file,
F11.4c. embedded JavaScript resource,
Video: #6 | JavaScript Intellisense Support in Visual Studio 200811 minutes, 23 seconds
F11.4d. created from server code
F12. Targeting Mobile Devices (5 percent) (Exam 70-562)
F12.1. Access device capabilities. – May include but is not limited to:
F12.1a. working with emulators
F12.2. Control device-specific rendering. – May include but is not limited to:
F12.2a. DeviceSpecific control;
F12.2b. device filters;
F12.2c. control templates
F12.3. Add mobile Web controls to a Web page. – May include but is not limited to:
F12.3a. StyleSheet controls;
F12.3b. List controls;
F12.3c. Container controls
F12.4. Implement control adapters. – May include but is not limited to:
F12.4a. App_Browsers; -- Contains browser definitions (.browser files) that ASP.NET uses to identify individual browsers and determine their capabilities. For more information, see Browser Definition File Schema (browsers Element) and How to: Detect Browser Types in ASP.NET Web Pages.
F12.4b. rendering by using ChtmlTextWriter or XhtmlTextWriter --
F12.4b1. ChtmlTextWriter -- Writes a series of cHTML-specific characters and text to the output stream of an ASP.NET server control. The ChtmlTextWriter class provides formatting capabilities that ASP.NET server controls use when rendering cHTML content to clients.
F12.4b2. XhtmlTextWriter -- Writes Extensible Hypertext Markup Language (XHTML)-specific characters, including all variations of XHTML modules that derive from XTHML, to the output stream for an ASP.NET server control for mobile devices.
F13. Programming Web Applications (17 percent) (Exam 70-562)
F13.1. Customize the layout and appearance of a Web page. – May include but is not limited to:
F13.1a. CSS,
F13.1b. Themes and Skins, -- ASP.NET themes are a collection of properties that define the appearance of pages and controls in your Web site. A theme can include skin files, which define property settings for ASP.NET Web server controls, and can also include cascading style sheet files (.css files) and graphics. By applying a theme, you can give the pages in your Web site a consistent appearance.
F13.1c. Master Pages, -- ASP.NET master pages enable you to create a page layout (a master page) that you can use with selected or all pages (content pages) in your Web site. Master pages can greatly simplify the task of creating a consistent look for your site.
F13.1d. and Web Parts, -- ASP.NET Web Parts is an integrated set of controls for creating Web sites that enable end users to modify the content, appearance, and behavior of Web pages directly from a browser.
F13.1e. App_Themes, -- A page theme is a theme folder with control skins, style sheets, graphics files and other resources created as a subfolder of the \App_Themes folder in your Web site.
F13.1f. StyleSheetTheme -- sets the cascading style sheet (CSS) that defines the appearance of the page in the Web browser.
F13.2. Work with ASP.NET intrinsic objects. – May include but is not limited to:
F13.2a. Request, -- Gets the HttpRequest object for the requested page.
F13.2b. Server, -- You can use the Server object to access methods and properties on the server. Most of these methods and properties serve as utility functions.
F13.2c. Application, -- Gets the HttpApplicationState object for the current Web request.
F13.2d. Session, -- The Session object controls the installation process. It opens the Installer database, which contains the installation tables and data.
F13.2e. Response, -- Gets the HttpResponse object associated with the Page object. This object allows you to send HTTP response data to a client and contains information about that response. You can use the Response object to send output to the client.
F13.2f. HttpContext -- Encapsulates all HTTP-specific information about an individual HTTP request.
F13.3. Implement globalization and accessibility. – May include but is not limited to:
F13.3a. resource files, -- A resource file is an XML file that contains the strings that you want to translate into different languages or paths to images. The resource file contains key/value pairs. Each pair is an individual resource. Key names are not case sensitive. For example, a resource file might contain a resource with the key Button1 and the value Submit.
F13.3b. culture settings, -- In an ASP.NET Web page, you can set to two culture values, the Culture and UICulture properties. The Culture value determines the results of culture-dependent functions, such as the date, number, and currency formatting, and so on. The UICulture value determines which resources are loaded for the page.
F13.3c. RegionInfo, -- Contains information about the country/region.
F13.3d. App_GlobalResources, -- Folder containing resources (.resx and .resources files) that are compiled into assemblies with global scope. Resources in the App_GlobalResources folder are strongly typed and can be accessed programmatically. For more information, see ASP.NET Web Page Resources Overview.
F13.3e. App_LocalResources, -- Folder containing resources (.resx and .resources files) that are associated with a specific page, user control, or master page in an application For more information, see ASP.NET Web Page Resources Overview.
F13.3f. TabIndex, -- Use the TabIndex property to specify or determine the tab index of a Web server control on the Web Forms page. When you press the Tab key, the order in which the Web server controls receive focus is determined by the TabIndex property of each control.
F13.3g. AlternateText , -- Sets or returns the alternate text to display when an image is not available for the device. The default value is an empty string ("").
F13.3h. GenerateEmptyAlternateText, -- Gets or sets a value indicating whether the control generates an alternate text attribute for an empty string value.
F13.3i. AccessKey, -- Use the AccessKey property to specify the keyboard shortcut for the Web server control. This allows you to navigate quickly to the control by pressing the ALT key and the key for the specified character on the keyboard.
F13.3j. Label.AssociatedControlID -- Gets or sets the identifier for a server control that the Label control is associated with.
F13.4. Implement business objects and utility classes. – May include but is not limited to:
F13.4a. App_Code , -- Contains source code for utility classes and business objects (for example, .cs, .vb, and .jsl files) that you want to compile as part of your application. In a dynamically compiled application, ASP.NET compiles the code in the App_Code folder on the initial request to your application. Items in this folder are then recompiled when any changes are detected.
F13.4b. external assemblies
F13.5. Implement session state, view state, control state, cookies, cache, or application state.
F13.5a. session state, -- Use ASP.NET session state to store and retrieve values for a user.
F13.5b. view state, -- View state is the method that the ASP.NET page framework uses to preserve page and control values between round trips. When the HTML markup for the page is rendered, the current state of the page and values that must be retained during postback are serialized into base64-encoded strings. This information is then put into the view-state hidden field or fields.
F13.5c. control state, --
F13.5d. cookies, -- A cookie is a small bit of text that accompanies requests and pages as they go between the Web server and browser. The cookie contains information the Web application can read whenever the user visits the site.
F13.5e. cache, --
F13.5f. application state. -- Application state is a data repository available to all classes in an ASP.NET application. Application state is stored in memory on the server and is faster than storing and retrieving information in a database. Unlike session state, which is specific to a single user session, application state applies to all users and sessions.
F13.6. Handle events and control page flow. – May include but is not limited to:
F13.6a. page events,
F13.6b. control events,
F13.6c. application events,
F13.6d. and session events, -- ASP.NET provides two events that help you manage user sessions: the Session_OnStart event, which is raised when a new session
begins, and the Session_OnEnd event, which is raised when a session is abandoned or expires. Session events are specified in the Global.asax file for an ASP.NET application.
F13.6e. cross-page posting; -- Cross-page posting enables you to configure a button on an ASP.NET Web page to post the current page to a different page.
F13.6f. Response.Redirect, -- The Redirect method causes the browser to redirect the client to a different URL. The Redirect method of the Response object operates by sending a header to the client. This header causes the client to look to another URL location specified in the header. Because a header must come at the beginning of a document, it is not possible to place the Redirect method in a document with HTML code preceding it.
F13.6g. Server.Transfer, -- The Transfer method sends all of the information that has been assembled for processing by one .asp file to a second .asp file. Server.Transfer acts as an efficient replacement for the Response.Redirect method.
F13.6h. IsPostBack, -- Gets a value indicating whether the page is being loaded in response to a client postback, or if it is being loaded and accessed for the first time.
F13.6i. setting AutoEventWireup -- Boolean attribute that indicates whether events of a Web Forms page are autowired: TRUE (default) if events for ASP.NET pages are automatically connected to event-handling functions; FALSE when event-autowiring is not activated.
F13.7. Implement the Generic Handler.