With Advanced Custom Training, you will learn hands on, from the best instructors.

The MCPD Enterprise Application Developer 3.5 program is a hands on, intensive 15-day developer class designed to teach Core Foundation, WinForms, Web, Windows Presentation and Windows Communication Foundations technologies. Developers learn  how to build interactive, data-driven client applications, targeting the Windows Forms, Web Forms (ASP .NET 3.5),  AJAX, Silverlight, Console and Service application platform using the .NET Framework 3.5 .

This camp also offers smaller, 7 day camps where you can focus only on the Windows Forms or Web Forms development and receive your MCTS certification.

 

Our MCPD certification programs contains Microsoft courseware which covers the following materials:

.NET Framework Development Fundamentals Developing applications that use system types and collections Embedding configuration, diagnostic, management, and installation features into a .NET Framework application Implementing serialization and input/output functionality in a .NET Framework application Improving the security of .NET Framework applications by using the .NET Framework security features Implementing interoperability, reflection, and mailing functionality in a .NET Framework application Implementing globalization, drawing, and text manipulation functionality in a .NET Framework application

Windows Communication Foundation Creating Services Exposing and Deploying Services Instrumenting and Administering Services Consuming Services Securing Services Managing the Service Life Cycle

Windows Forms Application Development Creating a UI for a Windows Forms Application by Using Standard Controls Integrating Data in a Windows Forms Application Implementing Printing and Reporting Functionality in a Windows Forms Application Enhancing Usability Implementing Asynchronous Programming Techniques to Improve the User Experience Developing Windows Forms Controls Configuring and Deploying Applications

ADO.NET Application Development Connecting to Data Sources Selecting and Querying Data Modifying Data Synchronizing Data Working with Disconnected Data Object Relational Mapping by Using the Entity Framework

ASP.NET Application Development Configuring and Deploying Web Applications Working with Data and Services Consuming and Creating Server Controls Troubleshooting and Debugging Web Applications Working with ASP.NET AJAX and Client-Side Scripting Programming Web Applications Targeting Mobile Devices

WE LIMIT OUR CLASS SIZES TO 12 STUDENTS - THIS ALLOWS FOR MORE ATTENTION FROM THE INSTRUCTOR, MORE SPACE FOR STUDENTS TO WORK AND MORE FOCUSED ENVIRONMENT.

MCPDClasses.com & Advanced Custom Training can get you there:

Our student pass the Microsoft Certification Exams. Our resources and methods are second to none.  We have a 98% success rate of students passing these exams the first time.

During the course of the class day, we teach you how to use the technology with real world examples. 

Facilities:

Our facilities are second to none.  Our training center is located 45 minutes south of Tampa in beautiful Sarasota, FL.  We use top end computer equipment, 20in monitors, cpu's with Virtualization, plenty of memory. Our chairs are comfortable - our desk allow plenty of room for student computer, your laptop and book.
  
Students stay at Marriott & Hilton brand hotels which provide full studio amenities including flat panel tvs, microwave and refrigerator in every room.  Students have access to 20+ restaurants within walking distance of the hotel.

Compare Us To The Competition - 

Many of our competitors place 30+ students in a classroom with only one instructor.  Often they try to extend the life of very old equipment with lag and slow performance on the software used today.  Our competitors often use less than desirable (extended stay) type of hotels in areas not suited for professionals.

Our Microsoft Certified Trainers (MCTs) are not instructors who "read from books".  Rather, our trainers are real world consultants who work directly with companies in addition to training our camps.  

We provide training in both C# or VB.NET!
You can test in either C# or VB.NET for MCPD Enterprise Application Developer.

Bootcamp Schedule -

Classroom hours are from 8:00am until 5:00pm daily. During these hours, students will participate in interactive lectures and demonstrations. Students will have hands on lab exercises based on topics related to the technology and certification expectations.  Additionally, students will spend several hours in the evening reviewing practice questions to prepare for the offical certification exam.

Course Materials -

We use a combination of Microsoft courseware along and custom labs written to demonstrate the different test objectives in a visual, hands on environment.  Additionally, we provide videos which demonstrate even more details so students will have constant visuals of topics.

Daily lectures, labs, and review sessions are supplemented by a combination of:

• Microsoft Courseware 
• Additional Files & Resources for add on labs
• Self Study Practice Test Resources.

Delivery Schedule:

The MCPD Enterprise Application Developer Bootcamp prepares students to achieve 5 certifications during the program:

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

Optional Cert - Ad Ons-

MCPD: ASP .NET Developer v3.5
MCPD: Win Forms Developer 3.5

