ASP.NET Developer Certification Training

3 Certifications: MCPD/MCTS: ASP .NET Developer v3.5 Boot Camp

Course Length: 8 days

Certifications:

·         MCTS: NET Framework 3.5, ASP .NET Applications

·         MCTS: .NET Framework 3.5, Core Foundations

·         MCPD: NET Framework 3.5, ASP .NET Developer 3.5

 

Number of Exams: 3

The Microsoft Certified Technology Specialist (MCTS) certifications enable professionals to target specific technologies and to distinguish themselves by demonstrating in-depth knowledge and expertise in their specialized technologies. An MCTS is consistently capable of implementing, building, troubleshooting, and debugging a particular Microsoft technology.

The Microsoft Certified Professional Developer: ASP .NET Developer credential is one of the most effective ways to demonstrate your expertise in using Microsoft Visual Studio 2008 and the Microsoft .NET Framework 3.5 in a specific, real-world job role.

An MCPD credential validates a comprehensive set of skills required to be successful on the job, and gives hiring managers and potential customers a reliable indicator of your job performance. This credential offers a simple, targeted framework that makes the certification paths easier to understand and allows you to stand out from the crowd.

·         Exam 70-536

·         Exam 70-562

·         Exam 70-564

 

 

Exam 70-536

Microsoft .NET Framework - Application Development Foundation

Developing applications that use system types and collections

• Manage data in a .NET Framework application by using the .NET Framework 2.0 system types. (Refer System namespace)
• Manage a group of associated data in a .NET Framework application by using collections. (Refer System.Collections namespace)
• Improve type safety and application performance in a .NET Framework application by using generic collections. (Refer System.Collections.Generic namespace)
• Manage data in a .NET Framework application by using specialized collections. (Refer System.Collections.Specialized namespace)
• Implement .NET Framework interfaces to cause components to comply with standard contracts. (Refer System namespace)
• Control interactions between .NET Framework application components by using events and delegates. (Refer System namespace)

Implementing service processes, threading, and application domains in a .NET Framework application

• Implement, install, and control a service. (Refer System.ServiceProcess namespace)
• Develop multithreaded .NET Framework applications. (Refer System.Threading namespace)
• Create a unit of isolation for common language runtime in a .NET Framework application by using application domains. (Refer System namespace)

Embedding configuration, diagnostic, management, and installation features into a .NET Framework application

• Embed configuration management functionality into a .NET Framework application. (Refer System.Configuration namespace)
• Create a custom Microsoft Windows Installer for the .NET Framework components by using the System.Configuration.Install namespace, and configure the .NET Framework applications by using configuration files, environment variables, and the .NET Framework Configuration tool (Mscorcfg.msc).
• Manage an event log by using the System.Diagnostics namespace.
• Manage system processes and monitor the performance of a .NET Framework application by using the diagnostics functionality of the .NET Framework 2.0. (Refer System.Diagnostics namespace)
• Debug and trace a .NET Framework application by using the System.Diagnostics namespace.
• Embed management information and events into a .NET Framework application. (Refer System.Management namespace)

Implementing serialization and input/output functionality in a .NET Framework application

• Serialize or deserialize an object or an object graph by using runtime serialization techniques. (Refer System.Runtime.Serialization namespace)
• Control the serialization of an object into XML format by using the System.Xml.Serialization namespace.
• Implement custom serialization formatting by using the Serialization Formatter classes.
• Access files and folders by using the File System classes. (Refer System.IO namespace)
• Manage byte streams by using Stream classes. (Refer System.IO namespace)
• Manage the .NET Framework application data by using Reader and Writer classes. (Refer System.IO namespace)
• Compress or decompress stream information in a .NET Framework application (refer System.IO.Compression namespace), and improve the security of application data by using isolated storage. (Refer System.IO.IsolatedStorage namespace)

Improving the security of the .NET Framework applications by using the .NET Framework 2.0 security features

• Implement code access security to improve the security of a .NET Framework application. (Refer System.Security namespace)
• Implement access control by using the System.Security.AccessControl classes.
• Implement a custom authentication scheme by using the System.Security.Authentication classes. (Refer System.Security.Authentication namespace)
• Encrypt, decrypt, and hash data by using the System.Security.Cryptography classes. (Refer System.Security.Cryptography namespace)
• Control permissions for resources by using the System.Security.Permission classes. (Refer System.Security.Permission namespace)
• Control code privileges by using System.Security.Policy classes. (Refer System.Security.Policy namespace)
• Access and modify identity information by using the System.Security.Principal classes. (Refer System.Security.Principal namespace)

Implementing interoperability, reflection, and mailing functionality in a .NET Framework application

