8 Certification - MCPD/MCTS: .NET v3.5 Boot Camp

Course Length: 15 days

Certifications:

MCTS: .NET Framework v3.5, ADO.NET Applications
MCTS: .NET Framework v3.5, ASP .NET Applications
MCTS: .NET Framework v3.5, Core Foundation
MCTS: .NET Framework v3.5, Windows Communication Foundation Applications
MCTS: .NET Framework v3.5, Windows Forms Applications
MCPD: ASP .NET Developer v3.5
MCPD: Enterprise Application Developer v3.5
MCPD: Windows Developer v3.5

Number of Exams: 8

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: Enterprise Application 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-505

 

• Exam 70-536
• Exam 70-563
• Exam 70-562
• Exam 70-564
• Exam 70-561
• Exam 70-503
• Exam 70-565

 

Exam 70-505

Microsoft .NET Framework 3.5, Windows Forms Application Development

Creating a UI for a Windows Forms Application by Using Standard Controls

• Add and configure a Windows Form.
• Manage control layout on a Windows
• Add and configure a Windows Forms control.
• Create and configure menus.
• Create event handlers for Windows Forms and controls.

Integrating Data in a Windows Forms Application

• Implement data-bound controls.

This objective may include but is not limited to: Use the DataGridView control to display and update the tabular data contained in a data source, use a simple data-bound control to display a single data element on a Windows Form, implement complex data binding to integrate data from multiple sources, navigate forward and backward through records in a DataSet in Windows Forms, define a data source by using a DataConnector component, create data forms by using the Data Form Wizard

• Manage connections and transactions.

This objective may include but is not limited to: Configure a connection to a database by using the Connection Wizard, configure a connection to a database by using Server Explorer, configure a connection to a database by using the Connection class, connect to a database by using specific database Connection objects, handle exceptions when connecting to a database, perform transactions by using the Transaction object

• Create, add, delete, and edit data in a connected environment.

This objective may include but is not limited to: Retrieve data by using a DataReader object, build SQL commands in Server Explorer, build SQL commands in code, create parameters for a Command object, perform database operations by using a Command object, retrieve data from a database by using a Command object, perform asynchronous operations by using a Command object

• Query data from data sources by using LINQ

This objective may include but is not limited to: LINQ to SQL, LINQ to Objects, LINQ to Microsoft ADO.NET, LINQ to XML

• Create, add, delete, and edit data in a disconnected environment.

This objective may include but is not limited to: Create a DataSet graphically, create a DataSet programmatically, add a DataTable to a DataSet, add a relationship between tables within a DataSet, navigate a relationship between tables, merge DataSet contents, copy DataSet contents, create a typed DataSet, create DataTables, manage data within a DataTable, create and use DataViews, represent data in a DataSet by using XML, use the OleDbDataAdapter object to access an ADO Recordset or Record, generate DataAdapter commands automatically by using the CommandBuilder object, generate DataAdapter commands programmatically, populate a DataSet by using a DataAdapter, update a database by using a DataAdapter, resolve conflicts between a DataSet and a database by using a DataAdapter, respond to changes made to data at the data source by using DataAdapter events, perform batch operations by using DataAdapters

• Manage XML by using the XML Document Object Model (DOM).

This objective may include but is not limited to: Read XML data into the DOM, modify an XML document by adding and removing nodes, modify nodes, write data in an XML format by using the DOM, handle DOM events

• Read, write, and validate XML by using the XmlReader class and the XmlWriter class.

This objective may include but is not limited to: read XML data, elements, and attributes, read specific elements or attributes, use XmlTextReader, XmlNodeReader, XmlValidatingReader, and XmlWriter classes

Implementing Printing and Reporting Functionality in a Windows Forms Application

• Manage the print process by using print dialogs.

This objective may include but is not limited to: Configure print options at run time, change printers attached to a user's computer, configure the PrintPreviewDialog control, set page details for printing by using the PageSetupDialog

• Construct print documents.

This objective may include but is not limited to: Configure the PrintDocument component, print a text document in a Windows form, print graphics in a Windows form, print a document by using the PrintDialog component, alert users to the completion of a print job

• Enable security features for printing in a Windows Forms application
• Create a customized PrintPreview component.

This objective may include but is not limited to: setting the Document property to establish the document to be previewed, set Columns and Row properties, set the UseAntiAlias property for smoother text, configure zoom settings, set StartPage property, add custom methods and events to a PrintPreview control

Enhancing Usability

• Perform drag and drop operations.

This objective may include but is not limited to: perform drag and drop within an application and across applications, perform drag and drop by using the Treeview control

• Implement globalization and localization for a Windows Forms application.