Days	Module Description		Exam
1-3	MCPD .NET Framework 3.5 WinForms		70-505
4-6	MCPD .NET Framework 3.5 Core Foundations		70-536
7-9	MCPD .NET Framework 3.5 Web Client Dev		70-562
10-12	.NET Framework 3.5 WPF & ADO .NET		70-561
13-15	.NET Framework 3.5 WCF & Enterprise		70-503 / 70-565

The MCPD: Enterprise Application Developer 3.5 certification requires six exams to achieve this certification.

Students take all of these test onsite at our training facility while attending our course.  Below are the objectives of these exams as presented by Microsoft.

 

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.

  This objective may include but is not limited to: Add a Windows Form to a project at design time. Configure a Windows Form to control accessibility, appearance, behavior, configuration, data, design, focus, layout, style, and other functionality

• Manage control layout on a Windows Form.

  This objective may include but is not limited to: Group and arrange controls by using the Panel control, GroupBox control, TabControl control, FlowLayoutPanel control, and TableLayoutPanel control

• Add and configure a Windows Forms control.

  This objective may include but is not limited to: Use the integrated development environment (IDE) to add a control to a Windows Form or other container control of a project at design time, add controls to a Windows Form at run time, configure controls on a Windows Form at design time to optimize the UI, modify control properties

• Create and configure menus.

  This objective may include but is not limited to: Create and configure a MenuStrip component on a Windows Form, change the displayed menu structure programmatically, create and configure the ContextMenuStrip component on a Windows Form

• Create event handlers for Windows Forms and controls.

  This objective may include but is not limited to: Manage mouse and keyboard events within Windows Forms applications, create event handlers at run time to respond to system or user events dynamically, connect multiple events to a single event handler

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

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)

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

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.

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

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; managing "User Instance" and AttachDBfilename

• Manage connection objects.

  May include but is not limited to: managing connection state, managing connection pool; implementing persistent data connections; implementing Multiple Active Result Sets (MARS); encrypting and decrypting data

• Work with data providers.

  May include but is not limited to: limitations, behaviors, performance, installation issues, deployment issues; ODBC, Microsoft OLE DB, SqlClient, managed providers, third-party providers, native providers

• Connect to a data source by using a generic data access interface.

  May include but is not limited to: System.Data.Common namespace classes

• Handle and diagnose database connection exceptions.

  May include but is not limited to: implementing try/catch handlers

Selecting and Querying Data

• Build command objects.

  May include but is not limited to: building Parameters collections; using input and output parameters and return values; selecting an appropriate CommandType action; selecting an appropriate Execute method; using the CommandBuilder class; choosing appropriate CommandBehavior

• Query data from data sources.

  May include but is not limited to: writing queries to solve assigned problems; implementing data paging; sorting, filtering, and aggregating data

• Retrieve data source data by using the DataReader.

  May include but is not limited to: retrieving data from SELECT statements; retrieving data from stored procedures; working with multiple result sets

• Manage data by using the DataAdapter or the TableAdapter.

  May include but is not limited to: retrieving data from SELECT statements; retrieving data from stored procedures; working with multiple result sets; working with JOIN products; creating updatable DataAdapters and TableAdapters; modifying TableAdapter Fill methods

• Execute an asynchronous query.

  May include but is not limited to: handling asynchronous events

• Handle special data types.

  May include but is not limited to: Binary Large Objects (BLOBs); Filestream, Spatial, Table Value Parameters

• Query data sources by using LINQ.

  May include but is not limited to: extended method; CLR delegate; lambda expressions; classes of the System.LINQ.Expressions namespace

• Manage exceptions when selecting data.

  May include but is not limited to: identifying and resolving syntax errors; security exceptions

Modifying Data

• Manage transactions.

  May include but is not limited to: selecting an appropriate transaction isolation level; participating in local transactions; participating in distributed transactions; using declarative transactions

• Manage data integrity.

  May include but is not limited to: cascading updates or cascading deletes; auto number management; server-generated value management; client-side data validation; business rules, constraints

• Update data.

  May include but is not limited to: update data by using stored procedures; update dataSets to data source; managing concurrency

• Manage exceptions when modifying data.

  May include but is not limited to: resolve exceptions from data integrity, constraint, or referential integrity violations; data locking conflicts; data collision issues

• Transform data by using LINQ.

  May include but is not limited to: aggregation operators; JOIN operator, QUERY operator, LIKE, etc.

Synchronizing Data

• Monitor event notifications.

  May include but is not limited to: implement notifications by using SqlDependency or SqlNotificationRequest

• Cache data.

  May include but is not limited to: SqlCacheDependency, Local Data Cache

• Manage update conflicts between online data and offline data.

• Partition data for synchronization.

• Implement Synchronization Services.

  May include but is not limited to: SyncAgent, SyncTable, ClientSyncProvider, ServerSyncProvider, SyncAdapter