• Expose COM components to the .NET Framework and the .NET Framework components to COM. (Refer System.Runtime.InteropServices namespace)
• Call unmanaged DLL functions in a .NET Framework application, and control the marshaling of data in a .NET Framework application. (Refer System.Runtime.InteropServices namespace)
• Implement reflection functionality in a .NET Framework application (refer System.Reflection namespace), and create metadata, Microsoft intermediate language (MSIL), and a PE file by using the System.Reflection.Emit namespace.
• Send electronic mail to a Simple Mail Transfer Protocol (SMTP) server for delivery from a .NET Framework application. (Refer System.Net.Mail namespace)

Implementing globalization, drawing, and text manipulation functionality in a .NET Framework application

• Format data based on culture information. (Refer System.Globalization namespace)
• Enhance the user interface of a .NET Framework application by using the System.Drawing namespace.
• Enhance the text handling capabilities of a .NET Framework application (refer System.Text namespace), and search, modify, and control text in a .NET Framework application by using regular expressions. (Refer System.RegularExpressions namespace)

[ Back to top ]

Exam 70-562

Microsoft .NET Framework 3.5, ASP.NET Application Development

Configuring and Deploying Web Applications

• Configure providers.

May include but is not limited to: personalization, membership, data sources, site map, resource, security

• Configure authentication, authorization, and impersonation.

May include but is not limited to: Forms Authentication, Windows Authentication

• Configure projects, solutions, and reference assemblies.

May include but is not limited to: local assemblies, shared assemblies (GAC), Web application projects, solutions

• Configure session state by using Microsoft SQL Server, State Server, or InProc.

May include but is not limited to: setting the timeout; cookieless sessions

• Publish Web applications.

May include but is not limited to: FTP, File System, or HTTP from Visual Studio

• Configure application pools.
• Compile an application by using Visual Studio or command-line tools.

May include but is not limited to: aspnet_compiler.exe, Just-In-Time (JIT) compiling, aspnet_merge.exe

Consuming and Creating Server Controls

• Implement data-bound controls.

May include but is not limited to: DataGrid, DataList, Repeater, ListView, GridView, FormView, DetailsView, TreeView, DataPager

• Load user controls dynamically.
• Create and consume custom controls.

May include but is not limited to: registering controls on a page, creating templated controls

• Implement client-side validation and server-side validation.

May include but is not limited to: RequiredFieldValidator, CompareValidator, RegularExpressionValidator, CustomValidator, RangeValidator

• Consume standard controls.

May include but is not limited to: Button, TextBox, DropDownList, RadioButton, CheckBox, HyperLink, Wizard, MultiView

Working with Data and Services

• Read and write XML data.

May include but is not limited to: XmlDocument, XPathNavigator, XPathNodeIterator, XPathDocument, XmlReader, XmlWriter, XmlDataDocument, XmlNamespaceManager

• Manipulate data by using DataSet and DataReader objects.
• Call a Windows Communication Foundation (WCF) service or a Web service from an ASP.NET Web page.
• Implement a DataSource control.

May include but is not limited to: LinqDataSource, ObjectDataSource, XmlDataSource, SqlDataSource

• Bind controls to data by using data binding syntax.

Troubleshooting and Debugging Web Applications

• Configure debugging and custom errors.
• Set up an environment to perform remote debugging.
• Debug unhandled exceptions when using ASP.NET AJAX.

May include but is not limited to: client-side Sys.Debug methods; attaching a debugger to Windows Internet Explorer

• Implement tracing of a Web application.
• Debug deployment issues.

May include but is not limited to: aspnet_regiis.exe; creating an IIS Web application; setting the .NET Framework version

• Monitor Web applications.

May include but is not limited to: health monitoring by using WebEvent, performance counters

Working with ASP.NET AJAX and Client-Side Scripting

• Implement Web Forms by using ASP.NET AJAX.

May include but is not limited to: EnablePartialRendering, Triggers, ChildrenAsTriggers, Scripts, Services, UpdateProgress, Timer, ScriptManagerProxy

• Interact with the ASP.NET AJAX client-side library.

May include but is not limited to: JavaScript Object Notation (JSON) objects; handling ASP.NET AJAX events

• Consume services from client scripts.
• Create and register client script.

May include but is not limited to: inline, included .js file, embedded JavaScript resource, created from server code

Targeting Mobile Devices

• Access device capabilities.

May include but is not limited to: working with emulators

• Control device-specific rendering.

May include but is not limited to: DeviceSpecific control; device filters; control templates

• Add mobile Web controls to a Web page.

May include but is not limited to: StyleSheet controls; List controls; Container controls

• Implement control adapters.

May include but is not limited to: App_Browsers; rendering by using ChtmlTextWriter or XhtmlTextWriter

Programming Web Applications

• Customize the layout and appearance of a Web page.

May include but is not limited to: CSS, Themes and Skins, Master Pages, and Web Parts, App_Themes, StyleSheetTheme