This objective may include but is not limited to: work with resource files for localization, determine installed locales

• Implement accessibility features
• Create and configure multiple-document interface (MDI) forms.

This objective may include but is not limited to: create parent and child forms, identify active child form, send data to an active child form, arrange child forms, create menus for an MDI application

• Create, configure, and customize user assistance controls and components.

This objective may include but is not limited to: Configure the PropertyGrid component, configure the ProgressBar control, configure StatusStrip, configure ToolTip, configure ErrorProvider, configure HelpProvider controls, configure timer components

• Persist Windows Forms application settings between sessions

Implementing Asynchronous Programming Techniques to Improve the User Experience

• Manage a background process by using the BackgroundWorker component.

This objective may include but is not limited to: Run a background process, announce completion of a background process, cancel a background process, report on the progress of a background component, request status of a background component

• Change the appearance of a UI element by using triggers.

This objective may include but is not limited to: using multiple triggers; using property triggers; using event triggers; using data triggers

• Implement an asynchronous method.

This objective may include but is not limited to: Create an asynchronous method, create a new process thread, implement advanced asynchronous techniques

Deploying Windows Forms Controls

• Create a composite Windows Forms control.

This objective may include but is not limited to: create properties, methods and events, expose properties of constituent controls, create custom dialog boxes, customize a control's paint and render, set visibility at run time, provide a toolbox bitmap

• Create a custom Windows Forms control by inheriting from the control class
• Create an extended control by inheriting from an existing Windows Forms control

Configuring and Deploying Applications

• Configure the installation of a Windows Forms application by using ClickOnce technology.

This objective may include but is not limited to: install a Windows Forms application on a client computer, install a Windows Forms application from a server, configure the required permissions of an application

• Install a Windows Presentation Foundation (WPF) browser application by using ClickOnce
• Install a Visual Studio Tools for Office (VSTO) application by using ClickOnce
• Configure and work with Windows Vista User Account Control (UAC) by using ClickOnce deployments
• Create a Windows Forms setup application.

This objective may include but is not limited to: configure setup project to add icons during setup, set deployment project properties, configure conditional installation based on operating system versions, set appropriate Launch Conditions based on the .NET Framework version, add custom actions to a setup project, add error-handling code to a setup project

• Set appropriate security permissions to deploy the application.

This objective may include but is not limited to: elevated permissions

• Configure Trusted Application deployments
• Configure security features in an application.

This objective may include but is not limited to: Configure code access security, configure the application to work with UAC, configure Windows manipulation permissions, configure appropriate file access permissions for the application, control printing security for the application

 

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)

Exam 70-563

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

Validating an application design against specifications

• Analyze the technical feasibility of application design.

May include but is not limited to: architecture (Windows vs. ASP), resourcing (staffing, skill sets, hardware, OS), network capacity and distribution, application extensibility, existing applications, exposing APIs, timeframe, integration of third-party controls, applications, external data sources

• Validate proof of concept.

May include but is not limited to: evaluating the technical specification and comparing against the proof of concept

• Evaluate design against available resources.

May include but is not limited to: cost, timeframe, resources (local vs. distributed teams), hardware resources, network resources, customer infrastructure (required hardware such as servers, routers, and RAM and required software such as OS)

• Evaluate testing requirements.

May include but is not limited to: stress testing, testing against high activity and frequency of operations, testing with a true representative sample, building test cases

Planning data management

• Plan data access strategy.

May include but is not limited to: retrieve data from disparate data sources (XML data, flat files, and relational databases, manage class-generated data, LINQ), manage bulk imports and exports (ETL, data transformation), choose appropriate data access layer, manage data purity (re-validate data across trust boundaries), manage data asynchronously, leverage synchronization services, connection management

• Plan data caching and persistence strategy.

May include but is not limited to: managing data cache, managing data persistence (storing disconnected scenarios, managing offline data), mapping database to local cache (loading all customers locally), managing data state

• Select a data storage mechanism.

May include but is not limited to: security, target data engine, target environment (workstation capabilities, OS, bandwidth, domain vs. workgroup, connectivity, reliability)

• Plan application data sharing.

May include but is not limited to: managing data shared between forms and processes, managing data synchronization (ADO.NET synchronization services), drag and drop files or objects from outside sources

• Design a schema evolution management strategy.

May include but is not limited to: synchronizing an application with a schema

• Design a concurrency management strategy.

May include but is not limited to: database segmentation, planning for concurrency and collision avoidance, optimistic vs. pessimistic

Planning user interaction and presentation strategy

• Design application content flow.