Working with Disconnected Data

• Manage occasionally connected data.

• Programmatically create data objects.

  May include but is not limited to: DataTable; DataSet

• Work with untyped DataSets and DataTables.

  May include but is not limited to: populating a DataSet or DataTable

• Expose a DataTableReader from a DataTable or from a DataSet.

• Work with strongly typed DataSets and DataTables.

Object Relational Mapping by Using the Entity Framework

• Define and implement an Entity Data Model.

  May include but is not limited to: mapping schemas and storage metadata; EDM Generator

• Query data by using Object Services.

  May include but is not limited to: querying data as objects and shaping results; working with objects; managing the Object Context; customizing objects

• Map data by using the Entity SQL Language.

  May include but is not limited to: manually define mapping files; execute an Entity SQL Query by using EntityCommand

• Access entity data by using the EntityClient Provider.

  May include but is not limited to: managing EntityConnection; creating EntityCommand; executing a query by using EntityDataReader; managing EntityTransaction

Exam 70-503

Microsoft .NET Framework 3.5 - Windows Communication Foundation Application Development

Creating Services

• Define Service contracts.
• Define Data contracts.
• Define Operation contracts.
• Define Message contracts.
• Process generic messages.

Exposing and Deploying Services

• Create and configure service endpoints.
• Manage consistency between life cycle, sessions, concurrency, and bindings.
• Host a service in a managed application.
• Host a service on a Web server.
• Create custom behaviors.

Instrumenting and Administering Services

• Implement end-to-end service tracing.
• Monitor service health.
• Log messages.
• Dynamically configure the service by using the service model.
• Implement inspectors.

Consuming Services

• Create a service proxy.
• Configure the client endpoint.
• Call a service by using a service proxy.
• Handle exceptions on clients.
• Consume non-WCF services.

Securing Services

• Implement transport-level security.
• Implement message-level security.
• Authenticate clients.
• Authorize clients.
• Impersonate clients.

Managing the Service Life Cycle

• Manage instances.
• Manage sessions.
• Manage transactions.
• Manage concurrency.
• Manage consistency between instances, sessions, transactions, and concurrency.

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

Envisioning and Designing an Application

• Analyze and refine the logical design of the application

  May include but is not limited to: clarify logical design; evaluate the layers; evaluate application workflow; evaluate data flow diagrams; evaluate performance; evaluate maintainability; evaluate extensibility; evaluate availability; evaluate design against use cases; evaluate recoverability; evaluate data integrity

• Analyze and refine the physical design of the application

  May include but is not limited to: evaluate the tiers; evaluate migration strategy; clarify physical design; evaluate component specification; evaluate performance; evaluate maintainability; evaluate extensibility; evaluate scalability; evaluate availability; evaluate recoverability; evaluate data integrity

• Analyze and refine the database design of the application

  May include but is not limited to: evaluate stored procedure requirements; evaluate schema requirements; identify whether triggers are required; identify required data types

• Analyze and refine the integration strategy

  May include but is not limited to: evaluate integration of application with other systems; internal vs. external integration; enable future integration with other systems; evaluate WCF as an integration component

• Identify the appropriate technology

  May include but is not limited to: identify the technology and format for transport; identify the technology and format for messages; identify the technology and format for required client interoperability; choose a platform - Windows vs. Web; choose a communication technology - Windows Communication Foundation (WCF), Web services, Remoting, message queueing; define a component communication strategy; recommend build vs. buy; choose a platform - Windows Presentation Foundation (WPF), ASP.NET, AJAX, Windows Forms, Windows service

• Analyze technical feasibility

  May include but is not limited to: develop a proof of concept; perform a technical risk assessment; recommend changes to the design to meet the same technical goals; analyze feasibility of design in planned environment; determine whether the proposed design could integrate with other systems by using WCF

• Analyze security requirements

  May include but is not limited to: recommend an authentication method; recommend an authorization method; recommend a secure communication method

Designing and Developing an Application Framework

• Choose an appropriate implementation approach for the application design logic

  May include but is not limited to: choose data storage mechanisms; choose data flow structure; choose decision flow structure; state management techniques; security implementation; finalize component specification

• Define the interaction between framework components

  May include but is not limited to: determine types of clients that will access the application; define data APIs, security APIs, abstract classes, class interfaces, and data contracts; map data to object model; messaging and transport methods such as WCF, Remoting, Web services, MSMQ, Enterprise Services

• Define a validation strategy

  May include but is not limited to: define where in the framework each type of validation will happen; choose a validation method

• Define an event-logging strategy

  May include but is not limited to: choose a storage mechanism for logged events; choose a systemwide event logging method; decide logging levels based on severity or priority; define a reporting strategy

