| Unit 1: Creating a Web Application
|
|
|
| This unit describes the different types of Web sites that you can create with Visual Studio 2005. It introduces the concept of event handling, and shows how to work with default event handlers for an object. It also explains how to control a Web application through the hierarchy of configuration files.
|
|
|
| Lessons
|
|
|
| - Visual Studio Web Site Types
|
| - Default Event Handling in Web Applications
|
| - Web Configuration Files
|
|
|
| Lab 1: Creating a Web Application
|
|
|
| - Exercise 1. Creating a New Web Application
|
| - Exercise 2. Configuring and Building a Web Application
|
|
|
| After completing this unit, students will be able to:
|
|
|
| - Describe the types of Web sites that they can create with Visual Studio 2005.
|
| - Describe the concept of a default event handler for an object.
|
| - Explain how the Machine.Config and Web.Config files control the settings for a Web application.
|
| - Create a new Web application.
|
| - Configure and build a Web application.
|
|
|
|
|
| Unit 2: Programming a Web Application
|
|
|
| This unit introduces the advanced event-handling capabilities of ASP.NET 2.0 and describes how to work with events in Visual Studio 2005. It shows how to work with non-default event handlers and centralized event handlers. It also addresses other common Web programming concepts, including:
|
|
|
| - Detecting the type, version, and capability of the browser being used to view a Web site.
|
| - Accessing information in an ASP.NET Web Page header.
|
| - Using the HttpResponse.Write method to provide feedback to users.
|
| - Handling page-level errors.
|
|
|
| Lessons
|
|
|
| - Event Handling in Web Applications
|
| - Browser Capability Detection
|
| - Page Header Retrieval
|
| - Page-Level and Application-Level Error Handling
|
|
|
|
|
| Lab 2: Programming a Web Application
|
|
|
| - Exercise 1. Implementing Non-Default Event Handlers
|
| - Exercise 2. Detecting Browser Capabilities and Setting Page Header Properties
|
| - Exercise 3. Handling Page-Level Exceptions
|
|
|
| After completing this unit, students will be able to:
|
|
|
| - Describe various event-handling techniques.
|
| - Explain how to detect browser types and capabilities.
|
| - Explain how to access page headers.
|
| - Describe how to handle page-level errors and application-level errors.
|
| - Implement advanced techniques for handling events.
|
| - Implement browser-capability detection.
|
| - Implement page-header manipulation.
|
| - Implement page-level and application-level error handling.
|
|
|
|
|
| Unit 3: Adding and Configuring Server Controls
|
|
|
| This unit explains how to use the HTML controls and Web server controls provided by Visual Studio 2005 and ASP.NET 2.0. It shows how to design and build Web-based user interfaces, and it teaches how to program Web server controls. This unit also describes how the ASP.NET 2.0 postback model works and how it can be used.
|
|
|
| Lessons
|
|
|
| - HTML Controls and Web Server Controls
|
| - Types of Web Server Controls
|
| - Working with Web Server Controls
|
| - The ASP.NET 2.0 Page Postback Model
|
|
|
| Lab 3: Adding and Configuring Server Controls
|
|
|
| - Exercise 1. Building Graphical User Interfaces with HTML Controls
|
| - Exercise 2. Building Graphical User Interfaces with Web Server Controls
|
| - Exercise 3. Programming Web Server Controls and Working with Postbacks
|
|
|
| After completing this unit, students will be able to:
|
|
|
| - Explain the differences between HTML controls and Web server controls.
|
| - Describe the different types of Web server controls.
|
| - Explain how to use HTML controls and Web server controls.
|
| - Explain how the postback model of ASP.NET 2.0 works.
|
| - Create Web-based user interfaces with HTML controls and Web server controls.
|
| - Write code that interacts with Web server controls.
|
| - Write code that interacts with the postback model of ASP.NET 2.0.
|
|
|
|
|
| Unit 4: Creating a Common Layout by Using Master Pages
|
|
|
| This unit explains how to use master pages to define common layouts for Web pages. Master pages provide developers with a new set of features for ensuring consistent page layout. Students will work with master pages and nested master pages in the lab to build a Web application that has a consistent layout and functionality across Web pages.
|
|
|
| Lessons
|
|
|
| - What Are Master Pages?
|
| - What Are Content Pages?
|
| - Nested Master Pages
|
|
|
| Lab 4: Creating a Common Layout by Using Master Pages
|
|
|
| - Exercise 1. Designing a Master Page
|
| - Exercise 2. Adding and Configuring Content Pages
|
| - Exercise 3. Designing Nested Master Pages
|
|
|
| After completing this unit, students will be able to:
|
|
|
| - Describe the concept of a master page.
|
| - Describe the concept of a content page.
|
| - Describe nested master pages.
|
| - Design master pages.
|
| - Configure content pages.
|
| - Design nested master pages.
|
|
|
|
|
| Unit 5: Managing State for a Web Application
|
|
|
| This unit describes the different state management technologies that students can use in ASP.NET 2.0 Web applications. It discusses how controls can retain state data over multiple requests, and then explains how developers can work with this state data. This unit then shows how to store state data in the Application and Session objects provided by ASP.NET 2.0. It also discusses the different session-data storage mechanisms. Finally, this unit explains how to use the Cache object to cache and retrieve state data.
|
|
|
| Lessons
|
|
|
| - ViewState Properties and ControlState Data
|
| - Application and Session Objects
|
| - Strategies for Managing Session State Data
|
| - The Cache Object
|
|
|
| Lab 5: Managing State for a Web Application
|
|
|
| - Exercise 1. Configuring ViewState Properties for Web Server Controls
|
| - Exercise 2. Storing and Retrieving Application and Session State
|
| - Exercise 3. Implementing Out-of-Process Session State
|
| - Exercise 4. Storing and Managing State Data in the Cache Object
|
|
|
|
|
| After completing this unit, students will be able to:
|
|
|
| - Describe the ViewState and ControlState data models for Web pages.
|
| - Describe the Application and Session objects and explain how state data is stored and retrieved in these objects.
|
| - Describe various session-state data-storage strategies.
|
| - Describe the Cache object and explain how you can use it to store and manage state data.
|
| - Configure ViewState properties and ControlState properties for Web server controls.
|
| - Store and retrieve Application and Session state.
|
| - Implement out-of-process session state.
|
| - Store and manage state data in the Cache object.
|
|
|
|
|
| Unit 6: Accessing and Displaying Data
|
|
|
| This unit describes how to add database connections to the Web.Config file and the benefits that this approach adds when building manageable Web applications. This unit then describes the new data controls for accessing data in a variety of formats. It includes details about using the SqlDataSource control, the XmlDataSource control, and the ObjectDataSource control. This unit also describes how user interface data controls are bound to the data source controls, and it includes a discussion about binding data-aware standard controls to data.
|
|
|
| Lessons
|
|
|
| - Database Connections and the Web.Config File
|
| - Relational Data and Data Source Controls
|
| - XML Data and Data Source Controls
|
| - Object Data and Data S
|
| Course Search About this courseSummary / Objectives Pre-requisites Post-requisites Skills Certification Exams Extra Information Up coming eventsStart Location
|
| 09 Jan 2008 QA-IQ Glasgow City Rd Centre
|
| 14 Jan 2008 QA-IQ London Tabernacle St Centre
|
| 28 Jan 2008 QA-IQ Leeds Centre
|
| 11 Feb 2008 QA-IQ Manchester Stockport Centre
|
| 10 Mar 2008 QA-IQ London Tabernacle St Centre
|
| 10 Mar 2008 QA-IQ Newcastle Centre
|
| 14 Apr 2008 QA-IQ London Tabernacle St Centre
|
| 19 May 2008 QA-IQ London Tabernacle St Centre
|
| 16 Jun 2008 QA-IQ London Tabernacle St Centre
|
|
|
|
|
| Tools
|
| Email to a friend
|
| Add to favourites
|
| Print this page Home :: Terms & Conditions :: Website Policies :: Site Map :: Print Friendly
|
| Copyright © 2007 QA-IQ Ltd. All rights |
Top