May include but is not limited to: user navigation, user interface goals, layout techniques (dynamic layout techniques), components not part of control data class (ToolTipProvider, ErrprProvider, HelpProvider)

• Plan data capture.

May include but is not limited to: validating input (type converters, regular expressions, apply business rules), responding to mouse and keyboard input, pick list (combo boxes, list boxes, auto-fill text boxes)

• Design a reporting strategy.

May include but is not limited to: MicrosoftReportViewer, CrystalReportViewer, print classes, embedded vs. external server-generated reports

• Design user interface components.

May include but is not limited to: common dialog boxes, designing navigation by using menus, SDI and MDI (multiple monitor configuration, implementing master and detail), single vs. multiple instances of the application, implementing data binding, abstracting with custom controls (abstract base classes), using and creating user controls (extend a custom control to add functionality, creating a custom DataGridView column), integrating with non-Forms UI elements

• Design a data-binding strategy.

May include but is not limited to: populating from XML, populating from SQL, populating from object data source and entity, lazy loads, updating bound data (concurrency management, late commits, lazy commits), data context

• Design forms inheritance.

May include but is not limited to: visual inheritance, functionality common across forms

Designing security implementation

• Design role-based security.

May include but is not limited to: implementing security by using IPrincipal and IIdentity, custom vs. platform security, managing user functionality, limit or gate access, data decoupling, designing security profiles

• Design data transmission and storage.

May include but is not limited to: SSL, encryption (offline data, password management)

• Design authentication and authorization.

May include but is not limited to: login mechanism (domain user accounts, SQL Server user accounts), role-based application configuration, security auditing and logging, file system rights and authorization, Web service rights and authentication

• Plan Windows Vista compliance.

May include but is not limited to: user application data directory (registry settings, isolated storage)

• Plan least-privileged execution.

May include but is not limited to: User Access Control (UAC), assembly authentication, certificate management

•  

Planning application deployment and maintenance

• Select an installer.

May include but is not limited to: ClickOnce, MSI, XCOPY, third party (InstallShield)

• Plan for multiple-component application deployment.

May include but is not limited to: bootstrap installation, legacy applications, application suite, COM-visible assemblies

• Plan application re-deployment.

May include but is not limited to: deploying Windows-based applications and updating, deploying a patch (dependencies on service packs), database synchronization (re-deployment of data in place [merge]), preserving configuration, unattended installation

• Plan database deployment.

May include but is not limited to: existing or shared instance; remote server; DLL deployment; shared GAC deployment; embedded database

• Plan application removal.

May include but is not limited to: clean uninstall, uninstalling shared components, uninstalling remaining components, restoring client state, clean or restore registry

• Plan a performance-monitoring strategy.

May include but is not limited to: profiling, tracing, performance counters, audit trails

• Plan an exception-management strategy.

May include but is not limited to: implementing a framework for logging and exception handling, error handling and reporting, user feedback

Designing the application architecture

• Plan a globalization and localization strategy.

May include but is not limited to: embedding resources into the application for localization

• Design for accessibility.

May include but is not limited to: screen reader, tool tips

• Plan an application migration strategy.

May include but is not limited to: interoperability with legacy applications, integrating with non-Forms applications

• Design n-layer architecture.

May include but is not limited to: logically separating concerns (business objects layer or tier, data tier), design project structure (effective use of sub projects)

• Plan a component re-use strategy.

May include but is not limited to: sharing common resources, coupling of generic elements to specific elements, Object-Oriented modeling techniques, dealing with COM interoperability issues associated with existing legacy components

• Plan system resource management.

May include but is not limited to: understand JIT or GAC caching

• Plan multi-threaded implementation and UI responsiveness.

May include but is not limited to: implementing multi-threading and reporting progress, updating the UI from a background thread

Designing for optimized performance

• Plan optimized data retrieval.

May include but is not limited to: type data sets vs. un-typed data sets, entity models, ORM performance, performance monitoring of tiers for latency and chunkiness (batch retrieval, multiple small calls), roundtrip optimization, caching of frequently used data (pick List data, drop down data, list boxes)

• Design state management.

May include but is not limited to: storing application state, storing user state, managing server-side state

• Plan resource management.

May include but is not limited to: memory, GDI handles, unmanaged resources, resource disposition memory management, resource planning (skill set to project tasks), order of application component development

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

 

Exam 70-561

Microsoft .NET Framework 3.5, ADO.NET Application Development

Connecting to Data Sources

• Manage connection strings.

May include but is not limited to: using the ConnectionStringBuilder; leveraging the ConfigurationManager; protecting the connection string; using Security Support Provider Interface (SSPI) or SQL Server authentication; correctly addressing the SQL Server instance; mana