| Exam news | |
| Audience profile | |
| Credit toward certification | |
| Code languages | |
| Preparation tools and resources | |
| Skills measured |
Exam 70-552: UPGRADE: MCAD Skills to MCPD Windows Developer by Using the Microsoft .NET Framework became available in May 2006. This is a professional (PRO) upgrade exam for those who have obtained the Microsoft Certified Application Developer (MCAD) certification.
| • | This upgrade exam is available at 40 percent off retail price |
Candidates for this exam work on a team in a medium-sized or large development environment that uses Microsoft Visual Studio .NET 2003 Enterprise Developer or Visual Studio 2005. Candidates should have at least two years of experience developing Windows-based applications by using the Microsoft .NET Framework. Candidates should have a working knowledge of Visual Studio 2005.
Candidates should have at least three to four years of on-the-job experience dedicated to Windows-based application development and should have worked in the following phases of the application life cycle:
| • | Technical envisioning and planning |
| • | Design and development |
| • | Stabilizing and releasing |
When you pass Exam 70-552: UPGRADE: MCAD Skills to MCPD Windows Developer by Using the Microsoft .NET Framework, you complete the requirements for the following certifications:
| • | Microsoft Certified Professional Developer: Windows Developer |
| • | Microsoft Certified Technology Specialist: .NET Framework 2.0 Windows Applications |
When the exam begins, you can choose the programming language in which the code segments will appear. The available code languages for this exam are:
| • | Microsoft Visual Basic 2005 |
| • | Microsoft Visual C# 2005 |
| • | Microsoft Visual C++ 2005 |
To help you prepare for this exam, Microsoft Learning recommends that you have hands-on experience with the product and that you use the following training resources. These training resources do not necessarily cover all of the topics listed in the "Skills measured" section.
| Classroom training | Microsoft E-Learning | Microsoft Press books | Practice tests |
Workshop 2541: Core Data Access with Microsoft Visual Studio 2005 (three days) Workshop 2542: Advanced Data Access with Microsoft Visual Studio 2005 (two days) Workshop 2546: Core Windows Forms Technologies with Microsoft Visual Studio 2005 (three days) Workshop 2547: Advanced Windows Forms Technologies with Microsoft Visual Studio 2005 (two days) | Collection 2546: Core Windows Client Development with Microsoft Visual Studio 2005 (18-hour series) Collection 2547: Advanced Windows Client Development with Microsoft Visual Studio 2005 (12-hour series) Collection 2541: Core Data Access Development with Microsoft Visual Studio 2005 (18-hour series) Collection 2542: Advanced Data Access Development with Microsoft Visual Studio 2005 (12-hour series) Note Collection 2956 is now offered as two collections: Collection 5160: Core Development with the Microsoft .NET Framework 2.0 Foundation (formerly part of Collection 2956) (16-hour series) Collection 5161: Advanced Development with the Microsoft .NET Framework 2.0 Foundation (formerly part of Collection 2956) (14-hour series) | MCTS Self-Paced Training Kit (Exam 70-526): Microsoft .NET Framework 2.0 Windows-Based Client Development (ISBN: 9780735623330) MCTS Self-Paced Training Kit (Exam 70-536): Microsoft .NET Framework 2.0—Application Development Foundation (ISBN: 9780735622777) MCPD Self-Paced Training Kit (Exam 70-548): Designing and Developing Windows-Based Applications Using the Microsoft .NET Framework (ISBN: 9780735623392) CLR via C#, Second Edition (ISBN: 9780735621633) Debugging Microsoft .NET 2.0 Applications (ISBN: 9780735622029) Programming Microsoft Visual Basic 2005: The Language (ISBN: 9780735621831) Programming Microsoft Visual C# 2005: The Language (ISBN: 9780735621817) Programming Microsoft ADO.NET 2.0 Core Reference (ISBN: 9780735622067) | MeasureUp (Measureup.com) Self Test Software (Selftestsoftware.com) |
| • | Learning Plan: Get started by creating a step-by-step study guide that is based on recommended resources for this exam. |
| • | Microsoft Learning Community: Join newsgroups and visit community forums to connect with your peers for suggestions on training resources and advice on your certification path and studies. |
| • | TechNet: Designed for IT professionals, this site includes how-to instructions, best practices, downloads, technical resources, newsgroups, and chats. |
| • | MSDN: Designed for IT professionals, this site includes how-to instructions, best practices, downloads, technical resources, newsgroups, and chats. |
This certification exam measures your ability to develop and implement rich client applications, targeting the Windows Forms platform using .NET Framework 2.0. Before taking the exam, you should be proficient in the job skills listed in the following table. The table lists Official Microsoft Learning Products that may help you reach competency in the skills being tested in the exam.
| KEY: |
| Skills measured by Exam 70-552 | Workshop 2541 | Workshop 2542 | Workshop 2546 | Workshop 2547 | 2956E (now Collections 5160 and 5161) | ||||||||||||||||||||||||||||||||||||
| Section 1 | |||||||||||||||||||||||||||||||||||||||||
| Developing applications that use system types and collections | |||||||||||||||||||||||||||||||||||||||||
Manage data in a .NET Framework application by using .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)
| |||||||||||||||||||||||||||||||||||||||||
Implement .NET Framework interfaces to cause components to comply with standard contracts. (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)
| |||||||||||||||||||||||||||||||||||||||||
Debug and trace a .NET Framework application by using the System.Diagnostics 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.
| |||||||||||||||||||||||||||||||||||||||||
Access files and folders by using the File System 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 .NET Framework applications by using the .NET Framework 2.0 security features | |||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||
Enhance the user interface of a .NET Framework application by using the System.Drawing namespace.
| |||||||||||||||||||||||||||||||||||||||||
| Section 2 | |||||||||||||||||||||||||||||||||||||||||
| Creating a UI for a Windows Forms Application by Using Standard Controls | |||||||||||||||||||||||||||||||||||||||||
Manage control layout on a Windows Form.
| |||||||||||||||||||||||||||||||||||||||||
Add and configure a Windows Forms control.
| |||||||||||||||||||||||||||||||||||||||||
Create and configure menus.
| |||||||||||||||||||||||||||||||||||||||||
| Integrating Data in a Windows Forms Application | |||||||||||||||||||||||||||||||||||||||||
Implement data-bound controls.
| |||||||||||||||||||||||||||||||||||||||||
Manage connections and transactions.
| |||||||||||||||||||||||||||||||||||||||||
Read, write, and validate XML by using the XmlReader class and the XmlWriter class.
| |||||||||||||||||||||||||||||||||||||||||
| Enhancing Usability | |||||||||||||||||||||||||||||||||||||||||
Create, configure, and customize user assistance controls and components.
| |||||||||||||||||||||||||||||||||||||||||
| Implementing Asynchronous Programming Techniques to Improve the User Experience | |||||||||||||||||||||||||||||||||||||||||
Manage a background process by using the BackgroundWorker component.
| |||||||||||||||||||||||||||||||||||||||||
| Configuring and Deploying Applications | |||||||||||||||||||||||||||||||||||||||||
Configure the installation of a Windows Forms application by using ClickOnce technology.
| |||||||||||||||||||||||||||||||||||||||||
| Section 3 | |||||||||||||||||||||||||||||||||||||||||
| Envisioning and Designing an Application | |||||||||||||||||||||||||||||||||||||||||
Evaluate the technical feasibility of an application design concept.
| |||||||||||||||||||||||||||||||||||||||||
Create a proof-of-concept prototype.
| |||||||||||||||||||||||||||||||||||||||||
Evaluate the technical specifications for an application to ensure that the business requirements are met.
| |||||||||||||||||||||||||||||||||||||||||
Evaluate the logical design of an application.
| |||||||||||||||||||||||||||||||||||||||||
Evaluate the physical design of an application. Considerations include the design of the project structure, the number of files, the number of assemblies, and the location of these resources on the server.
| |||||||||||||||||||||||||||||||||||||||||
| Designing and Developing a User Interface | |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate layout for the visual interface.
| |||||||||||||||||||||||||||||||||||||||||
Evaluate a strategy for implementing a common layout throughout the UI.
| |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate control based on design specifications.
| |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate data validation method at the UI layer.
| |||||||||||||||||||||||||||||||||||||||||
Choose appropriate user assistance and application status feedback techniques.
| |||||||||||||||||||||||||||||||||||||||||
| Designing and Developing a Component | |||||||||||||||||||||||||||||||||||||||||
Establish the required characteristics of a component.
| |||||||||||||||||||||||||||||||||||||||||
Create the high-level design of a component.
| |||||||||||||||||||||||||||||||||||||||||
Develop the public API of a component.
| |||||||||||||||||||||||||||||||||||||||||
Develop the features of a component.
| |||||||||||||||||||||||||||||||||||||||||
Develop an exception handling mechanism.
| |||||||||||||||||||||||||||||||||||||||||
Develop the data access and data handling features of a component.
| |||||||||||||||||||||||||||||||||||||||||
Develop a component to include profiling requirements.
| |||||||||||||||||||||||||||||||||||||||||
| Designing and Developing an Application Framework | |||||||||||||||||||||||||||||||||||||||||
Consume a reusable software component.
| |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate exception handling mechanism.
| |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate implementation approach for the application design logic.
| |||||||||||||||||||||||||||||||||||||||||
Choose an appropriate event logging method for the application.
| |||||||||||||||||||||||||||||||||||||||||
Evaluate the application configuration architecture.
| |||||||||||||||||||||||||||||||||||||||||
| Testing and Stabilizing an Application | |||||||||||||||||||||||||||||||||||||||||
Perform a code review. | |||||||||||||||||||||||||||||||||||||||||
Evaluate the testing strategy. |