• Define a monitoring strategy for specific characteristics or aspects of an application

  May include but is not limited to: decide whether to monitor data; decide which characteristics to monitor; choose event monitoring mechanisms; decide monitoring levels based on requirements; choose a system-wide monitoring method from the available monitoring mechanisms; define a reporting strategy

Designing Application Components

• Create the high-level design of a component

  May include but is not limited to: establish the life cycle of a component; define user interface for each component; define interoperability requirements; identify and extract reusable components; document the design of a component by using pseudo code, class diagrams, sequence diagrams, activity diagrams, and state diagrams; decide whether to require constructor input

• Define the internal architecture of a component

  May include but is not limited to: decide whether existing functionality can be implemented or inherited; decide how to handle unmanaged and managed resources; decide which extensibility features are required; determine state management implementation; decide whether a component must be multithreaded; decide which functions to implement in the base class, abstract class, or sealed class

• Define the data handling for a component

  May include but is not limited to: define data access; analyze data relationships; analyze the data handling requirements of a component

• Consume components

  May include but is not limited to: identify reusable components; handle unmanaged components; identify whether a component needs to be extended; identify whether a component needs to be wrapped; identify whether any existing functionality needs to be hidden; test that reused components meet the specifications

• Define a strategy for exceptions and other component feedback

  May include but is not limited to: identify expected exceptions; decide how to deal with expected exceptions; decide how to deal with unhandled exceptions; decide how to deal with WCF faults; define other component feedback, such as events, callbacks, and messages; define a reporting strategy

Stabilizing and Testing an Application

• Define a performance testing strategy

  This objective may include but is not limited to: define how you will test an application's performance under a specified load; define how you will test an application's behavior when specified load is exceeded

• Define a functional testing strategy

  This objective may include but is not limited to: identify component interactions and dependencies; define how you will test a component in isolation; define how you will test a component's interactions with other components

• Perform integration testing

  This objective may include but is not limited to: run integration tests to determine whether the component interacts with other components as expected; verify results; test that endpoints are correct and service references are updated for communication methods such as WCF, Remoting, Web services, MSMQ, and Enterprise Services

• Perform a code review

  This objective may include but is not limited to: perform a security review; perform a functional review; perform a performance review; perform a regulatory compliance review

• Resolve a bug

  This objective may include but is not limited to: analyze root cause for problems in code, such as exception handling issues, performance problems, security issues, resource usage issues, and features that do not perform as expected

Migrating, Deploying, and Maintaining an Application

• Create a deployment plan

  This objective may include but is not limited to: identify component-level deployment dependencies; identify location of specific components for deployment; determine a deployment method; identify required assembly registration; document the physical deployment of the application

• Analyze the configuration of the production environment

  This objective may include but is not limited to: security environment; database environment; networking environment; .NET Framework versions; IIS versions; hardware and software requirements

• Analyze performance monitoring data

  This objective may include but is not limited to: identify performance spikes; identify performance trends; monitor and analyze resource usage; monitor and analyze security aspects

• Analyze logs

  This objective may include but is not limited to: review logs during deployment phase; review logs to determine source of failure; trace data to identify source of error

Advanced Custom Training offers the highest quality technical education in an all-inclusive course package specifically designed for the needs and ease of our students. We attend to every detail so our students can focus solely on their educational objectives.

• All inclusive package includes Airfare (Roundtrip to Tampa/Sarasota Florida), Transportation to and from airport, 15 Days of Hotel Accommodations, Breakfast and Lunch, Unlimited Beverages and Snacks.
• Intensive Hands-on Training by Microsoft Certified Trainers utilizing our (Lecture | Lab | Demo | Video) Delivery
• Microsoft Courses  and custom materials comprised of comprehensive study materials, Microsoft training materials, practical lab manuals, and practice test resources
• Examination Vouchers
• On-site Certification Testing
• Examination Passing Policy

Advanced Custom Training has the best well-equipped educational facilities where you will attend instruction and labs and have access to comfortable study and rest/break room.

Our Microsoft Certified Trainers teach to accommodate every student’s learning needs by working one on one with students, hands-on labs, self-testing, question and answer sessions. 

Which class/camp are you interested in? * MCPD: .Net Visual Studio 2008 Bootcamp MCITP: Windows 7 or Server 2003/2008 Bootcamp MCITP: SQL 2008 Business Intelligence Bootcamp MCITP: SQL 2008 Admin Bootcamp MCITP: SQL 2008 Developer Bootcamp MCITP: SQL 2008 Admin/Dev Combo Bootcamp Microsoft On-site Training Non-bootcamp Microsoft Training First Name * Last Name * Email Address * Phone Number