• Work with ASP.NET intrinsic objects.

May include but is not limited to: Request, Server, Application, Session, Response, HttpContext

• Implement globalization and accessibility.

May include but is not limited to: resource files, culture settings, RegionInfo, App_GlobalResources, App_LocalResources, TabIndex, AlternateText , GenerateEmptyAlternateText, AccessKey, Label.AssociatedControlID

• Implement business objects and utility classes.

May include but is not limited to: App_Code , external assemblies

• Implement session state, view state, control state, cookies, cache, or application state.
• Handle events and control page flow.

May include but is not limited to: page events, control events, application events, and session events, cross-page posting; Response.Redirect, Server.Transfer, IsPostBack, setting AutoEventWireup

• Implement the Generic Handler.

[ Back to top ]

Exam 70-564

Designing and Developing ASP.NET Applications Using the Microsoft .NET Framework 3.5

Designing and Implementing Controls

• Choose appropriate controls based on business requirements.

May include but is not limited to: user controls, server controls, built-in controls, custom controls, third-party controls, Web parts

• Design controls for reusability.

May include but is not limited to: user controls, server controls, inheritance for changing behavior

• Manage states for controls.

May include but is not limited to: control state, view state, accessing form elements

• Leverage data-bound controls.

May include but is not limited to: use gridviews, use sorting and paging callbacks when available, when to use custom sorting and paging, server-side pagination

• Choose appropriate validation controls based on business requirements.

May include but is not limited to: server-side page validation (Page.IsValid), custom validator, validation groups, validation summary

• Identify the appropriate usage of ASP.NET AJAX.

May include but is not limited to: implementing partial page updates with update panel, using ASP.NET AJAX controls, script services

• Manage JavaScript dependencies with server controls.

Designing the Presentation and Layout of an Application

• Design complex layout with Master Pages.

May include but is not limited to: strongly typed master pages, nested master pages

• Plan for various user agents.

May include but is not limited to: markups for different browsers for mobile devices, screen readers, accessibility

• Design a brandable user interface by using themes.

May include but is not limited to: shared themes across multiple applications, run time master page selection

• Design site navigation.

May include but is not limited to: when to extend site map provider, treeview menu vs. site map path, programmatically manipulating site map nodes, overriding menu rendering by using control adapters, filtering site map nodes based on user roles

• Plan Web sites to support globalization.

May include but is not limited to: custom resource provider vs. resource files, localize applications

Accessing Data and Services

• Plan vendor-independent database interactions.

May include but is not limited to: IDBconnection, IDBcommand, IDBadapter, IdataReader, Datareader vs. dataset

• Identify the appropriate usage of data source controls.

May include but is not limited to: SQLDataSource, ObjectDataSource, XMLDataSource

• Leverage LINQ in data access design.

May include but is not limited to: LINQtoSQL, lambda expressions, LINQtoObjects, LINQtoXML

• Identify opportunities to access and expose Web services.

May include but is not limited to: WCF, ASMX, REST

Establishing ASP.NET Solution Structure

• Determine when to use the Web Site model vs. a Web Application Project.

May include but is not limited to: project file, references, namespace, user profile object, precompilation

• Establish an error-handling strategy.

May include but is not limited to: Global.asax events, Web.config elements, TRY/CATCH blocks, error logging

• Manipulate configuration files to change ASP.NET behavior.

May include but is not limited to: machine key, tracing, encrypting Web configuration data, custom configuration sections

• Identify a deployment strategy.

May include but is not limited to: mangement application pools, Web deployment projects, pre-compilation, custom action classes

Leveraging and Extending ASP.NET Architecture

• Design a state management strategy.

May include but is not limited to: Cache, ViewState, Application object, Session object, cookies, cookieless session

• Identify the events of the page life cycle.

May include but is not limited to: appending controls, PostBack model, accessing state, data binding

• Write HttpModules and HttpHandlers.

May include but is not limited to: URL rewriting, SSO application, dynamically retrieve data

• Debug ASP.NET Web applications.

May include but is not limited to: debug JavaScript, tracing, debug tools in IDE, examining HTTP headers

• Plan for long-running processes by using asynchronous pages.

May include but is not limited to: AddonPreRenderCompleteAsync, RegisterAsyncTask

Applying security principles

• Identify appropriate security providers.

May include but is not limited to: membership, role, profile, extending custom providers

• Decide which user-related information to store in a profile.

May include but is not limited to: create user profile properties, extend membership objects, custom types

• Establish security settings in Web.config.

May include but is not limited to: identity/impersonation, authentication, authorization (location nodes in Web.config)

• Identify vulnerable elements in applications.

May include but is not limited to: SQL injection, cross-site scripting, protecting against bots

• Ensure that sensitive information in applications is protected.

May include but is not limited to: hash and salt passwords, encrypting information