• Understand computer storage and data types. This objective may include but is not limited to the following:
  • How a computer stores programs and the instructions in computer memory.
  • Memory stacks and heaps
  • Memory size requirements for the various data storage types
  • Numeric data and textual data
• Understand computer decision structures. This objective may include but is not limited to the following:
  • Various decision structures used in all computer programming languages
  • If decision structures
  • Multiple decision structures such as If…Else and switch/Select Case
  • Reading flowcharts
  • Decision tables
  • Evaluating expressions
• Identify the appropriate method for handling repetition. This objective may include but is not limited to the following:
  • For loops
  • While loops
  • Do..While loops
  • Recursion
• Understand error handling. This objective may include but is not limited to the following:
  • Structured exception handling

• Understand the fundamentals of classes. This objective may include but is not limited to the following:
  • Properties
  • Methods
  • Events
  • Constructors
  • How to create a class
  • How to use classes in code
• Understand inheritance. This objective may include but is not limited to the following:
  • Inheriting the functionality of a base class into a derived class
• Understand polymorphism. This objective may include but is not limited to the following:
  • Extending the functionality in a class after inheriting from a base class
  • Overriding methods in the derived class
• Understand encapsulation. This objective may include but is not limited to the following:
  • Creating classes that hide their implementation details while still allowing access to the required functionality through the interface
  • Access modifiers

• Understand Web page development. This objective may include but is not limited to the following:
  • HTML
  • Cascading Style Sheets (CSS)
  • JavaScript
• Understand Microsoft ASP.NET Web application development. This objective may include but is not limited to:
  • Page life cycle
  • Event model
  • State management
  • Client-side vs. server-side programming
• Understand Web hosting. This objective may include but is not limited to the following:
  • Creating virtual directories and Web sites
  • Deploying Web applications
  • Understanding the role of Internet Information Services
• Understand Web services. This objective may include but is not limited to the following:
  • Web services that will be consumed by client applications
  • Accessing Web services from a client application
  • SOAP and Web Service Definition Language (WSDL)

Christmas waves a magic wand over this world, and behold, everything is softer and more beautiful. In celebration of this special season, we bring happy tidings. uCertify has a special treat for the foremost300 customers only!

Check out our low, low sale prices on over 300 IT certification exams. Sample Savings: Get any 6 Prepkits for only $56.67 each! That’s a savings of 60%! Or pick any 3 Prepkits for a savings of 40%! Remember, you only have to succeed the last time. Setting an example is not the main means of influencing others; it is the only means.

See https://www.ucertify.com/cart/selectadeal.php for details

Hurry! Sale begins NOW! At these Santa sized savings, be sure you are one of the first, lucky 300 customers!

Buy more and Save more!

We guarantee that you will pass your certification exam in first attempt or we will provide full refund. Checkout our 100% money back guarantee!

Click here to view uCertify Christmas Offer online

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

NOte: This is a guest Post by uCertify Team.

• Understand Windows Forms applications. This objective may include but is not limited to the following:
  • Windows Forms event model
  • Visual inheritance
  • UI design
  • Use of Multiple Document Interface (MDI)
  • Single Document Interface
  • SDI applications
• Understand console-based applications. This objective may include but is not limited to the following:
  • Characteristics and capabilities of console-based applications
• Understand Windows Services. This objective may include but is not limited to the following:
  • Characteristics and capabilities of Windows Services

• Understand relational database management systems. This objective may include but is not limited to the following:
  • Characteristics and capabilities of database products
  • Database design
  • Entity Relationship Diagrams (ERDs)
  • Normalization concepts
• Understand database query methods. This objective may include but is not limited to the following:
  • Structured query language (SQL)
  • Creating and accessing stored procedures
  • Updating data and selecting data
• Understand database connection methods. This objective may include but is not limited to the following:
  • Connecting to various types of data stores
  • XML file
  • In-memory object
  • Resource optimization

Hey! Cyber Monday, the Monday following the Thanksgiving holiday, begin the online holiday shopping time of year. If you are eager to achieve any plus in a competitive economy of IT Certification then ……….“May be you went out on Friday & tried it and if you still did not notice it, then make an effort back on Cyber Monday.”

Package Saving License 6 PrepKits Only $339.99 i.e. $56.67 each PrepKits 60% Home and Work Additional $34 Saving 5 PrepKits Only $309.99 i.e. $62 each PrepKits 56% Home and Work Additional $31 Saving 4 PrepKits Only $279.99 i.e. $70 each PrepKits 50% Home and Work Additional $28 Saving 3 PrepKits Only $249.99 i.e. $83.33 each PrepKits 40% Home and Work Additional $25 Saving 2 PrepKits Only $179.99 i.e. $90 each PrepKits 35% Home and Work Additional $18 Saving

Buy more and Save more!
60% off any 6 PrepKits
55% off any 5 PrepKits
50% off any 4 PrepKits
40% off any 3 Prepkits
35% off any 2 Prepkits

We guarantee that you will pass your certification exam in first attempt or we will provide full refund. Checkout our 100% money back guarantee!

Click here to view Cyber Monday Offer online

Happy Shopping & Happy Learning!

Each and every PrepKit come up with industry paramount Money back Guarantee. If you are unable to pass, we will return your money. Home and Work license permit you to install the PrepKit on two computers. Sale starts at the moment and ends on Cyber Monday, Nov 30th.

Black Friday might be the leading shopping day of the year, however, Cyber Monday, lashes out the online shopping period in anticipation of Christmas. If you did not desire to wake up at an impious hour to exchange blows with crazy deal hunters in the stores, you can still get excellent deals on the Internet.

For more Information visit: http://www.ucertify.com/

Follow uCertify Team on FaceBook: http://www.facebook.com/Certifications

Note: This is a guest post by uCertify Team

Enjoy PRE-THANKS GIVING OFFER, before the event that Americans commonly call the “First Thanksgiving” will be celebrated to give thanks to God for guiding them safely to the New World.

Buy 2 or more Prepkits and get 40% OFF

uCertify invites the first 100 customers to begin feasting early..!!

uCertify has some terrific treats for you this Thanksgiving! Turkey and mashed potatoes are not the only things up for gobbling this week. Check out these incredible savings!

This is one feast you won’t want to miss! The best part … you won’t regret feasting! You will pass in your first attempt or your money back. No questions asked. This is one gift you won’t need to return.

‘Tis the season to be jolly! So, celebrate the savings! Treat yourself to the gift of learning!

Join the feasting! Choose from over 400 test prep software for Microsoft, ITIL CompTIA, Oracle, IBM, Cisco, CCNA, & many more. Nobody beats our breadth and depth of experience. 100% guaranteed..!!!

For .NET Application developers, we have special offer too, visit .NET 4 Certifications.

Buy our PrepKits and Save upto 50%! And yes, get the online and mobile versions absolutely FREE!

http://learn.ucertify.com

Simply sign up or login with your existing account and add the Prepkit of your choice and and access it from anywhere. You can add your license information from this link

http://learn.ucertify.com/myprofile.php?func=mylicense

Click here now to Save : uCertify’s Pre-Thanksgiving Sale!

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Note: This is a guest post by uCertify Team.

The leaves are falling, pumpkins are all around, and the air smells crisp, it must be fall! We hope this page will help you make fall a learning time in your LYf. You will find ideas, links, e-books, fall printables, and more on uCertify Offer.  If you like a Preparation Kit that PrepKit of uCertify, click on it to buy N learn more. Now “fall” into uCertify Home!

This offer is available for the first 100 customers only. Be one of the first to buy any of our PrepKits and get the ONLINE version absolutely FREE! Access the PrepKit from any computer, your iPhone or iPad! How COOL is that?!

Ready for more WonderFALL savings?

Choose from over 300 test prep software for CompTIA, Microsoft, Oracle, IBM, Cisco, CCNA & many more. Nobody beats our breadth and depth of experience.

Buy our PrepKits and Save upto 50%! And yes, get the online and mobile versions absolutely FREE!

 
http://www.ucertify.me

Simply sign up or login with your existing account and add the Prepkit of your choice and and access it from anywhere. You can add your license information from this link

 
http://www.ucertify.me/myprofile.php?func=mylicense

iPhone and iPad users signup to http://learn.ucertify.com or login with your existing account and add the Prepkit of your choice and and access it from your iPhone and iPad. You can add your license information from this link

 
http://learn.ucertify.com/myprofile.php?func=mylicense

Click here now to Save : uCertify’s WonderFALL Sale!

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Note: This is a guest post by uCertify Team

In this tutorial, you build a matching game, where the player must match pairs of hidden icons. You learn how to:

• Hold objects using a List object.
• Use a foreach loop in Visual C# or a For Each loop in Visual Basic.
• Keep track of a form’s state using reference variables.
• Build an event handler that you can use with multiple objects.
• Make a timer fire exactly once when started.

When you finish, your program will look like the following picture.

Read More…

Main link: http://msdn.microsoft.com/en-us/library/dd553235.aspx

In this tutorial, you build a timed math quiz game, where the player must answer four random arithmetic problems within a specified time. You learn how to:

• Generate random numbers using the Random class.
• Trigger events using a Timer control.
• Control program flow using if else statements.
• Perform basic arithmetic operations.

When you finish, your program will look like the following picture.

Read More…

Main link: http://msdn.microsoft.com/en-us/library/dd492172.aspx

In this tutorial, you build a maze game, where the user has to move the mouse pointer from the start to the finish without touching any of the walls. You learn how to:

• Lay out a form using a Panel container.
• Build a maze using Label controls.
• Write code to show a message box.
• Set up event handlers for mouse events.
• Play sounds in your program.
• Organize your code using classes.

  Read More…

  Main Link: http://msdn.microsoft.com/en-us/library/dd492162.aspx

In this tutorial, you build a program that loads a picture from a file and displays it in a window. You learn how to drag controls like buttons and picture boxes on your form, set their properties, and use containers to smoothly resize the form. You also get started writing code. You learn how to:

• Create a new project.
• Test (debug) an application.
• Add basic controls like check boxes and buttons to a form.
• Position controls on a form using layouts.
• Add Open File and Color dialog boxes to a form.
• Write code using IntelliSense and code snippets.
• Write event handler methods.

When you finish, your program will look like the following picture. Read More…

Main Link: http://msdn.microsoft.com/en-us/library/dd492135.aspx

The following table shows whether certain features are supported in the listed versions of Visual Studio Professional.

• “Yes” means that the Visual Studio version includes the feature.
• “Add-in” means that the Visual Studio version does not include the feature, but it is available and you can get more information by clicking the link.
• “No” means that the Visual Studio version does not include the feature.

  Read More…

   

  Main Link: http://msdn.microsoft.com/en-us/library/ee519072.aspx

You may want to locate the product key for Visual Studio when you are working with customer support, upgrading from a trial version, or updating your own records. To find the product key for Team Foundation Server, follow the steps in Locate or Change the Product Key for Team Foundation Server. Read More…

Main Link: http://msdn.microsoft.com/en-us/library/gg442060.aspx

You can evaluate the Professional, Premium, Ultimate, and Test Professional editions of Visual Studio 2010 for up to 90 days. The evaluation period begins when you use the product for the first time. The length of the trial period depends on product registration. If you do not register the product, you can use it for 30 days; if you register it, you can use it for a total of 90 days.

You can register anytime within the first 30 days to obtain the remainder of the 90-day period. For example, if you download and use Visual Studio 2010 Premium for 10 days and then register it, you can use it for an additional 80 days. To continue to use the product after 90 days, you must provide a valid product key. For information about how to locate the product key, see How to: Locate the Visual Studio Product Key. Before you upgrade, we recommend that you review the Visual Studio 2010 and MSDN Licensing White Paperthat is available on the Microsoft Download Center website. Read More…

Main Link: http://msdn.microsoft.com/en-us/library/gg442061.aspx

Important Considerations About Multiple Language Installations

• When multiple language versions of a Visual Studio product are installed, the same features must be installed for every language version.
• Service packs must be applied to all installed versions of Visual Studio. For example, if an English version and a Japanese version are installed, you must install the service packs for both versions.

Read More…

Main Link: http://msdn.microsoft.com/en-us/library/ee230309.aspx

The Visual Studio 2010 Image Library contains application images that appear in Microsoft Windows, the Office system, Microsoft Visual Studio, and other Microsoft software. You can use this set of over 1,000 images to create applications that look visually consistent with Microsoft software.

The image library includes three main categories of images: animations, bitmaps, and icons. A readme file, *readme.htm, is included for each major area. These readme files include information about how to use these images appropriately in your applications.

The Visual Studio Image Library is installed on your computer together with Visual Studio. To access the files in the image library, you must extract them from VS2010ImageLibrary.zip. Read More…

Main Link: http://msdn.microsoft.com/en-us/library/ms246582.aspx

Visual Studio 2010 can be installed on a computer that already has an earlier version of Visual Studio. We recommend that you install Visual Studio versions in the order in which they were released. For example, install Visual Studio 2008 before you install Visual Studio 2010. Before you install versions side by side, review the following conditions:

• If you open in Visual Studio 2010 a solution from an earlier version and then save the solution, you can no longer open the solution in the earlier version.
• If you uninstall a version of Visual Studio on a computer that has more than one version installed, the file associations for Visual Studio will be removed for all versions. You can remap these file associations by using the Restore File Associations button on the Environment, General page of the Options dialog box.

  Read More…

  Main link: http://msdn.microsoft.com/en-us/library/ms246609.aspx

Visual Studio can be installed by using the installation media (for example, DVDs), or by downloading from the product website.

This document provides the following installation information:

• Installing Visual Studio
• Troubleshooting Installation Problems
• Enterprise Network Deployment
• After Visual Studio Is Installed
  • Registering Visual Studio
  • Repairing Visual Studio
  • Installing Optional Components
  • Checking for Service Releases and Product Updates
  • Uninstalling Visual Studio

• Related Topics

  Read More….

  Main link: http://msdn.microsoft.com/en-us/library/e2h7fzkw.aspx

The roots of education are bitter, but the fruit is sweet. It’s time to go back to school. It’s time to prepare the first Computer project of the new school year. As usual, uCertify offer IT certification Simulators to all teacher and students and even parents at this back to school season.

Do you have the right tools to get ahead this new school year? Earn more, do more, with an IT certification. Get certified – no issue if you are a fresh high school grad or in college or an IT professional. IT certifications help you stand out. Class shows. Let your credential do the talking.

For a limited time only, uCertify is offering a massive 50% discount!

Buy any two PrepKits for $169.99

(compare to about $119.99 for each PrepKit!). Choose from over 300 test Prep software for CompTIA, Microsoft, Oracle, IBM, Cisco, CCNA & many more. No one beats our wideness and deepness of experience.

uCertify – the fastest way to IT certification with the right tools and the right price. It’s quite simply, the right thing to do.

Hurry! Sale begins … .through ….. Only!

This is a guest post by:

uCertify Team

Hurry! Sale runs 8/17 through 8/25 only!

Click here now to Save : uCertify’s Back 2 School Sale! 

 Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

In this video Jesse Liberty demonstrates the List Template for Windows Phones and uses it to create a whimsical stock prediction application.

Jesse Liberty provides a fast introduction to Data Entity Modeling and WCF in Silverlgiht.

For more detail, visit here

In this video, Jesse Liberty demonstrates the power and utility of Expression Blend behaviors in Silverlight programming.

Behaviors are a breezy mode of adding functionality to XAML design elements in Expression Blend. The idea is that a number of rich functionality that would be hard for a designer to do can be wrapped in a way that can be used as a drag-and-drop feature to add that functionality to a XAML element in Expression Blend.

Launched today, the MTA will offer students a certification in the fundamentals of IT and development. Unlike more advanced Microsoft certifications, the MTA targets students with no prior IT or development experience or employment. It is available exclusively in educational settings and is designed to easily integrate into the curricula of existing computer classes… Read More….

Configuring and Deploying Web Applications

• Configure authentication and authorization.
  This objective may include but is not limited to: Forms Authentication, Windows Authentication; authorization; file authorization; impersonation
  This objective does not include: Windows Cardspace authentication, Passport (Windows Live ID) authentication, Custom authentication
• Configure projects, solutions, and reference assemblies.
  This objective may include but is not limited to: local assemblies, shared assemblies (GAC), Web application projects, solutions; configuration files; AppSettings
• Publish Web applications.

  This objective may include but is not limited to: choosing the appropriate method to deploy an application based on existing or intended environment; updatable vs. not updateable; MSI deployment; Internet Information Server (IIS) installation and configuration.

• Understand application pools.
  This objective may include but is not limited to: purpose of application pools; effect of application pools on Web applications
  Not: configuring or assigning application pools

Working with Client-Side Scripting

• Understand client-side scripting.
  This objective may include but is not limited to: purpose of client-side scripting, various client-side scripting languages
• Understand AJAX concepts.

  This objective may include but is not limited to: ASP.NET AJAX implementation, working with client-side libraries, EnablePartialRendering, Triggers, ChildrenAsTriggers, Scripts, Services, UpdateProgress, Timer, ScriptManagerProxy, extender controls

Troubleshooting and Debugging Web Applications

• Debug a Web application.
  This objective may include but is not limited to: Use in conjunction with custom error pages to display appropriate error information to the appropriate user; implement tracing of a Web application, Trace.axd, Trace=True on @Page directive,
• Handle Web application errors

  This objective may include but is not limited to: HTTP error codes

Working with Data and Services

• Read and write XML data.
  This objective may include but is not limited to: Understanding XML, XML validation
  This objective does not include: Web Services, XPath syntax, XmlDocument, XPathNavigator, XPathNodeIterator, XPathDocument, XmlReader, XmlWriter, XmlDataDocument, XmlNamespaceManager
• Distinguish between DataSet and DataReader objects.

  This objective may include but is not limited to: the ability to choose the proper data object to use based on application requirements/design

• Call a service from a Web page.

  This objective may include but is not limited to: creating a basic WCF Service or Web Service so that it can be consumed; App_WebReferences;  configuration

• Understand DataSource controls.
  This objective may include but is not limited to: LinqDataSource, ObjectDataSource, XmlDataSource, SqlDataSource
• Bind controls to data by using data binding syntax.

  This objective may include but is not limited to: ensure that data is updated and displayed in data-aware controls

• Manage data connections and databases.

  This objective may include but is not limited to: database connections; connection objects; connection pools; transaction objects;

Programming  Web Applications

• Customize the layout and appearance of a Web page.
  This objective may include but is not limited to: CSS,  tables, embedding images, page layout for navigation
• Understand ASP.NET intrinsic objects.
  This objective may include but is not limited to: Request, Server, Application, Session, Response, HttpContext
• Understand state information in Web applications.
  This objective may include but is not limited to: understand how state is stored based on application design and hardware; understand different types such as session state, view state, control state, and application state
• Understand events and control page flow.
  This objective may include but is not limited to: application and page life cycle events; page events; control events; application events; and session events; cross-page posting; Response.Redirect; Server.Transfer; IsPostBack; setting AutoEventWireup
• Understand controls.
  This objective may include but is not limited to: understanding various types of controls, including  user, server, Web, and validation controls; know which is the appropriate type of control for a scenario
• Understand configuration files.
  This objective may include but is not limited to: Understanding the usage of web.config and machine.config, and the settings that can be made

This exam is designed to allow candidates to assess their knowledge and skills around Web applications using Microsoft and other technologies.

• Understand the System Security namespace.
  • This objective may include but is not limited to: understanding permissions and what cryptography is
• Understand authentication and authorization.
  • This objective may include but is not limited to: understanding code access security, access control, and policies

• Understand the fundamentals of Microsoft Intermediate Language (MSIL) and Common Language Infrastructure (CLI).
  • This objective may include but is not limited to: understanding what MSIL is, what the CLI is, how source code is compiled into MSIL, and how code is Just-in-Time (JIT) compiled
• Understand the use of strong naming.
  • This objective may include but is not limited to: understanding why strong naming is used, how to sign assemblies to support strong naming, and Global Assembly Cache (GAC)
• Understand version control.
  • This objective may include but is not limited to: understanding how .NET applications are versioned and how to run different versions on the same computer
• Understand assemblies and metadata.
  • This objective may include but is not limited to: understanding .NET assemblies, shared assemblies, and metadata in .NET

Understanding I/O Classes in the .NET Framework
Understand .NET file classes.
This objective may include but is not limited to: understanding read/write file classes and stream readers and writers
Understand console I/O.
This objective may include but is not limited to: understanding System.Console classes for input and output
Understand XML classes in the .NET Framework.
This objective may include but is not limited to: understanding XMLReader, XMLWriter, and XML Schemas

• Understand .NET class hierarchies.
  • This objective may include but is not limited to: understanding system classes, classifications of classes, and logical organization of classes
• Understand Object Oriented Concepts in the .NET Framework.
  • This objective may include but is not limited to: understanding how inheritance works in .NET, polymorphism, and interfaces
• Understand .NET namespaces.
  • This objective may include but is not limited to: understanding the reason for namespaces, the organization of namespaces in the class library, and how to use namespaces in an application
• Understand and create class libraries.
  • This objective may include but is not limited to: understanding the logical grouping of classes and the logic behind class libraries (what they are, why they are important)
• Understand and use different data types in the .NET Framework.
  • This objective may include but is not limited to: understanding intrinsic data types, values types, reference types, boxing, unboxing, and .NET collection classes
• Understand generics.
  • This objective may include but is not limited to: understanding generics infrastructure, generic interfaces, generic delegates, contravariant and covariant generic type arguments, generic methods, verifiability, and constraints

98-372: Microsoft .NET Fundamentals Exam

SAVE UPTO 50%

The month of July means Freedom to millions of people around the world. Sure, may people know about Bastille day in France or the 4th of July in America. But did you know that twenty, that’s right, 20 other countries celebrate their independence in July?

At uCertify, we know how special freedom is. No matter who or where, independence and the freedom to choose is very important to all of us. In celebration of this spirit, uCertify is proud to announce our annual Freedom Sale!

uCertify is offering an amazing discount of upto 50%! Check out the offer!

Choose from over 300 exams, covering all major certification vendors. Second, if, for any reason you are not satisfied with your purchase, simply let us know within 7 days of your order, and we will return your money. How cool is that?! This super guarantee is in addition to our unbeatable 1 year guarantee.

So, what are you waiting for? Hurry! The Freedom offer is valid June 29 – July 6, 2011only.

Click here now to Save : uCertify’s FREEDOM Sale!

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Note: This is a guest post by uCertify Team

Microsoft makes every effort to ensure that certifications are relevant, respected, and highly valued within the IT community and that they without bias confirm the expertise of technology practitioners. Earning a Microsoft Certification helps show an individual’s understanding of the latest IT developments and mastery of skills in a particular technology. Microsoft Certifications command immense esteem in the industry, thanks in part to the thorough process used to develop the exams. Launch your journey to a more successful IT career today.

.NET Exams retiring on June 30, 2011

• Design for error handling.
  This objective may include but is not limited to: collecting user feedback when errors occur, handling exceptions across tiers
  This objective does not include: try/catch blocks
• Evaluate and recommend a test strategy.
  This objective may include but is not limited to: recommending functional testing, recommending reliability testing (performance testing, stress testing, scalability testing, duration testing)
  This objective does not include: unit testing
• Design a diagnostics and monitoring strategy.
  This objective may include but is not limited to: profiling, tracing, performance counters, audit trails (events and information); usage reporting; deciding where to log events (local vs.centralized reporting)

• Define a client deployment strategy.
  This objective may include but is not limited to: recommending an installation method (Xcopy, ClickOnce, MSI, third party); identifying prerequisites (target framework and bootstrap requirements), deploying COM components
• Plan a database deployment.
  This objective may include but is not limited to: existing or shared instance; remote server; embedded database; deploying new objects (such as tables, stored procedures, and views) to a new or existing database; recognizing database security concerns (such as shared instances and access); remote vs. local database
  This objective does not include: DLL deployment; shared GAC deployment
• Design a solution update strategy.
  This objective may include but is not limited to: preserving shared components, data integrity, and user customizations; designing an update delivery method (e.g., automated update detection from the client), version mismatch (both local binaries and service interfaces)
• Plan for n-tier deployment.
  This objective may include but is not limited to: mapping the solution to the topology (required hardware such as servers, routers, and RAM and required software such as OS); determining component installation order; reviewing security requirements

• Choose the appropriate data access strategy.
  This objective may include but is not limited to:  choosing the appropriate data access technology (Entity Framework, LINQ to SQL, Microsoft ADO.NET); supporting data sources such as XML data, flat files, and relational databases
• Design data caching.
  This objective may include but is not limited to: managing data cache (lifetime, targets, size, scope), managing data state (change notification, cache invalidation/synchronization)
• Design for a concurrent multi-user environment.
  This objective may include but is not limited to: planning for concurrency and collision avoidance, optimistic vs. pessimistic locking, cross-tier distributed transactions

• Choose the appropriate Windows Client technology.
  This objective may include but is not limited to: choosing between Windows Forms, WPF, or a combination; choosing an appropriate presentation pattern (Model View Presenter [MVP], Model View/View Model [MV-VM]); identifying areas for possible migration/interoperability from Windows Forms to WPF
• Design application workflow.
  This objective may include but is not limited to: user navigation, designing wizards, modal vs. non-modal; dependencies among UI elements; designing for input types based on environment and audience (kiosk, very large display, small display, indoors and outdoors)
• Design data presentation and input.
  This objective may include but is not limited to: designing data validation; designing a data-binding strategy; designing a reporting strategy; choosing media services (audio, video, images, animation); managing data shared between forms

• Design a loosely coupled layered architecture.
  This objective may include but is not limited to: separation of concerns including presentation, business logic, and data; minimizing logical dependencies; deciding how layers connect (e.g., content-based vs. context-based filtered routing)
• Design service interaction.
  This objective may include but is not limited to: service granularity (cohesiveness); interface granularity (responsibilities of an operation), versioning, data and service contracts (using a message contract rather than a data contract); hosting and protocol; managing data integrity (re-validating data across trust boundaries); evaluating use of RESTful interface (URI/resource structure); choosing a message exchange pattern; choosing synchronous vs. asynchronous operation invocation; deciding whether to use custom SOAP headers
  This objective does not include: interacting with existing/external systems
• Design the security implementation.
  This objective may include but is not limited to: protecting data during transmission (encryption/hashing algorithm), authentication (client/proxy credential) and authorization (groups, built-in or custom role provider, claims, federated security), designing for least privilege (impersonation and/or delegation), planning for User Access Control (UAC) environments; auditing
• Design for globalization and localization.
  This objective may include but is not limited to: multi-locale services; designing for time zone, sorting, UI considerations; database design considerations

• Monitor and collect performance data.
  This objective may include but is not limited to: logging generated SQL (ToTraceString), collecting response times, implementing performance counters, implementing logging, implementing instrumentation
• Handle exceptions.
  This objective may include but is not limited to: resolving data concurrency issues (handling OptimisticConcurrency exception, Refresh method), handling errors, transaction exceptions, connection exceptions, timeout exceptions, handling an exception from the Entity Framework disconnected object, security exceptions
• Protect data.
  This objective may include but is not limited to: encryption, digital signature, hashing, salting, least privilege
• Synchronize data.
  This objective may include but is not limited to: online/offline Entity Framework, synchronization services, saving locally

• Create, update, or delete data by using SQL statements.
  This objective may include but is not limited to: Create/Update/Delete (CUD), using DataSets, calling stored procedures, using parameters
• Create, update, or delete data by using DataContext.
  This objective may include but is not limited to: CUD, calling stored procedures, using parameters
  This objective does not include: ObjectTrackingEnabled
• Create, update, or delete data by using ObjectContext.
  This objective may include but is not limited to: CUD, calling stored procedures, using parameters, setting SaveOptions

• Execute a SQL query.
  This objective may include but is not limited to: DBCommand, DataReader, DataAdapters, DataSets, managing data retrieval by using stored procedures, using parameters, System.Data.Common namespace classes
• Create a LINQ query.
  This objective may include but is not limited to: syntax-based and method-based queries, joining, filtering, sorting, grouping, aggregation, lambda expressions, paging, projection
  This objective does not include: compiling queries
• Query data by using ADO.NET Data Services.
  This objective may include but is not limited to: implementing filtering and entitlement in ADO.NET Data Services, addressing resources, creating a query expression, accessing payload formats, Data Services interceptors

• Create and manage a data connection.
  This objective may include but is not limited to: connecting to a data source, closing connections, maintaining the life cycle of a connection
• Configure ADO.NET Data Services.
  This objective may include but is not limited to: creating access rules for entities, configuring authorization and authentication, configuring HTTP verbs

• Map entities and relationships by using the Entity Data Model.
  This objective may include but is not limited to: using the Visual Designer, building an entity data model from an existing database, managing complex entity mappings in EDMX, editing EDM XML, mapping to stored procedures, creating user-defined associations between entities, generating classes with inheritance and mapping them to tables
  This objective does not include: using MetadataWorkspace
• Create and customize entity objects.
  This objective may include but is not limited to: configuring changes to an Entity Framework entity, using the ADO.NET EntityObject Generator (T4), extending, self-tracking entities, snapshot change tracking, ObjectStateManager, partial classes, partial methods in the Entity Framework

• Configure message logging.
  This objective may include but is not limited to: configuring message listeners; logging level; message filters; configuring logging known PII
  This objective does not include: secure message logs
• Configure diagnostics.
  This objective may include but is not limited to: WMI; performance counters; event logging

• Manage sessions.
  This objective may include but is not limited to: code and configuration; session management attributes; throttling; reliable sessions; transport-level and application-level sessions; invoking a callback contract
• Manage concurrency.
  This objective may include but is not limited to: single, multiple, and reentrant concurrency modes; SynchronizationContext and CallbackBehavior
  This objective does not include: deadlocks and other multithreading issues

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

• Configure secure Bindings.
  This objective may include but is not limited to: transport, message, mixed mode
• Configure message security.
  This objective may include but is not limited to: specifying protection levels on different message parts

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

• Create a service proxy.
  This objective may include but is not limited to: using a proxy class or channel factory to create a proxy; creating a proxy for an asynchronous communication; creating a proxy for a duplex communication
  This objective does not include: SvcUtil command-line switches
• Consume RESTful services
  This objective may include but is not limited to: access HTTP context; JSON/POX

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Hosting and Configuring Services

• Create and configure endpoints. This objective may include but is not limited to the following:
  • Default and standard bindings
  • Custom bindings created from standard binding elements;
  • Standard endpoints
  • Transports including HTTP, TCP, named pipes, UDP, MSMQ code-based service configuration
  • Message encoding

This objective does not include the following:

• Creating a custom binding element;
• Creating new standard endpoints,
• Loading configuration from a location other than the default application configuration file, security, transaction, reliable sessions

• Configure Behaviors. This objective may include but is not limited to the following:
  • Applying service, endpoint, and operation behaviors in configuration and code

This objective does not include the following:

• Creating a custom behavior
• Creating and using dispatch behaviors
• Loading configuration from a location other than the default application configuration file

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Creating Services

• Create service and operation contracts. This objective may include but is not limited to the following:
  • One-way, duplex, and request reply;
  • Creating and specifying  fault contracts;
  • Configuration-based contracts;
  • Exposing service metadata;
  • Selecting serialization (e.g., data contract serializer vs. XML serializer)

This objective does not include designing service and operation contracts; transactions, instantiation, security-related attributes

• Create data contracts. This objective may include but is not limited to the following:
  • Managing Known Types;
  • Controlling data serialization;
  • Using required and order attributes on data members;
  • Implementing versioning using IExtensibleDataObject;
  • POCOs

This objective does not include using custom serializer (ISerializationSurrogate)

• Implement RESTful services. This objective may include but is not limited to the following:
  • Accessing HTTP context
  • WebGet/WebInvoke
  • UriTemplates
  • JSON/POX

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Stabilizing and Releasing a Solution

• Implement a WPF test strategy. This objective may include but is not limited to the following:
  • Automation peer
  • UI automation
  • IntelliTrace
• Debug XAML by using the WPF Visualizer. This objective may include but is not limited to the following:
  • Accessing the Visualizer
  • Drilling down into the visual tree
  • Viewing and changing properties

This objective does not include setting a breakpoint and stepping through code

• Create and configure a Windows Installer project. This objective may include but is not limited to the following:
  • Configuring a setup project to add icons during setup
  • Setting deployment project properties
  • Configuring conditional installation based on operating system versions
  • Setting appropriate Launch Conditions based on the .NET Framework version
  • Adding custom actions to a setup project
  • Adding error-handling code to a setup project
• Configure deployment security settings. This objective may include but is not limited to the following:
  • Configuring and integrating UAC by using ClickOnce deployments
  • Setting appropriate security permissions to deploy the application

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Enhancing the Functionality and Usability of a Solution

• Implement asynchronous processes and threading. This objective may include but is not limited to the following:
  • Implementing asynchronous programming patterns
  • Marshalling between threads
  • Freezing UI elements
  • Using timers
  • Task Parallel Library
  • Parallel LINQ
  • Using the dispatcher
  • BackgroundWorker component
• Implement security features of an application. This objective may include but is not limited to the following:
  • Configuring Software Restriction Policy (SRP)
  • Full trust and partially trusted security
  • Interoperability with legacy CAS policy
  • User Account Control (UAC)
• Manage user and application settings. This objective may include but is not limited to the following:
  • Creating application settings
  • Creating user settings
  • Loading and saving settings

This objective does not include persisting to database

• Implement dependency properties. This objective may include but is not limited to the following:
  • Enabling data binding and animation
  • Property metadata
  • Property change callbacks

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Managing Data at the User Interface Layer

• Implement data binding. This objective may include but is not limited to the following:
  • Binding options, static and dynamic resources, element bindings, setting the correct binding mode and update mode
  • Binding to nullable values

This objective does not include binding to a specific data source

• Implement data validation. This objective may include but is not limited to the following:
  • Handling validation and providing user feedback via the error provider (WinForms) or data templates (WPF), IDataErrorInfo, validation control, form validation and control validation
• Prepare collections of data for display. This objective may include but is not limited to the following:
  • Filtering, sorting, and grouping data
  • LINQ
  • CollectionView (WPF), BindingSource object (WinForms)
• Implement data-bound controls. This objective may include but is not limited to the following:
  • Using the DataGridView (WinForms) or DataGrid (WPF) control to display and update the data contained in a data source
  • Implementing complex data binding to integrate data from multiple sources
  • ItemsControl-derived controls (WPF)

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

Enhancing a User Interface by Using Advanced Techniques

• Manage routed events in WPF. This objective may include but is not limited to the following:
  • Tunneling vs. bubbling events
  • Handling and cancelling events

This objective does not include simple event handling and creating custom events

• Configure WPF commanding. This objective may include but is not limited to the following:
  • Defining WPF commands based on RoutedCommand
  • Associating commands to controls
  • Handling commands
  • Ccommand bindings
  • Input gestures

This objective does not include creating custom commands by implementing ICommand

• Implement user-defined controls. This objective may include but is not limited to the following:
  • Deciding whether to use a user/composite, extended, or custom control
  • Creating a user/composite control
  • Extending from an existing control

This objective does not include creating a custom control by inheriting directly from the Control class and writing code

Upgrade: Transition your MCPD .NET Framework 3.5 Windows Developer Skills to MCPD .NET 4 Windows Applications Developer

• Choose the most appropriate control class. This objective may include but is not limited to the following:
  • Evaluating design requirements and then selecting the most appropriate control based on those requirements
  • Recognizing when none of the standard controls meet requirements
    Item controls, menu controls, and content controls
  This objective does not include designing a custom control
• Implement screen layout by using nested control hierarchies. This objective may include but is not limited to the folloiwng:
  • Using panel-derived controls
  • Attaching properties
  This objective does not include items controls and control customization.

Everybody’s Irish on St. Patrick’s Day! Spring is in the air, so why not take time to explore the Huge Offers by uCertify.

Any 3 Prepkits for $219.99

That’s just $73.33 per PrepKit

Hurry! First 300 Customers Only!

Get lucky this St. Patrick’s day! Maybe you’ll find a four leaved clover, a pot of gold, or even better, lots of green! Lots of green savings, that is! This week, Mar 17 -Mar 21, save BIG on any 3 uCertify Prepkit.

HURRY! Sale ends Mar 21st Any 3 Prepkits for $219.99!
Choose from over 300 IT certification prepkits, each backed by our 100% money back guarantee.

Note: This is a guest post by uCertify Inc.

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

HURRY! 5 DAYS ONLY (Feb 21- Feb 25)

In honor of the birth anniversaries of two great men, George Washington and Abraham Lincoln, uCertify is pleased to offer fantastic savings on President’s Day!

Monday Feb 21 – Friday Feb 25th, 2011 ONLY, all IT certification Prepkits are only $95.99! or less

HURRY! 5 DAYS ONLY!

Choose from over hundreds of IT certification prepkits, each backed with our 100% money back guarantee.

So, hurry! Sale begins Feb 21st and ends Feb 25th. ANY Prepkit, ONLY $95.99! or less

This is a guest post by uCertify team

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Designing a Deployment Strategy (14%)

• Design a deployment process.

This objective may include but is not limited to: Windows Installer (MSI) vs. xcopy vs. Web Deployment Tool, scaling, rolling deployments

• Design configuration management.

This objective may include but is not limited to: using the ConfigSource attribute (for example, connection strings), staging vs. production vs. development, topologies, machine.config vs. web.config, using IIS vs. Visual Studio Development Server during development, application pools, configuration inheritance

• Plan for scalability and reliability.

This objective may include but is not limited to: scaling up, scaling out, at physical level and at architectural level, impact of offloading technologies on load balancing, including state, synchronizing machine and encryption keys

• Design a health monitoring strategy.

This objective may include but is not limited to: when to monitor application or business-related events (e.g., on UI every time clicked or in business layer), determining a strategy for using ASP.NET Health Monitoring, throttling, filtering, delivery method

to watch or create (including performance counters and event tracing) to analyze performance issues, page and fragment caching

• Understand application life cycle management. This objective may include but is not limited to the following:
  • Phases of application life cycle management
  • Software testing
• Interpret application specifications. This objective may include but is not limited to the following:
  • Reading application specifications and translating them into prototypes
  • Code
  • Components
• Understand algorithms and data structures. This objective may include but is not limited to the following:
  • Arrays
  • Stacks
  • Queues
  • Linked lists, and
  • Sorting algorithms
  • Performance implications of various data structures
  • Choosing the right data structure

Preparing For and Investigating Application Issues (15%)

• Choose a testing methodology.

This objective may include but is not limited to: black box, white box, integration, regression, coverage, API testing, performance testing, security testing

This objective does not include: load testing, Web testing, unit testing

• Design an exception handling strategy.

This objective may include but is not limited to: HandleError attribute in MVC, common error pages, post-error processing, global vs. page level

• Recommend an approach to debugging.

This objective may include but is not limited to: tools and approaches for a given scenario (for example, memory dumps, DebuggingAttributes, crashes vs. hangs, deadlocks, assembly binding), when to attach to process (Visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analysis

This objective does not include: basic breakpoints

• Recommend an approach to performance issues.

This objective may include but is not limited to: which instrumentation to watch or create (including performance counters and event tracing) to analyze performance issues, page and fragment caching

Designing Security Architecture and Implementation (17%)

• Plan for operational security.

This objective may include but is not limited to: approaches for process- and resource-level security, including local and remote resources, Code Access Security (CAS), including trust level, process identity, application pool, and identity tag

• Design an authentication and authorization model.

This objective may include but is not limited to: authentication providers, including WindowsForms, and custom user identity flowthrough (for example, trusted subsystem), role management, membership providers, URL authorization (for example, AuthorizationAttribute), file authorization, Authorization Manager (AzMan)

• Plan for minimizing attack surfaces.

This objective may include but is not limited to: input validation, throttling inputs, request filtering, where to use Secure Sockets Layer (SSL)

Designing Data Strategies and Structures (18%)

• Design data access.

This objective may include but is not limited to: choosing data access technologies such as ADO.NETData Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services

• Design data presentation and interaction.

This objective may include but is not limited to: pulling data from data layer and binding into views, pages, and controls, and pulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically

• Plan for data validation.

This objective may include but is not limited to: contextual validation vs. data integrity, where to validate data, synchronization between UI and data layer, data annotations

Designing Data Strategies and Structures (18%)

• Design data access.

This objective may include but is not limited to: choosing data access technologies such as ADO.NETData Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services

• Design data presentation and interaction.

This objective may include but is not limited to: pulling data from data layer and binding into views, pages, and controls, and pulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically

• Plan for data validation.

This objective may include but is not limited to: contextual validation vs. data integrity, where to validate data, synchronization between UI and data layer, data annotations

Designing the User Experience (17%)

• Design the site structure.

This objective may include but is not limited to: designing application segmentation for manageability and security (for example, using areas, shared views, master pages, and nested master pages), appropriate use of style sheets, client-side scripting, themes, client ID generation, rendering element modes, routing engine

• Plan for cross-browser and/or form factors.

This objective may include but is not limited to: evaluating the impact on client side behaviors, themes, bandwidth, style sheets (including application design – task based or scaled rendering of existing page), when to apply Browsers file, structural approaches, user agents, different platforms (mobile vs. desktop)

• Plan for globalization.

This objective may include but is not limited to: designing to support local, regional, language, or cultural preferences, including UI vs. data localization (for example, implementing at database level or resource level), when to use CurrentCulture vs. CurrentUICulture, globalization rollout plan (for example, setting base default language, planning localization), handling Unicode data (for example, what fields to include, request encoding), right-to-left support, vertical text and non-Latin topographies, calendars, data formatting, sorting

Designing the Application Architecture (19%)

• Plan the division of application logic.

  This objective may include but is not limited to: choosing between client-side and server side processing, planning separation of concern, (for example, partitioning functionality between controllers and evaluating business and data service consumption), planning for long-running processes (for example, synchronous vs. asynchronous)

• Analyze requirements and recommend a system topology.
  This objective may include but is not limited to: designing interaction between applications, mapping logical design to physical implementation, validating nonfunctional requirements and cross-cutting concerns (for example, communications, operations management, and security), evaluating baseline needs (for example, scale and quality of service)
• Choose appropriate client-side technologies.
  This objective may include but is not limited to: JavaScript, ASP.NET AJAX, jQuery, Microsoft Silverlight
• Choose appropriate server-side technologies.
  This objective may include but is not limited to: user controls, server controls, partials, custom HtmlHelper extensions, Web parts, inheriting controls, dynamic data controls
• Design state management.
  This objective may include but is not limited to: designing an application for the proper use of application state, session state, and request state (for example, ViewState, ControlState, Cache object, cookies, and client-side persistence)

Save 36%

It seems like only yesterday that we welcomed in 2011, but as you may have noticed, it is already the end of January! Have you begun on your New Year’s resolutions to get your career goals in order? Getting certified is a great way to expand your skills prove your abilities to your employer.

uCertify has helped thousands of professionals achieve their IT certification goals. This week, we are making it easy on your check book. For 3 days only, order any 2 Prepkits of your choice for only $179.99. That’s a 36% savings off our regular prices.

This is guest post by uCertify team

Designing for Stability and Maintenance (19%)

• Design for error handling.

This objective may include but is not limited to: collecting user feedback when errors occur, handling exceptions across tiers

This objective does not include: try/catch blocks

• Evaluate and recommend a test strategy.

This objective may include but is not limited to: recommending functional testing, recommending reliability testing (performance testing, stress testing, scalability testing, duration testing)

This objective does not include: unit testing

• Design a diagnostics and monitoring strategy.

This objective may include but is not limited to: profiling, tracing, performance counters, audit trails (events and information); usage reporting; deciding where to log events (local vs. centralized reporting)

Planning a Solution Deployment (17%)

• Define a client deployment strategy.

This objective may include but is not limited to: recommending an installation method (Xcopy, ClickOnce, MSI, third party); identifying prerequisites (target framework and bootstrap requirements), deploying COM components

• Plan a database deployment.

This objective may include but is not limited to: existing or shared instance; remote server; embedded database; deploying new objects (such as tables, stored procedures, and views) to a new or existing database; recognizing database security concerns (such as shared instances and access); remote vs. local database

This objective does not include: DLL deployment; shared GAC deployment

• Design a solution update strategy.

This objective may include but is not limited to: preserving shared components, data integrity, and user customizations; designing an update delivery method (e.g., automated update detection from the client), version mismatch (both local binaries and service interfaces)

• Plan for n-tier deployment.

This objective may include but is not limited to: mapping the solution to the topology (required hardware such as servers, routers, and RAM and required software such as OS); determining component installation order; reviewing security requirements

Implementing Client-Side Scripting and AJAX (16%)

• Add dynamic features to a page by using JavaScript.
  This objective may include but is not limited to: referencing c
  lient ID; Script Manager; Script combining; Page.clientscript.registerclientscriptblock; Page.clientscript.registerclientscriptinclude; sys.require (scriptloader)
  This objective does not include: interacting with the server; referencing JavaScript files; inlining JavaScript
• Alter a page dynamically by manipulating the DOM.This objective may include but is not limited to: using jQuery, adding, modifying, or removing page elements, adding effects, jQuery selectors

  This objective does not include: AJAX

• Handle JavaScript events.
  This objective may include but is not limited to: DOM events, custom events, handling events by using jQuery
• Implement ASP.NET AJAX.This objective may include but is not limited to: client-side templating, creating a script service, extenders (ASP.NET AJAX Control Toolkit), interacting with the server, Microsoft AJAX Client Library, custom extenders; multiple update panels; triggers; UpdatePanel.UpdateMode; Timer

  This objective does not include: basic update panel and progress

• Implement AJAX by using jQuery.This objective may include but is not limited to: $.get, $.post, $.getJSON, $.ajax, xml, html, JavaScript Object Notation (JSON), handling return types

  This objective does not include: creating a service

Designing the Data Access Layer (21%)

• Choose the appropriate data access strategy.

This objective may include but is not limited to:  choosing the appropriate data access technology (Entity Framework, LINQ to SQL, Microsoft ADO.NET); supporting data sources such as XML data, flat files, and relational databases

• Design the data object model.

This objective may include but is not limited to: mapping to persistent storage (mapping to tables, XML files), abstracting from the service layer (encapsulating underlying schema details); designing a schema change management strategy

• Design data caching.

This objective may include but is not limited to: managing data cache (lifetime, targets, size, scope), managing data state (change notification, cache invalidation/synchronization)

• Design offline storage and data synchronization.

This objective may include but is not limited to: managing offline data, mapping a data store to local cache, designing synchronization; analyzing target data environment (e.g., Microsoft SQL Server, SQL Express, workstation capabilities, OS, bandwidth, reliability)

• Design for a concurrent multi-user environment.

This objective may include but is not limited to: planning for concurrency and collision avoidance, optimistic vs. pessimistic locking, cross-tier distributed transactions

• Analyze data services for optimization.

This objective may include but is not limited to: object relational mapping (ORM) performance, optimizing roundtrips, lazy vs. eager loading, caching of frequently used data

Designing the Presentation Layer (21%)

• Choose the appropriate Windows Client technology.

This objective may include but is not limited to: choosing between Windows Forms, WPF, or a combination; choosing an appropriate presentation pattern (Model View Presenter [MVP], Model View/View Model [MV-VM]); identifying areas for possible migration/interoperability from Windows Forms to WPF

• Design the UI layout and structure.

This objective may include but is not limited to: evaluating the conceptual design, deciding how the UI will be composed (e.g., static vs. dynamic screen); designing for the inheritance and re-use of visual elements (e.g., styles, resources); accessibility considerations; deciding when custom controls are needed

• Design application workflow.

This objective may include but is not limited to: user navigation, designing wizards, modal vs. non-modal; dependencies among UI elements; designing for input types based on environment and audience (kiosk, very large display, small display, indoors and outdoors)

• Design data presentation and input.

This objective may include but is not limited to: designing data validation; designing a data-binding strategy; designing a reporting strategy; choosing media services (audio, video, images, animation); managing data shared between forms

• Design presentation behavior.

This objective may include but is not limited to:  determining which behaviors will be implemented and how; drag and drop functionality

• Design for UI responsiveness.

This objective may include but is not limited to: offloading operations from UI thread and reporting of progress, avoiding unnecessary screen refresh; media buffering; client vs. server side sorting and filtering of data; addressing UI memory issues

Designing the Layers of a Solution (22%)

• Design a loosely coupled layered architecture.

This objective may include but is not limited to: separation of concerns including presentation, business logic, and data; minimizing logical dependencies; deciding how layers connect (e.g., content-based vs. context-based filtered routing)

• Design service interaction.

This objective may include but is not limited to: service granularity (cohesiveness); interface granularity (responsibilities of an operation), versioning, data and service contracts (using a message contract rather than a data contract); hosting and protocol; managing data integrity (re-validating data across trust boundaries); evaluating use of RESTful interface (URI/resource structure); choosing a message exchange pattern; choosing synchronous vs. asynchronous operation invocation; deciding whether to use custom SOAP headers

This objective does not include: interacting with existing/external systems

• Design the security implementation.

This objective may include but is not limited to: protecting data during transmission (encryption/hashing algorithm), authentication (client/proxy credential) and authorization (groups, built-in or custom role provider, claims, federated security), designing for least privilege (impersonation and/or delegation), planning for User Access Control (UAC) environments; auditing

• Design for interoperability with external systems.

This objective may include but is not limited to: choosing an appropriate strategy for communicating with COM components, mainframe services, and Web services

• Design for optimal processing.

This objective may include but is not limited to: parallel processing; asynchronous processing; service bus; gateway processes; scalability (scale out vs. scale up); designing tiers to minimize latency (batch retrieval, multiple small calls)

• Design for globalization and localization.

This objective may include but is not limited to: multi-locale services; designing for time zone, sorting, UI considerations; database design considerations

Developing and Deploying Reliable Applications (18%)

• Monitor and collect performance data.

This objective may include but is not limited to: logging generated SQL (ToTraceString), collecting response times, implementing performance counters, implementing logging, implementing instrumentation

• Handle exceptions.

This objective may include but is not limited to: resolving data concurrency issues (handling OptimisticConcurrency exception, Refresh method), handling errors, transaction exceptions, connection exceptions, timeout exceptions, handling an exception from the Entity Framework disconnected object, security exceptions

• Protect data.

This objective may include but is not limited to: encryption, digital signature, hashing, salting, least privilege

• Synchronize data.

This objective may include but is not limited to: online/offline Entity Framework, synchronization services, saving locally

• Deploy ADO.NET components.

This objective may include but is not limited to: packaging and publishing from Visual Studio, deploying an ADO.NET Services application; packaging and deploying Entity Framework metadata
This objective does not include: configuring IIS, MSDeploy, MSBuild

Manipulating Data (22%)

• Create, update, or delete data by using SQL statements.

This objective may include but is not limited to: Create/Update/Delete (CUD), using DataSets, calling stored procedures, using parameters

• Create, update, or delete data by using DataContext.This objective may include but is not limited to: CUD, calling stored procedures, using parameters

  This objective does not include: ObjectTrackingEnabled

• Create, update, or delete data by using ObjectContext.

This objective may include but is not limited to: CUD, calling stored procedures, using parameters, setting SaveOptions

• Manage transactions.This objective may include
  but is not limited to: System.Transactions, DBTransaction, rolling back a transaction, Lightweight Transaction Manager (LTM)

This objective does not include: distributed transactions, multiple updates within a transaction, multiple synchronization of data within an acidic transaction

• Create disconnected objects.

This objective may include but is not limited to: creating self-tracking entities in the Entity Framework, attaching objects, DataSets, table adapters

Querying Data (22%)

• Execute a SQL query.

This objective may include but is not limited to: DBCommand, DataReader, DataAdapters, DataSets, managing data retrieval by using stored procedures, using parameters, System.Data.Common namespace classes

• Create a LINQ query.

  This objective may include but is not limited to: syntax-based and method-based queries, joining, filtering, sorting, grouping, aggregation, lambda expressions, paging, projection

  This objective does not include: compiling queries

• Create an Entity SQL (ESQL) query.

This objective may include but is not limited to: joining, filtering, sorting, grouping, aggregation, paging, using functions, query plan caching, returning a reference to an entity instance, using parameters with ESQL, functionality related to EntityClient classes

• Handle special data types.

  This objective may include but is not limited to: querying BLOBs, filestream, spatial and table-valued parameters

  This objective does not include: implementing data types for unstructured data, user-defined types, Common Language Runtime (CLR) types

• Query XML.

  This objective may include but is not limited to: LINQ to XML, XmlReader, XmlDocuments, XPath

  This objective does not include: XSLT, XmlWriter

• Query data by using ADO.NET Data Services.

This objective may include but is not limited to: implementing filtering and entitlement in ADO.NET Data Services, addressing resources, creating a query expression, accessing payload formats, Data Services interceptors

Managing Connections and Context (18%)

• Configure connection strings and providers.

  This objective may include but is not limited to: managing connection strings including Entity Framework connection strings, using the ConfigurationManager, correctly addressing the Microsoft SQL Server instance, implementing connection pooling, managing User Instanceand AttachDBfilename, switching providers, implementing multiple active result sets (MARS)

  This objective does not include: using the ConnectionStringBuilder; Oracle data provider; creating and using a custom provider; using third-party providers

• Create and manage a data connection.

This objective may include but is not limited to: connecting to a data source, closing connections, maintaining the life cycle of a connection

• Secure a connection.

  This objective may include but is not limited to: encrypting and decrypting connection strings, using Security Support Provider Interface (SSPI) or SQL Server authentication, read only vs. read/write connections

  This objective does not include:  Secure Sockets Layer (SSL)

• Manage the DataContext and ObjectContext.

This objective may include but is not limited to: managing the life cycle of DataContext and ObjectContext, extending the DataContext and ObjectContext, supporting POCO

• Implement eager loading.

  This objective may include but is not limited to: configuring loading strategy by using LazyLoadingEnabled, supporting lazy loading with POCO, explicitly loading entities

• Cache data.

  This objective may include but is not limited to: DataContext and ObjectContext cache including identity map, local data cache

  This objective does not include: Velocity, SqlCacheDependency

• Configure ADO.NET Data Services.

This objective may include but is not limited to: creating access rules for entities, configuring authorization and authentication, configuring HTTP verbs

Modeling Data (20%)

• Map entities and relationships by using the Entity Data Model.

  This objective may include but is not limited to: using the Visual Designer, building an entity data model from an existing database, managing complex entity mappings in EDMX, editing EDM XML, mapping to stored procedures, creating user-defined associations between entities, generating classes with inheritance and mapping them to tables

  This objective does not include: using MetadataWorkspace

• Map entities and relationships by using LINQ to SQL.

This objective may include but is not limited to: using the Visual Designer, building a LINQ to SQL model from an existing database, mapping to stored procedures

• Create and customize entity objects.

This objective may include but is not limited to: configuring changes to an Entity Framework entity, using the ADO.NET EntityObject Generator (T4), extending, self-tracking entities, snapshot change tracking, ObjectStateManager, partial classes, partial methods in the Entity Framework

• Connect a POCO model to the Entity Framework.

  This objective may include but is not limited to: implementing the Entity Framework with persistence ignorance, user-created POCO entities

  This objective does not include: using the POCO templates

• Create the database from the Entity Framework model.

This objective may include but is not limited to: customizing the Data Definition Language (DDL) (templates) generation process, generating scripts for a database, Entity Data Model tools

• Create model-defined functions.

This objective may include but is not limited to: editing the Conceptual Schema Definition Language CSDL, enabling model-defined functions by using the EdmFunction attribute, complex types

Developing a Web Application by Using ASP.NET MVC 2 (13%)

• Create custom routes.
  This objective may include but is not limited to: route constraints, route defaults, ignore routes, custom route parameters
• Create controllers and actions.
  This objective may include but is not limited to: Visual Studio support for right-click context menus; action filters (including Authorize, AcceptVerbs, and custom) and model binders; ActionResult sub-classes
• Structure an ASP.NET MVC application.
  This objective may include but is not limited to: single project areas (for example, route registration, Visual Studio tooling, and inter-area links); organizing controllers into areas; shared views; content files and folders
• Create and customize views.

  This objective may include but is not limited to: built-in and custom HTML helpers (for example, HTML.RenderAction and HTML.RenderPartial), strongly typed views, static page checking, templated input helpers, ViewMasterPage, ViewUserControl

  This objective does not include: Microsoft.Web.Mvc Futures assembly

Displaying and Manipulating Data (19%)

• Implement data-bound controls.

  This objective may include but is not limited to: advanced customization of DataList, Repeater, ListView, FormsView, DetailsView, TreeView, DataPager, Chart, GridView

  This objective does not include: working in Design mode

• Implement DataSource controls.

  This objective may include but is not limited to: ObjectDataSource, LinqDataSource, XmlDataSource, SqlDataSource, QueryExtender, EntityDataSource

  This objective does not include: AccessDataSource, SiteMapDataSource

• Query and manipulate data by using LINQ.

  This objective may include but is not limited to: transforming data by using LINQ to create XML or JSON, LINQ to SQL, LINQ to Entities, LINQ to objects, managing DataContext lifetime

  This objective does not include: basic LINQ to SQL

• Create and consume a data service.

This objective may include but is not limited to: WCF, Web service; server to server calls; JSON serialization, XML serialization

This objective does not include: client side, ADO.NET Data Services

• Create and configure a Dynamic Data project.
  This objective may include but is not limited to: dynamic data controls, custom field templates; connecting to DataContext and ObjectContext

Configuring and Extending a Web Application (15%)

• Configure authentication and authorization.

  This objective may include but is not limited to: using membership, using login controls, roles, location element, protecting an area of a site or a page

  This objective does not include:  Windows Live; Microsoft Passport; Windows and Forms authentication

• Configure providers.

  This objective may include but is not limited to: role, membership, personalization, aspnet_regsql.exe

  This objective does not include: creating custom providers

• Create and configure HttpHandlers and HttpModules.
  This objective may include but is not limited to: generic handlers, asynchronous handlers, setting MIME types and other content headers, wiring modules to application events
• Configure initialization and error handling.
  This objective may include but is not limited to: handling Application_Start, Session_Start, and Application_BeginRequest in global.asax, capturing unhandled exceptions, custom error section of web.config, redirecting to an error page; try and catch; creating custom exceptions
• Reference and configure ASMX and WCF services.

  This objective may include but is not limited to: adding service reference, adding Web reference, changing endpoints, wsdl.exe, svcutil.exe; updating service URL; shared WCF contracts assembly

  This objective does not include: creating WCF and ASMX services

• Configure projects and solutions, and reference assemblies.
  This objective may include but is not limited to: local assemblies, shared assemblies (global assembly cache), Web application projects, solutions, settings file, configuring a Web application by using web.config or multiple .config files; assemblyinfo
• Debug a Web application.
  This objective may include but is not limited to: remote, local, JavaScript debugging, attaching to process, logging and tracing, using local IIS, aspnet_regiis.exe
• Deploy a Web application.

  This objective may include but is not limited to: pre-compilation, publishing methods (e.g.,
  MSDeploy, xcopy, and FTP), deploying an MVC application

  This objective does not include: application pools, IIS configuration

Developing and Using Web Forms Controls (18%)

• Validate user input.

  This objective may include but is not limited to: client side, server side, and via AJAX; custom validation controls; regex validation; validation groups; datatype check; jQuery validation

  This objective does not include: RangeValidator and RequiredValidator

• Create page layout.

  This objective may include but is not limited to: AssociatedControlID; Web parts; navigation controls; FileUpload controls

  This objective does not include:  label; placeholder, panel controls; CSS, HTML, referencing CSS files, inlining

• Implement user controls.
  This objective may include but is not limited to: registering a control; adding a user control; referencing a user control; dynamically loading a user control; custom event; custom properties; setting toolbox visibility
• Implement server controls.

  This objective may include but is not limited to: composite controls, INamingContainer, adding a server control to the toolbox, global assembly cache, creating a custom control event, globally registering from web.config; TypeConverters

  This objective does not include: postback data handler, custom databound controls, templated control

• Manipulate user interface controls from code-behind.

  This objective may include but is not limited to: HTML encoding to avoid cross-site scripting, navigating through and manipulating the control hierarchy; FindControl; controlRenderingCompatibilityVersion; URL encoding; RenderOuterTable

  This objective does not include: Visibility, Text, Enabled properties

Developing Web Forms Pages (19%)

• Configure Web Forms pages.

  This objective may include but is not limited to: page directives such as ViewState, request validation, event validation, MasterPageFile; ClientIDMode; using web.config; setting the html doctype

  This objective does not include: referencing a master page; adding a title to a Web form

• Implement master pages and themes.

  This objective may include but is not limited to: creating and applying themes; adding multiple content placeholders; nested master pages; control skins; passing messages between master pages; switching between themes at runtime; loading themes at run time; applying a validation schema

  This objective does not include: creating a master page; basic content pages

• Implement globalization.
  This objective may include but is not limited to: resource files, browser files, CurrentCulture, currentUICulture, ASP:Localize
• Handle page life cycle events.
  This objective may include but is not limited to: IsPostback, IsValid, dynamically creating controls, control availability within the page life cycle, accessing control values on postback, overriding page events
• Implement caching.
  This objective may include but is not limited to: data caching; page output caching; control output caching; cache dependencies; setting cache lifetimes; substitution control
  This objective does not include: distributed caching (Velocity)
• Manage state.
  This objective may include but is not limited to: server-side technologies, for example, session and application; client-side technologies, for example, cookies and ViewState; configuring session state (in proc, state server, Microsoft SQL Server; cookieless); session state compression; persisting data by using ViewState; compressing ViewState; moving ViewState

Hurry! Last chance to get certified in 2010

uCertify has some terrific treats for you this Thanksgiving! Turkey and mashed potatoes are not the only things up for gobbling this week.

Check out these incredible savings!

60% off any 6 PrepKits

55% off any 5 PrepKits

50% off any 4 PrepKits

40% off any 3 Prepkits

35% off any 2 Prepkits

This is one feast you won’t want to miss! The best part … you won’t regret feasting! You will pass in your first attempt or your money back. No questions asked. This is one gift you won’t need to exchange.

‘Tis the season to be jolly! So, celebrate the savings! Treat yourself to the gift of learning!

uCertify wishes our customers a very happy Thanksgiving! GOBBLE, GOBBLE.

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Note: This is a guest post by uCertify Team.

You are not a current certification holder? PURCHASE YOUR PREPKIT, PASS AND SAVE 40%…

( CAN YOU BELIEVE THEIR EARLY EARLY BIRD PRICES ARE LOWER THAN 2009 PRICES? )

For more information visit http://www.ucertify.com and keep 40% at present!

Happy Thanksgiving!

Note: This is a guest Post by uCertify Team

Installing and Configuring TFS (27%)

• Install TFS.

This objective may include but is not limited to the following:

SQL Server version support, installing TFS in a multi-tier or multi-machine environment, installing TFS in a load-balanced environment, setting up version control proxy

• Configure application tier

This objective may include but is not limited to the following:

validating an installation, configuring SMTP for TFS, changing the URL (friendly name), changing the default SharePoint Web application, setting up reporting (SQL Server Analysis Services)

• Migrate and upgrade TFS.

This objective may include but is not limited to the following:

upgrading TFS 2005 or TFS 2008 to TFS 2010, importing a source base from Microsoft Visual Source Safe (VSS), a third-party revision control system, or a sub-version

• Install and configure team lab.

This objective may include but is not limited to the following:

set up environment templates, installing and configuring test agents, installing and configuring Virtual Machine Manager (basic Virtual Machine Manager installation), creating library shares or resource pools

• Install and configure multiple build agents and controllers.

This objective may include but is not limited to the following:

tagging, binding a controller to a project collection, adding as build agent

Managing TFS (27%)

• Manage Team Project Collections.

This objective may include but is not limited to the following:

moving project collections, managing team collections and projects, creating and configuring team project collections, moving team projects from one collection to another, creating a team project with SharePoint and SQL Server Reporting Services, cloning (splitting team project collections, partitioning)

• Configure for backup and recovery.

This objective may include but is not limited to the following: backup and recovery of TFS and related components, recover a failed application tier, recover a failed database tier, implement a disaster recovery plan

• Monitor server health and performance.

This objective may include but is not limited to the following:

application tier logs, monitoring the server for performance issues (monitoring activity logging database and TFS server manager), monitoring job infrastructure for failed jobs (monitoring warehouse adapters and warehouse jobs), cleanup of stale workspaces and shelvesets, cleanup builds (applying retention policies), setting up team build to use a version control proxy server

• Administer TFS application tier.

This objective may include but is not limited to the following:

retiring or archiving projects and purging the system, rebuilding a warehouse, configuring user permissions by using Active Directory Domain Services  and TFS groups, moving a TFS instance to a new server or a new domain, configuring security for TFS Work Item Only View

• Manage reporting for TFS.

This objective may include but is not limited to the following:

basic reporting using Microsoft Office Excel Services, adding a custom report to a SharePoint project portal, uploading a new SQL Server Reporting Services TFS report, configuring to enable a report to appear in a SharePoint project portal

• Set up automated functional and UI tests.

This objective may include but is not limited to the following: setting up a build definition, configuring the build definition to use the proper lab environment, setting up tests to work on an installed agent, setting up a service as interactive, setting up data collectors

Customizing TFS for Team Use (24%)

• Configure a team build definition.

This objective may include but is not limited to the following:

setting up for a Symbol Server and Source Server, setting up for test impact analysis, setting up for custom build numbers, configuring build log verbosity, setting up for code analysis, setting up for automated unit testing, setting up for architecture validation

• Configure and execute a build.

This objective may include but is not limited to the following:

queuing a build with parameters, reconciling workspaces as part of a gated check-in workflow, setting up build triggers (gated check-in, continuous integration, scheduled build)

• Modify a process template.

This objective may include but is not limited to the following:

customizing a process template by changing the workflow for a work item, adding a new work item type as a child of an existing work item (WI), uploading and downloading process templates

• Configure a team project.

This objective may include but is not limited to the following:

areas and iterations, default security groups, portal settings (team project portal site URL, process guidance URL)

• Apply work item customizations.

This objective may include but is not limited to the following:

link types, Global list, creating a new WI category and adding existing WI types to the new category, adding or removing fields, transitions, queries, customizing a workflow, creating or editing a work item type, importing and exporting work item types, renaming work item types

• Create Work Item Query Language (WIQL) queries.

This objective may include but is not limited to the following:

query folders and permissions, query types (tree, flat, directed), defining WIQL keywords, adding fields to a query, creating a WIQL query by using Team Explorer, identify built-in macros

• Configure client connectivity to TFS.

This objective may include but is not limited to the following:

configuring Visual Studio, Team Explorer, Microsoft Excel, Microsoft Project, and other tools to connect to TFS, configuring clients for proxy server

Administering Version Control (23%)

• Create and manage workspaces.

This objective may include but is not limited to the following:

cloaking, undo delete, modifying a workspace, deleting a workspace, specifying the workspace visibility, restoring deleted items, unlocking other users’ checkouts, pending changes, and code

• Configure shelvesets.

This objective may include but is not limited to the following:

private builds, creating a shelveset, deleting a shelveset, opening another user’s shelveset

• Branch and merge source artifacts.

This objective may include but is not limited to the following:

track change visualizations, converting a folder into a proper branch and creating a new branch, merging and resolving file conflicts, viewing branch hierarchy, creating a branch, deleting a branch

• Configure version control proxy.

This objective may include but is not limited to the following:

cache hit ratio, setting up the cache size, setting up for multiple TFS servers

• Configure team project version control settings.

This objective may include but is not limited to the following:

enable multiple checkout, enable get latest on checkout, configuring check-in policies for a team project (work items, builds, code analysis, testing policies)

Hello everyone,

Microsoft comes again with the famous FREE SECOND SHOT for all their certification exams. Now, you move your IT career to its next target. You can enhance your knowledge in a particular technology by taking multiple Microsoft Certified Technology Specialist (MCTS) certifications to show girth across different products, or build on the MCTS to take home a Microsoft Certified IT Professional (MCITP) certification with Microsoft Certification Exam Packs with Second Shots. As you all know that Microsoft Certification Exam Packs offer huge discounts plus a Free Second Shot for each and every exam in the pack. The Second Shot offer gives you the power to retake an exam if you do not pass it in the first time.

Proceed Now! Buy a Microsoft Certification Pack, get Second Shots Also

It does not matter what you are doing to validate your skills for your next IT job, hoping to get a promotion, or looking for your next Microsoft Certification, Microsoft always helps put together it easier for you to accomplish your ambitions.

In order to help you to get started, Microsoft is now giving you the chance i.e. Microsoft Certification Exam Packs, which offer huge discounts along with a Free Second Shot for each and every exam in the pack. You can select any of the following exam pack that is right for you:

Certification pack	Savings	Second Shot
5-exam pack	20%	Included with each exam
4-exam pack	20%	Included with each exam
3-exam pack	15%	Included with each exam
2-exam pack	15%	Included with each exam
1-exam	Regular price	Add 15% to single exam price*

For more Information about Microsoft Certification Exam Packs with free Second Shot offers, Go through this….

System.ServiceModel.Routing

Contains classes that are used by the Windows Communication Foundation (WCF) infrastructure to implement the routing of messages between WCF endpoints.

System.ServiceModel.Routing.Configuration

Contains configuration classes that are used by the Windows Communication Foundation (WCF) infrastructure to convert XML into common language runtime (CLR) types.

System.ServiceModel.Security

Contains classes that support general Windows Communication Foundation (WCF) security.

System.ServiceModel.Security.Tokens

Contains types that represent security tokens and certificates for Windows Communication Foundation (WCF) security.

System.ServiceModel.ServiceMoniker40

System.ServiceModel.Syndication

Contains the types that make up the syndication object model.

System.ServiceModel.Web

Contains types that make up the Web HTTP programming model.

System.ServiceModel.XamlIntegration

Provides utility classes to enable the serialization of entities to XAML.

System.ServiceProcess

Provides classes that enable you to implement, install, and control Windows service applications. Services are long-running executables that run without a user interface. Implementing a service involves inheriting from theServiceBase class and defining specific behavior to process when start, stop, pause, and continue commands are passed in, as well as custom behavior and actions to take when the system shuts down.

System.ServiceProcess.Design

Contains classes that can be used to extend design-time support for Windows service applications.

System.Speech.AudioFormat

System.Speech.Recognition

Contains Windows Desktop Speech technology types for implementing speech recognition.

System.Speech.Recognition.SrgsGrammar

System.Speech.Synthesis

System.Speech.Synthesis.TtsEngine

Contains types that support the creation of custom engines based on the Speech Synthesis Markup Language (SSML) for rendering Text-to-Speech (TTS).

System.Text

Contains classes representing ASCII, Unicode, UTF-7, and UTF-8 character encodings; abstract base classes for converting blocks of characters to and from blocks of bytes; and a helper class that manipulates and formatsString objects without creating intermediate instances of String.

System.Text.RegularExpressions

Contains classes that provide access to the .NET Framework regular expression engine. The namespace provides regular expression functionality that can be used from any platform or language that runs within the.NET Framework.

System.Threading

Provides classes and interfaces that enable multithreaded programming. In addition to classes for synchronizing thread activities and access to data (Mutex, Monitor, Interlocked, AutoResetEvent, and so on), this namespace includes a ThreadPool class that lets you use a pool of system-supplied threads, and a Timer class that executes callback methods on thread pool threads.

System.Threading.Tasks

Provides types that simplify the work of writing concurrent and asynchronous code.

System.Timers

Provides the Timer component, which enables you to raise an event on a specified interval.

System.Transactions

Contains classes that enable your code to participate in transactions. The classes support transactions with multiple, distributed participants, multiple phase notifications, and durable enlistments.

System.Transactions.Configuration

Contains classes that describe configuration options used by System.Transactions classes.

System.Web

Provides classes and interfaces that enable browser-server communication. This namespace includes theHttpRequest class, which provides extensive information about the current HTTP request, the HttpResponse class, which manages HTTP output to the client, and the HttpServerUtility class, which provides access to server-side utilities and processes. System.Web also includes classes for cookie manipulation, file transfer, exception information, and output cache control.

System.Web.ApplicationServices

Provides classes that provide access to ASP.NET forms authentication, roles, and profiles application services as Windows Communication Foundation (WCF) services.

System.Web.Caching

Provides classes for caching frequently used data on the server. This includes the Cache class, a dictionary that lets you store arbitrary data objects, such as hash tables and data sets. It also provides expiration functionality for those objects, and methods that let you add and remove the objects. You can also add the objects with a dependency upon other files or cache entries, and perform a callback to notify your application when an object is removed from the cache.

System.Web.ClientServices

Contains classes that support access to the ASP.NET login, roles, and profiles services from Windows-based applications.

System.Web.ClientServices.Providers

Contains client service providers and other classes that support access to the ASP.NET login, roles, and profiles services from Windows-based applications.

System.Web.Compilation

Contains classes for generating and compiling custom file types within the ASP.NET build environment.

System.Web.Configuration

Contains classes that are used to set up ASP.NET configuration.

System.Web.DynamicData

Contains classes that provide the core functionality for ASP.NET dynamic data and extensibility features that let you customize dynamic data behavior.

System.Web.DynamicData.Design

Contains classes that provide design-time support for the classes in the System.Web.DynamicData namespace.

System.Web.DynamicData.ModelProviders

Contains classes that define the core functionality for ASP.NET Dynamic Data providers.

System.Web.Handlers

Contains HTTP handler classes that process HTTP requests to a Web server.

System.Web.Hosting

Provides the functionality for hosting ASP.NET applications from managed applications outside of Microsoft Internet Information Services (IIS).

System.Web.Management

Contains classes and interfaces for managing and monitoring the health of Web applications.

System.Web.Mobile

Contains the core capabilities, including authentication and error-handling, required for building ASP.NET mobile Web applications.

System.Web.Profile

Contains classes that are used to implement the ASP.NET user profile in Web server applications.

System.Web.Query.Dynamic

Contains classes that are used to parse expressions from a LinqDataSource control into a Language-Integrated Query (LINQ).

System.Web.RegularExpressions

Provides regular expressions used to parse ASP.NET files. All members of the System.Web.RegularExpressionsnamespace are descendants of the Regex class.

System.Web.Routing

Provides classes that are used with URL routing, which enables you to use URLs that do not map to a physical file.

System.Web.Script

Contains classes that provide script resource information.

System.Web.Script.Serialization

Contains classes that provide JavaScript Object Notation (JSON) serialization and deserialization for managed types. It also provides extensibility features to customize serialization behavior.

System.Web.Script.Services

Provides attributes to customize Web service support for using AJAX functionality in ASP.NET.

System.Web.Security

Contains classes that are used to implement ASP.NET security in Web server applications.

System.Web.Services

Consists of the classes that enable you to create XML Web services using ASP.NET and XML Web service clients. XML Web services are applications that provide the ability to exchange messages in a loosely coupled environment using standard protocols such as HTTP, XML, XSD, SOAP, and WSDL. XML Web services enable the building of modular applications within and across companies in heterogeneous environments, making them interoperable with a broad variety of implementations, platforms, and devices.

System.Web.Services.Configuration

Consists of the classes that configure how XML Web services created using ASP.NET run.

System.Web.Services.Description

Consists of the classes that enable you to publicly describe an XML Web service by using the Web Services Description Language (WSDL). Each class in this namespace corresponds to a specific element in the WSDL specification, and the class hierarchy corresponds to the XML structure of a valid WSDL document.

System.Web.Services.Discovery

Consists of the classes that enable XML Web service clients to locate the available XML Web services on a Web server through a process called XML Web Services Discovery.

System.Web.Services.Protocols

Consists of the classes that define the protocols used to transmit data across the wire during the communication between XML Web service clients and XML Web services created using ASP.NET.

System.Web.SessionState

Supplies classes and interfaces that enable storage of data specific to a single client within a Web application on the server. The session state data is used to give the client the appearance of a persistent connection with the application. State information can be stored within local process memory or, for Web farm configurations, out-of-process using either the ASP.NET State service or a SQL Server database.

System.Web.UI

Provides classes and interfaces that enable you to create ASP.NET server controls and ASP.NET Web pages for the user interface of your ASP.NET Web applications. This namespace includes the Control class, which provides all HTML server controls, Web server controls, and user controls with a common set of functionality. It also includes the Page control, which is generated automatically whenever a request is made for an .aspx file in an ASP.NET Web application. Also included are classes which provide the server controls with data-binding functionality, the ability to save the view state of a given control or page, and parsing functionality.

System.Web.UI.Adapters

Contains the base classes for control adapters and page adapters, which you can use to override life-cycle states of pages and controls to modify their default markup or behavior for new markup standards or for specific browsers.

System.Web.UI.DataVisualization.Charting

Contains types for the Chart Web server control.

System.Web.UI.Design

Contains classes that can be used to extend design-time support for ASP.NET Web pages and for Web server controls.

System.Web.UI.Design.MobileControls

Obsolete. Contains classes that provide design-time support for the classes in the System.Web.UI.MobileControlsnamespace. The classes in this namespace are obsolete; use the classes in System.Web.UI.Design.WebControlsinstead.

System.Web.UI.Design.MobileControls.Converters

Contains classes that provide design-time support for data type converters in mobile controls.

System.Web.UI.Design.WebControls

Contains classes that can be used to extend design-time support for Web server controls.

System.Web.UI.Design.WebControls.WebParts

Contains classes that provide design-time support for controls derived from classes in theSystem.Web.UI.WebControls.WebParts namespace.

System.Web.UI.HtmlControls

Consists of a collection of classes that enable you to create HTML server controls on a Web Forms page. HTML server controls run on the server and map directly to standard HTML tags supported by most browsers. This enables you to programmatically control the HTML elements on a Web Forms page.

System.Web.UI.MobileControls

Obsolete. Contains a set of ASP.NET server controls that can intelligently render your application for different mobile devices. The classes in this namespace are obsolete; use the controls in System.Web.UI.WebControlsinstead.

System.Web.UI.MobileControls.Adapters

Contains classes you can use to override life-cycle stages of a mobile control to modify its default HTML, CHTML, or WML markup or behavior for new markup standards or for specific browsers and mobile devices.

System.Web.UI.MobileControls.Adapters.XhtmlAdapters

Contains classes you can use to override life-cycle stages of a mobile control to modify its default XHTML markup or behavior for new markup standards or for specific browsers and mobile devices.

System.Web.UI.WebControls

Contains classes that enable you to create Web server controls on a Web page. Web server controls run on the server and include form controls such as buttons and text boxes. They also include special-purpose controls such as a calendar. Because Web server controls run on the server, you can programmatically control these elements. Web server controls are more abstract than HTML server controls. Their object model does not necessarily reflect HTML syntax.

System.Web.UI.WebControls.Adapters

Contains classes you can use to override life-cycle stages of a Web control to modify a control’s default markup or behavior for new markup standards or for specific browsers.

System.Web.UI.WebControls.Expressions

Provides classes for filtering data in a Web page using the QueryExtender control.

System.Web.UI.WebControls.WebParts

Contains an integrated set of classes and interfaces for creating Web pages whose appearance and behavior can be modified (personalized) by end users. The user-defined settings for each page are saved for future browser sessions.

System.Web.Util

Contains classes that enable callback methods to be run under the scope of a transaction and that enable work to be posted to separate threads.

System.Windows

Provides several important Windows Presentation Foundation (WPF) base element classes, various classes that support the WPF property system and event logic, and other types that are more broadly consumed by the WPF core and framework.

System.Windows.Annotations

Contains types that support user-created annotations on content displayed in Windows Presentation Foundation (WPF) document viewing controls.

System.Windows.Annotations.Storage

Contains classes that define the storage architecture and media to save and retrieve user-created annotations.

System.Windows.Automation

Contains classes that provide support for Windows Presentation Foundation (WPF) user interface automation clients.

System.Windows.Automation.Peers

Defines the AutomationPeer base class and a set of types derived from it that correspond to.NET Framework controls.

System.Windows.Automation.Provider

Contains types for creating UI Automation providers for Windows Presentation Foundation (WPF).

System.Windows.Automation.Text

Contains enumerations that specify text formatting and related behavior for Windows Presentation Foundation (WPF) UI automation.

System.Windows.Baml2006

Contains reader and writer classes that can consume XAML in BAML form.

System.Windows.Controls

Contains classes to create controls that enable a user to interact with an application.

System.Windows.Controls.Primitives

Contains base classes and controls that are intended to be used as part of other, more complex controls.

System.Windows.Converters

Contains classes that support type conversion during serialization in Windows Presentation Foundation (WPF).

System.Windows.Data

Contains classes used for binding properties to data sources, data source provider classes, and data-specific implementations of collections and views.

System.Windows.Documents

Contains classes that support FixedDocument, FlowDocument, and XML Paper Specification (XPS) document creation.

System.Windows.Documents.DocumentStructures

Contains classes that describe the structure of an XpsDocument in terms of sections, paragraphs, figures, bulleted or numbered lists, and tables.

System.Windows.Documents.Serialization

Contains classes that support the creation and use of run-time accessible plug-in serializers which read and write documents in different data formats.

System.Windows.Forms

Contains classes for creating Windows-based applications that take full advantage of the rich user interface features available in the Windows operating system.

System.Windows.Forms.DataVisualization.Charting

Contains types for the Chart Windows Forms control.

System.Windows.Forms.Design

Contains classes that support design-time configuration and behavior for Windows Forms components. These classes consist of: Designer classes that provide support for Windows Forms components, a set of design time services, UITypeEditor classes for configuring certain types of properties, and classes for importing ActiveX controls.

System.Windows.Forms.Design.Behavior

Contains classes for creating custom user interface behavior for components at design time.

System.Windows.Forms.Integration

Contains classes that support interoperation of Windows Forms and Windows Presentation Foundation (WPF) controls.

System.Windows.Forms.Layout

Contains classes that support design-time and run-time layout behaviors.

System.Windows.Forms.VisualStyles

Contains classes for rendering controls and other Windows user interface elements with visual styles.

System.Windows.Ink

Provides classes to interact with and manipulate ink on the Windows Presentation Foundation (WPF) platform.

System.Windows.Input

Contains classes that support the Windows Presentation Foundation (WPF) input system.

System.Windows.Input.Manipulations

Provides functionality for monitoring and responding to a collection of manipulators as a single composite, enabling an application to track the changes to the composite instead of the individual components.

System.Windows.Input.StylusPlugIns

Provides classes that support manipulating data from a tablet pen on the Windows Presentation Foundation (WPF) platform.

System.Windows.Interop

Contains classes that support interoperation between Windows Presentation Foundation (WPF) and other technologies.

System.Windows.Markup

Contains classes to support serialization and Extensible Application Markup Language (XAML) in Windows Presentation Foundation (WPF) applications.

System.Windows.Markup.Localizer

Contains types that assist in the localization of binary XAML (BAML) sources.

System.Windows.Markup.Primitives

Contains classes that support Extensible Application Markup Language (XAML) in Windows Presentation Foundation (WPF) applications.

System.Windows.Media

Contains classes that enable integration of rich media, including drawings, text, and audio/video content, within Windows Presentation Foundation (WPF) applications.

System.Windows.Media.Animation

Contains classes that provide property animation functionality in Windows Presentation Foundation (WPF) applications.

System.Windows.Media.Converters

Contains types used by the MarkupWriter for serialization of Extensible Application Markup Language (XAML).

System.Windows.Media.Effects

Contains types that can be used to apply visual effects to bitmap images.

System.Windows.Media.Imaging

Contains types used to encode and decode bitmap images.

System.Windows.Media.Media3D

Contains types that support 3-D presentation in Windows Presentation Foundation (WPF) applications.

System.Windows.Media.Media3D.Converters

Defines types used by the MarkupWriter class for serialization of Extensible Markup Language (XAML).

System.Windows.Media.TextFormatting

Contains classes that control formatting of text, typically at a lower level than control-based text presentation or the text object model.

System.Windows.Navigation

Contains types used for navigation, including navigating between windows, and navigation journaling.

System.Windows.Resources

Contains low-level classes that support the Windows Presentation Foundation (WPF) resource model and the Resources build action.

System.Windows.Shapes

Contains a library of shapes that can be used in Extensible Application Markup Language (XAML) or code.

System.Windows.Shell

Contains types that provide managed code access to the enhanced functionality of the Windows 7 taskbar.

System.Windows.Threading

Contains classes that support the Windows Presentation Foundation (WPF) threading system.

System.Windows.Xps

Contains classes that write XML Paper Specification (XPS) documents to a data store or print queue.

System.Windows.Xps.Packaging

Contains classes that enable applications to read and write the components of an XPS document.

System.Windows.Xps.Serialization

Contains classes that support serialization of XPS documents.

System.Workflow.Activities

Contains classes that define activities that can be added to workflows to create and run an executable representation of a work process.

System.Workflow.Activities.Configuration

Contains classes that represent sections of a configuration file.

System.Workflow.Activities.Rules

Contains classes that define the conditions and actions that form a rule.

System.Workflow.Activities.Rules.Design

Contains classes that manage the Rule Set Editor and the Rule Condition Editor dialog boxes.

System.Workflow.ComponentModel

Contains the types that are used to create activities and workflows.

System.Workflow.ComponentModel.Compiler

Provides the infrastructure for validating and compiling activities and workflows.

System.Workflow.ComponentModel.Design

Contains classes that developers can use to build custom design-time behavior for workflows and activities.

System.Workflow.ComponentModel.Serialization

Provides the infrastructure for managing the serialization of activities and workflows to and from Extensible Application Markup Language (XAML) and CodeDOM.

System.Workflow.Runtime

Contains types that can be used to control the workflow runtime engine and the execution of a workflow instance.

System.Workflow.Runtime.Configuration

Contains classes that are used to configure the workflow runtime engine.

System.Workflow.Runtime.DebugEngine

Contains types for use in debugging workflow instances.

System.Workflow.Runtime.Hosting

Contains classes that are related to services provided to the workflow runtime engine by the host application.

System.Workflow.Runtime.Tracking

Contains types related to tracking services.

System.Xaml

Provides types that relate to XAML parsers and processors.

System.Xaml.Hosting

Contains classes related to XAML hosting.

System.Xaml.Hosting.Configuration

Contains classes related to XAML hosting configuration.

System.Xaml.Permissions

Contains types that specify permissions for certain XAML loading scenarios, such as loading under partial trust.

System.Xaml.Schema

Contains types that support the XAML type system for the XAML information set.

System.Xml

Provides standards-based support for processing XML.

System.Xml.Linq

Contains the types for LINQ to XML, which is an in-memory XML programming interface that enables you to modify XML documents efficiently and easily.

System.Xml.Resolvers

Provides support for prepopulating the cache with DTDs or XML streams.

System.Xml.Schema

Contains the XML classes that provide standards-based support for XML Schema definition language (XSD) schemas.

System.Xml.Serialization

Contains classes that are used to serialize objects into XML format documents or streams.

System.Xml.Serialization.Advanced

Contains classes that enable you to customize the code generated from a Web Services Description Language (WSDL) document.

System.Xml.Serialization.Configuration

Contains classes used to read the values found in application configuration files in the system.xml.serializationelement section.

System.Xml.XPath

Contains the classes that define a cursor model for navigating and editing XML information items as instances of the XQuery 1.0 and XPath 2.0 Data Model.

System.Xml.Xsl

Provides support for Extensible Stylesheet Transformation (XSLT) transforms. This namespace supports the W3C XSL Transformations (XSLT) Version 1.0 Recommendation.

System.Xml.Xsl.Runtime

Provides internal support for the classes in the System.Xml.Xsl namespace. The classes in this namespace support the .NET Framework infrastructure and are not intended to be used directly from your code.

UIAutomationClientsideProviders

Contains a single class that maps client automation providers.

System.DirectoryServices.AccountManagement

It provides uniform access and manipulation of user, computer, and group security principals across multiple principal stores.

System.DirectoryServices.ActiveDirectory

It provides a high-level abstraction object model that builds around Active Directory directory service tasks. The Active Directory directory service concepts such as forest, domain, site, subnet, partition, and schema are part of the object model.

System.DirectoryServices.Protocols

It provides the methods defined in the Lightweight Directory Access Protocol (LDAP) version 3 and Directory Services Markup Language (DSML) version 2.0 standards.

System.Drawing

It provides access to GDI+ basic graphics functionality. More advanced functionality is provided in theSystem.Drawing.Drawing2D, System.Drawing.Imaging, and System.Drawing.Text namespaces.

System.Drawing.Design

It holds classes that extend design-time user interface (UI) logic and drawing. You can further extend this design-time functionality to create custom toolbox items, type-specific value editors that can edit and graphically represent values of their supported types, or type converters that can convert values between certain types. This namespace provides the basic frameworks for developing extensions to the design-time UI.

System.Drawing.Drawing2D

It provides advanced two-dimensional and vector graphics functionality. This namespace includes the gradient brushes, the Matrix class (used to define geometric transforms), and the GraphicsPath class.

System.Drawing.Imaging

It provides advanced GDI+ imaging functionality. Basic graphics functionality is provided by the System.Drawingnamespace.

System.Drawing.Printing

It provides print-related services. Typically, you create a new instance of the PrintDocument class, set the properties that describe what to print, and call the Print method to actually print the document.

System.Drawing.Text

It provides advanced GDI+ typography functionality. Basic graphics functionality is provided by the System.Drawingnamespace. The classes in this namespace enable users to create and use collections of fonts.

System.Dynamic

It provides classes and interfaces that support the dynamic language runtime (DLR).

System.EnterpriseServices

It provides an important infrastructure for enterprise applications. COM+ provides a services architecture for component programming models deployed in an enterprise environment. This namespace provides .NET Framework objects with access to COM+ services, making the .NET Framework objects more practical for enterprise applications.

System.EnterpriseServices.CompensatingResourceManager

It provides classes that enable you to use a Compensating Resource Manager (CRM) in managed code. A CRM is a service provided by COM+ that enables you to include non-transactional objects in Microsoft Distributed Transaction Coordinator (DTC) transactions. Although CRMs do not provide the capabilities of a full resource manager, they do provide transactional atomicity (all-or-nothing behavior) and durability through the recovery log.

System.Globalization

It holds classes that define culture-related information, including the language, the country/region, the calendars in use, the format patterns for dates, currency, and numbers, and the sort order for strings. These classes are useful for writing globalized (internationalized) applications.

System.IdentityModel.Claims

It holds types that support the use of claims in the Extensible Identity Model.

System.IdentityModel.Policy

It holds types to build or use authorization policies in Windows Communication Foundation (WCF).

System.IdentityModel.Selectors

It holds the types that provide security tokens for outgoing SOAP messages and that authenticate security tokens in incoming SOAP messages.

System.IdentityModel.Tokens

It holds the types that are related to the predefined security tokens that ship with Windows Communication Foundation (WFC).

System.IO

It holds types that enable synchronous and asynchronous reading and writing on data streams and files.

System.IO.Compression

It holds classes that provide basic compression and decompression for streams.

System.IO.IsolatedStorage

It holds types that support the creation and use of isolated stores. With these stores, you can read and write data that less trusted code cannot access and help prevent the exposure of sensitive information that can be saved elsewhere on the file system. Data is stored in compartments that are isolated by the current user and by the assembly in which the code exists.

System.IO.Log

It holds types for implementing a custom diagnostic logging or transaction processing system.

System.IO.MemoryMappedFiles

It holds classes for using a memory-mapped file, which maps the contents of a file to an application’s logical address space.

System.IO.Packaging

It holds types that support storage of multiple data objects in a single container.

System.IO.Pipes

It holds types that provide a means for interprocess communication through anonymous and/or named pipes.

System.IO.Ports

It holds classes that control serial ports, providing a framework for synchronous and event-driven I/O, access to pin and break states, access to serial driver properties, and enumerations for specifying port characteristics.

System.Linq

It holds classes and interfaces that support queries that use Language-Integrated Query (LINQ).

System.Linq.Expressions

It holds types that enable language-level code expressions to be represented as objects in the form of expression trees.

System.Management

It provides access to a rich set of management information and management events about the system, devices, and applications instrumented to the Windows Management Instrumentation (WMI) infrastructure.

System.Management.Instrumentation

It provides the classes necessary for instrumenting applications for management and exposing their management information and events through WMI to potential consumers.

System.Media

It holds classes for playing sound files and accessing system sounds.

System.Messaging

It provides classes that enable you to connect to, monitor, and administer message queues on the network and send, receive, or peek messages.

System.Messaging.Design

It holds classes that can be used to extend design-time support for System.Messaging classes.

System.Net

It provides a simple programming interface for many of the protocols used on networks today. The WebRequestand WebResponse classes form the basis of what are called pluggable protocols, an implementation of network services that enables you to develop applications that use Internet resources without worrying about the specific details of the individual protocols.

System.Net.Cache

It defines the types and enumerations used to define cache policies for resources obtained using the WebRequestand HttpWebRequest classes.

System.Net.Configuration

It holds classes that applications use to programmatically access and update configuration settings for theSystem.Net namespaces.

System.Net.Mail

It holds classes used to send electronic mail to a Simple Mail Transfer Protocol (SMTP) server for delivery.

System.Net.Mime

It holds types that are used to represent Multipurpose Internet Mail Exchange (MIME) headers. These types are used with the types in the System.Net.Mail namespace to specify Content-Type, Content-Disposition and Content-transfer-Encoding headers when sending e-mail using the SmtpClient class.

System.Net.NetworkInformation

It provides access to network traffic data, network address information, and notification of address changes for the local computer. The namespace also contains classes that implement the Ping utility. You can use Ping and related classes to check whether a computer is reachable across the network.

System.Net.PeerToPeer

It provides access to peer networking functionality.

System.Net.PeerToPeer.Collaboration

It provides types that enhance peer-to-peer networking functionality and provide capabilities for serverless managed collaboration sessions.

System.Net.Security

It provides network streams for secure communications between hosts.

System.Net.Sockets

It provides a managed implementation of the Windows Sockets (Winsock) interface for developers who need to help control access to the network.

System.Numerics

It holds types that complement the numeric primitives, such as Byte, Double, and Int32, that are defined by the .NET Framework.

System.Printing

It holds types to support printing.

System.Printing.IndexedProperties

It holds classes that provide access to the properties of print system objects without using reflection, and enable rapid copying of the property settings to another object of the same type.

System.Printing.Interop

It provides types to support interconversion of managed PrintTicket objects and unmanaged Graphics Device Interface (GDI) DEVMODE structures.

System.Reflection

It holds classes and interfaces that provide a managed view of loaded types, methods, and fields, with the ability to dynamically create and invoke types.

System.Reflection.Emit

It holds classes that enable a compiler or tool to emit metadata and Microsoft intermediate language (MSIL) and optionally generate a PE file on disk. The primary clients of these classes are script engines and compilers.

System.Resources

It holds classes and interfaces that enable developers to create, store, and manage various culture-specific resources used in an application.

System.Resources.Tools

It holds the StronglyTypedResourceBuilder class, which provides support for strongly typed resources. Beginning with the .NET Framework version 2.0, this compile-time feature encapsulates access to resources by creating classes that contain a set of static read-only (get) properties, thus making it easier to consume resources.

System.Runtime

It holds advanced types that support diverse namespaces such as System, the Runtime namespaces, and theSecurity namespaces.

System.Runtime.Caching

It holds types that let you implement output caching in applications that are built on the .NET Framework.

System.Runtime.Caching.Configuration

It holds configuration handler classes for the .NET Framework caching feature.

System.Runtime.Caching.Hosting

It holds types that support the .NET Framework hosting environments that use caching features.

System.Runtime.CompilerServices

It provides functionality for compiler writers who use managed code to specify attributes in metadata that affect the run-time behavior of the common language runtime. The classes in this namespace are for compiler writers use only.

System.Runtime.ConstrainedExecution

It defines a set of types that enumerate and define a contract for reliability between the author of some code and the developers who take a dependency on that code. The types are intended for use in constrained execution regions (CERs) only.

System.Runtime.DurableInstancing

It holds classes that are used by the Windows Communication Foundation (WCF) infrastructure to implement a persistence provider.

System.Runtime.ExceptionServices

It holds classes for advanced exception handling.

System.Runtime.Hosting

It holds advanced types that are used in application activation within application domains.

System.Runtime.InteropServices

It provides a wide variety of members that support COM interop and platform invoke services. If you are unfamiliar with these services, see Interoperating with Unmanaged Code.

System.Runtime.InteropServices.ComTypes

It holds methods that are definitions of COM functions for managed code. These functions replace the now-obsolete UCOM methods in the System.Runtime.InteropServices namespace.

System.Runtime.InteropServices.Expando

It holds the IExpando interface, which lets you modify an object by adding or removing its members.

System.Runtime.Remoting

It holds classes and interfaces that enable developers to create and configure distributed applications.

System.Runtime.Remoting.Activation

It holds classes and objects that support server and client activation of remote objects.

System.Runtime.Remoting.Channels

It holds classes that support and handle channels and channel sinks, which are used as the transport medium when a client calls a method on a remote object.

System.Runtime.Remoting.Channels.Http

It holds channels that use the HTTP protocol to transport messages and objects to and from remote locations. By default, the HTTP channels encode objects and method calls in SOAP format for transmission, but other encoding and decoding formatter sinks can be specified in the configuration properties of a channel.

System.Runtime.Remoting.Channels.Ipc

It defines a communication channel for remoting that uses the Interprocess Communication (IPC) system of the Windows operating system. Because it does not use network communication, the IPC channel is much faster than the HTTP and TCP channels, but it can only be used for communication between application domains on the same physical computer.

System.Runtime.Remoting.Channels.Tcp

It holds channels that use the TCP protocol to transport messages and objects to and from remote locations. By default, the TCP channels encode objects and method calls in binary format for transmission, but other encoding and decoding formatter sinks can be specified in the configuration properties of a channel.

System.Runtime.Remoting.Contexts

It holds objects that define the contexts all objects reside within. A context is an ordered sequence of properties that defines an environment for the objects within it. Contexts are created during the activation process for objects that are configured to require certain automatic services such synchronization, transactions, just-in-time (JIT) activation, security, and so on. Multiple objects can live inside a context.

System.Runtime.Remoting.Lifetime

It holds classes that manage the lifetime of remote objects. Traditionally, distributed garbage collection uses reference counts and pinging for control over the lifetime of objects. This works well when there are a few clients per service, but does not scale well to thousands of clients per service. The remoting lifetime service associates a lease with each service, and deletes a service when its lease time expires. The lifetime service can take on the function of a traditional distributed garbage collector, and it also adjusts well when the numbers of clients per server increases.

System.Runtime.Remoting.Messaging

It holds classes used to create and remote messages. The remoting infrastructure uses messages to communicate with remote objects. Messages are used to transmit remote method calls, to activate remote objects, and to communicate information. A message object carries a set of named properties, including action identifiers, envoy information, and parameters.

System.Runtime.Remoting.Metadata

It holds classes and attributes that can be used to customize generation and processing of SOAP for objects and fields. The classes of this namespace can be used to indicate the SOAPAction, type output, XML element name, and the method XML namespace Uniform Resource Identifier (URI).

System.Runtime.Remoting.Metadata.W3cXsd2001

It holds the XML Schema Definition (XSD) defined by the World Wide Web Consortium (W3C) in 2001. The XML Schema Part 2: Datatypes specification from W3C identifies format and behavior of various data types. This namespace contains wrapper classes for the data types that conform to the W3C specification. All date and time types conform to the ISO standards specification.

System.Runtime.Remoting.MetadataServices

It holds the classes used by the Soapsuds.exe command line tool and the user code to convert metadata to and from XML schema for the remoting infrastructure.

System.Runtime.Remoting.Proxies

It holds classes that control and provide functionality for proxies. A proxy is a local object that is an image of a remote object. Proxies enable clients to access objects across remoting boundaries.

System.Runtime.Remoting.Services

It holds service classes that provide functionality to the .NET Framework.

System.Runtime.Serialization

It holds classes that can be used for serializing and deserializing objects. Serialization is the process of converting an object or a graph of objects into a linear sequence of bytes for either storage or transmission to another location. Deserialization is the process of taking in stored information and recreating objects from it.

System.Runtime.Serialization.Configuration

It holds classes used to read the values found in application configuration files in the <system.xml.serialization>section.

System.Runtime.Serialization.Formatters

It provides common enumerations, interfaces, and classes that are used by serialization formatters.

System.Runtime.Serialization.Formatters.Binary

It holds the BinaryFormatter class, which can be used to serialize and deserialize objects in binary format.

System.Runtime.Serialization.Formatters.Soap

It holds the SoapFormatter class, which can be used to serialize and deserialize objects in the SOAP format.

System.Runtime.Serialization.Json

It holds types for serializing objects to JavaScript Object Notation (JSON) and deserializing objects from JSON.

System.Runtime.Versioning

It holds advanced types that support versioning in side-by-side implementations of the .NET Framework.

System.Security

It provides the underlying structure of the .NET Framework security system, including base classes for permissions.

System.Security.AccessControl

It provides programming elements that control access to, and audit security-related actions on, securable objects.

System.Security.Authentication

It provides a set of enumerations that describe the security of a connection.

System.Security.Authentication.ExtendedProtection

It provides support for authentication using extended protection for applications.

System.Security.Authentication.ExtendedProtection.Configuration

It provides support for configuration of authentication using extended protection for applications.

System.Security.Cryptography

Provides cryptographic services, including secure encoding and decoding of data, as well as many other operations, such as hashing, random number generation, and message authentication.

System.Security.Cryptography.Pkcs

It holds programming elements for Public Key Cryptography Standards (PKCS), including methods for signing data, exchanging keys, requesting certificates, public key encryption and decryption, and other security functions.

System.Security.Cryptography.X509Certificates

It holds the common language runtime implementation of the Authenticode X.509 v.3 certificate. This certificate is signed with a private key that uniquely and positively identifies the holder of the certificate.

System.Security.Cryptography.Xml

It holds classes to support the creation and validation of XML digital signatures.

System.Security.Permissions

It defines classes that control access to operations and resources based on policy.

System.Security.Policy

It holds code groups, membership conditions, and evidence. These three types of classes are used to create the rules applied by the .NET Framework security policy system. Evidence classes are the input to security policy, and membership conditions are the switches; together these create policy statements and determine the granted permission set. Policy levels and code groups are the structure of the policy hierarchy. Code groups are the encapsulation of a rule and are arranged hierarchically in a policy level.

System.Security.Principal

It defines a principal object that represents the security context under which code is running.

System.Security.RightsManagement

It holds classes to support rights management of application-created content, such as content stored in a Package or XpsDocument.

System.ServiceModel

It holds the types necessary to build Windows Communication Foundation (WCF) service and client applications that can be used to build widely distributed applications.

System.ServiceModel.Activation

It holds the types required to construct and modify the dynamic creation of service hosts in a managed hosting environment.

System.ServiceModel.Activation.Configuration

It holds classes that represent the configuration elements in the SMSvcHost.exe.config file.

System.ServiceModel.Activities

It holds classes that enable you to send messages to and receive messages from workflows.

System.ServiceModel.Activities.Activation

It holds the WorkflowServiceHostFactory class that provides instances of WorkflowServiceHost in managed hosting environments where the host instance is created dynamically in response to incoming messages.

System.ServiceModel.Activities.Configuration

It holds classes that are used to configure workflow services. These classes allow you to apply service and endpoint behaviors and configure tracking.

System.ServiceModel.Activities.Description

It holds classes that enable you to control various behaviors related to workflow services.

System.ServiceModel.Activities.Presentation.Factories

It holds factories that create Receive/SendReply and Send/ReceiveReply activity pairs.

System.ServiceModel.Activities.Tracking

It holds classes used to create tracking records for a workflow service instance. Tracking records are created by the workflow runtime during the execution of a workflow instance, and are sent to registered tracking participants.

System.ServiceModel.Activities.Tracking.Configuration

It holds classes used to configure workflow tracking. These classes enable you to specify the tracking information you want your workflow to generate.

System.ServiceModel.Channels

It holds the types required to construct and modify the messages used by clients and services to communicate with each other, the types of channels used to exchange messages, the channel factories and channel listeners used to construct those channels, and the binding elements used to configure them.

System.ServiceModel.ComIntegration

It holds the types necessary to integrate Windows Communication Foundation (WCF) service and client applications with COM components.

System.ServiceModel.Configuration

It holds types used by the Windows Communication Foundation (WCF) infrastructure to convert XML into Common Language Runtime (CLR) types.

System.ServiceModel.Description

It holds the types requires to construct and modify descriptions of services, contract, and endpoints that are used to build service runtimes and to export metadata.

System.ServiceModel.Diagnostics

It holds an enumeration that is used to configure performance counters for diagnostic purposes.

System.ServiceModel.Discovery

It holds the types required for the creation and use of discoverable services.

System.ServiceModel.Discovery.Configuration

It holds classes that enable you to configure discovery settings in a configuration file.

System.ServiceModel.Discovery.Version11

It holds the classes required to create and use discoverable services. These classes implement the WS-Discovery version 1.1 protocol.

System.ServiceModel.Discovery.VersionApril2005

It holds the classes required to create and use discoverable services. These classes implement the April 2005 version of the WS-Discovery protocol.

System.ServiceModel.Discovery.VersionCD1

It holds the classes required to create and use discoverable services. These classes implement the Committee Draft 1 version of the WS-Discovery protocol.

System.ServiceModel.Dispatcher

It holds the types necessary to modify the run-time execution behavior of service and client applications.

System.ServiceModel.MsmqIntegration

It holds classes for Microsoft Message Queuing Service (MSMQ) integration, which enables communication between MSMQ applications and Windows Communication Foundation (WCF) applications.

System.ServiceModel.PeerResolvers

It holds classes that enable developers to customize and extend the Peer Name Resolution Protocol (PNRP) service.

System.ServiceModel.Persistence

It holds classes that allow workflow services (WCF services implemented as workflows) to be persisted into the persistence store.

System.Activities.Expressions

It holds classes and expression activities that support the use of expressions in a workflow.

System.Activities.Hosting

It holds classes that provide the base support for hosting and executing a workflow.

System.Activities.Persistence

It holds classes for capturing an object’s state independent of process or machine information.

System.Activities.Presentation

It holds base activity designer classes used to create custom activity designers.

System.Activities.Presentation.Converters

It offers converts for arguments, UI property data, and items in the editing model of the Windows Workflow Foundation.

System.Activities.Presentation.Debug

It holds classes that provide breakpoint management for a debugging process.

System.Activities.Presentation.Hosting

It holds classes that enable the host to interact with assemblies, commands, and imported namespaces.

System.Activities.Presentation.Metadata

It holds  classes that enable you to work with custom attributes of elements.

System.Activities.Presentation.Model

It holds classes that enable you to work with items in the model tree of the designer, such as accessing the model items properties and attached properties. Also provides functionality to manage the model tree.

System.Activities.Presentation.PropertyEditing

It holds classes that enable updating properties by providing property editors, category editors, and access to properties, property values, and filters.

System.Activities.Presentation.Services

It holds classes that enable interacting with the model tree to perform tasks such as creating and locating model items, and mapping view items with model items.

System.Activities.Presentation.Toolbox

It holds support for classifying and using tools when rehosting outside of Visual Studio 2010.

System.Activities.Presentation.Validation

It holds classes that provide activity validation functionality for activities.

System.Activities.Presentation.View

It holds functionality related to the view elements in the workflow designer, including accessing and creating view elements, accessing commands, working with the view state, selections, and the expression textbox.

System.Activities.Statements

It holds activities that can be used to create workflows, for flow control, interacting with collections and variables, exceptions, compensation, transactions, and interacting with legacy workflows.

System.Activities.Tracking

It holds classes used to create and interact with workflow tracking records.

System.Activities.Validation

It holds classes used for custom activity validation.

System.Activities.XamlIntegration

It holds classes that provide support for the serialization of activities into XAML.

System.AddIn

It holds an attribute for identifying add-ins.

System.AddIn.Contract

It holds types that provide the basis for communication between components that are updated independently.

System.AddIn.Contract.Automation

It holds types that components use to access type information and invoke type members.

System.AddIn.Contract.Collections

It holds types used to implement collection classes for add-in development.

System.AddIn.Hosting

It holds types for discovering, registering, activating, and controlling add-ins.

System.AddIn.Pipeline

It holds classes for constructing the communication pipeline between a host application and an add-in.

System.CodeDom

It holds classes that can be used to represent the elements and structure of a source code document. These elements can be used to model the structure of a source code document that can be output as source code in a supported language using the functionality provided by the System.CodeDom.Compiler namespace.

System.CodeDom.Compiler

It holds types for managing the generation and compilation of source code in supported programming languages. Code generators can each produce source code in a particular programming language based on the structure of Code Document Object Model (CodeDOM) source code models consisting of elements provided by the System.CodeDom namespace.

System.Collections

It holds interfaces and classes that define various collections of objects, such as lists, queues, bit arrays, hashtables and dictionaries.

System.Collections.Concurrent

It holds interfaces and classes that define various collection objects for concurrent processing.

System.Collections.Generic

It holds interfaces and classes that define generic collections, which enable users to create strongly typed collections that provide better type safety and performance than non-generic strongly typed collections.

System.Collections.ObjectModel

It holds classes that can be used as collections in the object model of a reusable library. Use these classes when properties or methods return collections.

System.Collections.Specialized

It holds specialized and strongly typed collections; for example, a linked list dictionary, a bit vector, and collections that contain only strings.

System.ComponentModel

It holds classes that are used to implement the run-time and design-time behavior of components and controls. This namespace includes the base classes and interfaces for implementing attributes and type converters, binding to data sources, and licensing components.

System.ComponentModel.Composition

It holds classes that constitute the majority of the Managed Extensibility Framework (MEF).

System.ComponentModel.Composition.Hosting

It holds classes for MEF that are useful to developers of extensible applications, or hosts.

System.ComponentModel.Composition.Primitives

It holds the primitive types underlying the MEF programming model.

System.ComponentModel.Composition.ReflectionModel

It holds types for the Managed Extensibility Framework (MEF) that are useful to developers using a reflection-based programming model.

System.ComponentModel.DataAnnotations

It holds attribute classes that are used to define metadata for ASP.NET Dynamic Data controls.

System.ComponentModel.Design

It holds classes that developers can use to build custom design-time behavior for components and user interfaces for configuring components at design time. The design time environment provides systems that enable developers to arrange components and configure their properties.

System.ComponentModel.Design.Data

It holds classes for implementing design-time behavior of data-related components.

System.ComponentModel.Design.Serialization

It holds types that support customization and control of serialization at design time.

System.Configuration

It holds the types that provide the programming model for handling configuration data.

System.Configuration.Assemblies

It holds classes that are used to configure an assembly.

System.Configuration.Install

It holds classes that enable you to write custom installers for your own components. The Installer class is the base class for all custom installers in the .NET Framework.

System.Configuration.Provider

It holds the base classes shared by both server and client applications to support a pluggable model to easily add or remove functionality.

System.Data

It holds classes that constitute most of the ADO.NET architecture. The ADO.NET architecture enables you to build components that efficiently manage data from multiple data sources.

System.Data.Common

It holds classes shared by the .NET Framework data providers. A .NET Framework data provider describes a collection of classes used to access a data source, such as a database, in the managed space.

System.Data.Common.CommandTrees

It holds classes to build expressions that make up a command tree.

System.Data.Design

It holds classes that can be used to generate a custom typed dataset.

System.Data.Entity.Design

It holds classes to generate Entity Data Model (EDM) files and object source code.

System.Data.Entity.Design.AspNet

It holds the Entity Data Model (EDM) build providers for the ASP.NET build environment.

System.Data.Entity.Design.PluralizationServices

It holds types for changing words from singular to plural form, and vice versa.

System.Data.EntityClient

It holds the .NET Framework Data Provider for the Entity Framework.

System.Data.Linq

It holds classes that support interaction with relational databases in LINQ to SQL applications.

System.Data.Linq.Mapping

It holds classes that are used to generate a LINQ to SQL object model that represents the structure and content of a relational database.

System.Data.Mapping

It holds types for storing data mapping information.

System.Data.Metadata.Edm

It holds a set of types that represent concepts throughout the models used by the Entity Framework and a set of classes that help applications work with metadata.

System.Data.Objects

It holds classes that provide access to the core functionality of Object Services.

System.Data.Objects.DataClasses

It holds classes that are base classes for types that are defined in an Entity Data Model (EDM), base classes for the types that are returned by navigation properties, and classes that define attributes that map common language runtime (CLR) objects to types in the conceptual model.

System.Data.Objects.SqlClient

It holds a type that contains common language runtime (CLR) methods that translate to database functions.

System.Data.Odbc

It holds classes that encapsulate the .NET Framework Data Provider for ODBC, which describes a collection of classes used to access an ODBC data source in the managed space.

System.Data.OleDb

It holds classes that encapsulate the .NET Framework Data Provider for OLE DB, which describes a collection of classes used to access an OLE DB data source in the managed space.

System.Data.OracleClient

It holds classes that encapsulate the .NET Framework Data Provider for Oracle, which describes a collection of classes used to access an Oracle data source in the managed space.

System.Data.Services

It holds access to classes used to build WCF Data Services.

System.Data.Services.BuildProvider

It holds classes that generate C# or Visual Basic code for a WCF Data Services client application based on the metadata returned by the data service.

System.Data.Services.Client

It holds the .NET Framework Client library that applications can use to interact with WCF Data Services.

System.Data.Services.Common

It holds a class that denotes the key property or properties of an entity.

System.Data.Services.Providers

It holds a series of interfaces that are implemented to define a custom data service provider for WCF Data Services.

System.Data.Sql

It holds classes that support SQL Server-specific functionality. The API extensions in this class add to the .NET Framework Data Provider for SQL Server (System.Data.SqlClient).

System.Data.SqlClient

It holds classes that encapsulate the .NET Framework Data Provider for SQL Server. The .NET Framework Data Provider for SQL Server describes a collection of classes used to access a SQL Server database in the managed space.

System.Data.SqlTypes

It holds classes for native data types within SQL Server. These classes provide a faster alternative to other data types. Using the classes in this namespace helps prevent type conversion errors caused in situations where loss of precision could occur. Because other data types are converted to and from SqlTypes behind the scenes, explicitly creating and using objects within this namespace results in faster code as well.

System.Deployment.Application

It holds types to create custom upgrade behavior in ClickOnce applications.

System.Device.Location

It holds classes that provide a single API to encapsulate the multiple location providers on a computer and support seamless prioritization and transitioning between them. An application developer who uses this API does not need to know which location-sensing technologies are available on a particular computer and is freed from the burden of tailoring an application to a specific hardware configuration

System.Diagnostics

It holds classes that enable you to interact with system processes, event logs, and performance counters. This namespace also provides classes that let you debug your application and trace the execution of your code.

System.Diagnostics.CodeAnalysis

It holds classes for interaction with code analysis tools. Code analysis tools are used to analyze code for conformance to coding conventions such as naming or security rules.

System.Diagnostics.Contracts

It holds static classes for representing program constructs such as preconditions, postconditions, and invariants.

System.Diagnostics.Contracts.Internal

It holds classes that the binary rewriter can use to handle a contract failure.

System.Diagnostics.Design

It holds classes that can be used to extend design-time support for application monitoring and instrumentation.

System.Diagnostics.Eventing

It holds types to support implementation of an application on Windows Vista. The instrumentation, when enabled, logs event data to the Event Tracing for Windows (ETW) tracing subsystem.

System.Diagnostics.Eventing.Reader

It holds types to support reading from and managing event logs.

System.Diagnostics.PerformanceData

It holds classes that are used to provide counter data, which expose performance metrics to consumers.

System.Diagnostics.SymbolStore

It holds classes that enable you to read and write debug symbol information, such as source line to Microsoft intermediate language (MSIL) maps. Compilers targeting the .NET Framework can store the debug symbol information into programmer’s database (PDB) files. Debuggers and code profiler tools can read the debug symbol information at run time.

System.DirectoryServices

It holds easy access to Active Directory from managed code. The namespace contains two component classes,DirectoryEntry and DirectorySearcher, which use the Active Directory Services Interfaces (ADSI) technology. ADSI is the set of interfaces that Microsoft provides as a flexible tool for working with a variety of network providers. ADSI gives the administrator the ability to locate and manage resources on a network with relative ease, regardless of the network’s size.

The .NET Framework class library is a library of classes, interfaces, and value types that provides access to system functionality and is designed to be the foundation on which .NET Framework applications, components, and controls are built.

Namespaces

The .NET Framework class library provides the following namespaces, which are documented in detail in this reference.

Accessibility

It holds types that are part of a managed wrapper for the Component Object Model (COM) accessibility interface.

Microsoft.Aspnet.Snapin

It holds classes that are necessary for the ASP.NET management console application to interact with the Microsoft Management Console (MMC).

Microsoft.Build.BuildEngine

It holds the classes that represent the MSBuild engine.

Microsoft.Build.Construction

It holds types that the MSBuild object model uses to construct project roots with unevaluated values.

Microsoft.Build.Conversion

It holds types that Visual Studio uses to convert project files.

Microsoft.Build.Debugging

It holds types for managing the debugger.

Microsoft.Build.Evaluation

It holds types that the MSBuild object model uses to evaluate projects.

Microsoft.Build.Exceptions

It holds exception types used by the MSBuild engine.

Microsoft.Build.Execution

It holds types that the MSBuild object model uses to build projects.

Microsoft.Build.Framework

It holds classes that make up the tasks, loggers, and events of MSBuild.

Microsoft.Build.Framework.XamlTypes

It holds classes used to represent XAML types parsed from files, rules, and other sources.

Microsoft.Build.Logging

It holds types used for logging the progress of a build.

Microsoft.Build.Tasks

It holds the implementation of all tasks shipping with MSBuild.

Microsoft.Build.Tasks.Deployment.Bootstrapper

It holds classes used internally by MSBuild.

Microsoft.Build.Tasks.Deployment.ManifestUtilities

It holds classes used internally by MSBuild.

Microsoft.Build.Tasks.Hosting

It holds classes used internally by MSBuild.

Microsoft.Build.Tasks.Windows

It holds classes used internally by MSBuild.

Microsoft.Build.Tasks.Xaml

It holds types that process XAML.

Microsoft.Build.Utilities

It offers helper classes that you can use to create your own MSBuild loggers and tasks.

Microsoft.CSharp

It holds classes that support compilation and code generation using the C# language.

Microsoft.CSharp.RuntimeBinder

It holds types that support interoperation between the dynamic language runtime (DLR) and C#.

Microsoft.Data.Entity.Build.Tasks

It holds types that represent MSBuild tasks used by the ADO.NET Entity Data Model Designer.

Microsoft.JScript

It holds classes that support compilation and code generation using the JScript language.

Microsoft.SqlServer.Server

It holds classes that are specific to the integration of the.NET Framework common language runtime (CLR) component into Microsoft SQL Server, and the SQL Server database engine process execution environment.

Microsoft.VisualBasic

It holds classes that support compilation and code generation using the Visual Basic language.

Microsoft.VisualBasic.Activities

It holds classes that provide Visual Basic expressions that can be bound to In and Out arguments, and Visual Basic expression settings.

Microsoft.VisualBasic.Activities.XamlIntegration

It holds a type converter and XAML serializer for Microsoft.VisualBasic.Activities.VisualBasicSettings.

Microsoft.VisualBasic.ApplicationServices

It holds types that support the Visual Basic Application Model and provide access to application information.

Microsoft.VisualBasic.Compatibility.VB6

It holds types used by tools for upgrading from Visual Basic 6.0 to Visual Basic .NET.

Microsoft.VisualBasic.CompilerServices

It holds internal-use only types that support the Visual Basic compiler.

Microsoft.VisualBasic.Devices

It holds types that support the My objects related to devices in Visual Basic.

Microsoft.VisualBasic.FileIO

It holds types that support the My file system object in Visual Basic.

Microsoft.VisualBasic.Logging

It holds types that support the My logging objects in Visual Basic and provides a simple log listener that directs logging output to file.

Microsoft.VisualBasic.MyServices

It holds types that support My in Visual Basic.

Microsoft.VisualBasic.MyServices.Internal

It holds internal-use only types that support My in Visual Basic.

Microsoft.VisualC

It holds types that support the Visual C++ compiler.

Microsoft.VisualC.StlClr

It holds types that implement the STL/CLR Library.

Microsoft.VisualC.StlClr.Generic

It holds types that implement the generic interface to the STL/CLR Library.

Microsoft.Win32

It offers two types of classes: those that handle events raised by the operating system and those that manipulate the system registry.

Microsoft.Win32.SafeHandles

It holds classes that are abstract derivations of safe handle classes that provide common functionality supporting file and operating system handles.

Microsoft.Windows.Themes

It offers exposure to the set of themes defined by Windows Presentation Foundation (WPF).

System

It holds fundamental classes and base classes that define commonly used value and reference data types, events and event handlers, interfaces, attributes, and processing exceptions. Other classes provide services supporting data type conversion, method parameter manipulation, mathematics, remote and local program invocation, application environment management, and supervision of managed and unmanaged applications.

System.Activities

It holds all the classes necessary to create and work with activities. The classes in this namespace enable you to define activities, the data flow into and out of activities, and variables.

System.Activities.Core.Presentation

It holds helper classes used in the default and extensibility scenarios for Windows Workflow Foundation.

System.Activities.Core.Presentation.Factories

It offers factories for creating activities that interact with collections and enable control flow in Windows Workflow Foundation.

System.Activities.Core.Presentation.Themes

It holds a class that is a collection of style configuration values used by the activity designers.

System.Activities.Debugger

It holds classes that provide support for debugging workflows.

System.Activities.DurableInstancing

It holds the SqlWorkflowInstanceStore class, which provides durability to workflow instances, and its helper classes.

System.Activities.ExpressionParser

It holds  classes that support the compilation of expressions.

DHTML Collections

This section contains a list of the collections exposed by the DHTML Object Model.

DHTML Constants

This section lists the constants in the DHTML Object Model.

DHTML Events

This section contains the events exposed by the DHTML Object Model.

DHTML Methods

This section contains a list of the methods exposed by the DHTML Object Model.

DHTML Objects

This section contains a list of the objects defined by DHTML.

DHTML Properties

This section contains a list of the properties in the DHTML Object Model.

HTML Character Sets

Character sets determine how the bytes that represent the text of your HTML document are translated to readable characters. Windows Internet Explorer interprets the bytes in your document according to the applied character set translations.

HTML Elements

This section contains a list of elements defined by HTML. The links take you to the element definitions, which contain the set of members for the element.

CSS Attributes: Index

This index lists all the supported Cascading Style Sheets (CSS) attributes by category, and indicates the version of Internet Explorer in which the attributes were first available.

CSS Length Units Reference

This section defines the supported length units for CSS

Color Table

Colors can be specified in HTML pages in two ways—by using numbers to denote an RGB color value, or by using a color name.

Command Identifiers

Command identifiers specify an action to take on the given object.

Default Behaviors Reference

Introduction to DHTML Behaviors provides a means for Web developers to extend the current Internet Explorer object model. A number of behaviors have been implemented as part of Microsoft Internet Explorer 5 and are referred to as default behaviors.

Language Codes

The following table lists all the possible language codes used to specify various system settings.

Tips and Tricks

As with any type of programming, writing bug-free, efficient scripts that meet your expectations takes a bit of work. The following sections provide some tips and hints to make that work take less time and go more smoothly.

Visual Filters and Transitions Reference

As of Internet Explorer 4.0, you can apply multimedia-style effects to your Web pages using visual filters and transitions. You can apply visual filters and transitions to standard HTML controls, such as text containers, images, and other windowless objects. Transitions are time-varying filters that create a transition from one visual state to another. By combining filters and transitions with basic scripting, you can create visually engaging and interactive documents.

Reference: http://msdn.microsoft.com/en-us/library/ms533050(v=VS.85).aspx

tabIndex

Sets or retrieves the index that defines the tab order for the object.

tableLayout

Sets or retrieves a string that indicates whether the table layout is fixed.

tabStop

Sets or retrieves whether an element behavior can receive focus and participate in the tabbing sequence.

tagName

Retrieves the tag name of the object.

tagUrn

Sets or gets the URN specified in the namespace declaration.

target

Sets or retrieves the window or frame at which to target content.

text

Sets or gets the text (foreground) color for the document body.

text

Sets or retrieves the text string specified by the option tag.

text

Sets or retrieves the text contained within the range.

text

Retrieves or sets the text of the object as a string.

textAlign

Sets or retrieves whether the text in the object is left-aligned, right-aligned, centered, or justified.

textAlignLast

Sets or retrieves how to align the last line or only line of text in the object.

textAutospace

Sets or retrieves the autospacing and narrow space width adjustment of text.

textDecoration

Sets or retrieves a value that indicates whether the text in the object has blink, line-through, overline, or underline decorations.

textDecorationBlink

Sets or retrieves a Boolean value that indicates whether the object’s textDecoration property has a value of “blink.”

textDecorationLineThrough

Sets or retrieves a Boolean value indicating whether the text in the object has a line drawn through it.

textDecorationNone

Sets or retrieves the Boolean value indicating whether the textDecoration property for the object has been set to none.

textDecorationOverline

Sets or retrieves a Boolean value indicating whether the text in the object has a line drawn over it.

textDecorationUnderline

Sets or retrieves whether the text in the object is underlined.

textIndent

Sets or retrieves the indentation of the first line of text in the object.

textJustify

Sets or retrieves the type of alignment used to justify text in the object.

textKashidaSpace

Sets or retrieves the ratio of kashida expansion to white space expansion when justifying lines of text in theobject.

textOverflow

Sets or retrieves a value that indicates whether to render ellipses(…) to indicate text overflow.

textTransform

Sets or retrieves the rendering of the text in the object.

textUnderlinePosition

Sets or retrieves the position of the underline decoration that is set through the textDecoration property of the object.

tFoot

Retrieves the tFoot object of the table.

tHead

Retrieves the tHead object of the table.

timeout

Gets or sets the value of the timeout property.

timeout

Gets or sets the time-out value.

title

Sets or retrieves advisory information (a ToolTip) for the object.

title

Sets or retrieves the title of the style sheet.

toElement

Sets or retrieves a reference to the object toward which the user is moving the mouse pointer.

top

Sets or retrieves the position of the object relative to the top of the next positioned object in the document hierarchy.

top

Retrieves the topmost ancestor window.

top

Sets or retrieves the top coordinate of the rectangle surrounding the object content.

topMargin

Sets or gets the margin for the top of the page.

trueSpeed

Sets or retrieves whether the position of the marquee is calculated using the scrollDelay and scrollAmountproperties and the actual time elapsed from the last clock tick.

type

Gets the classification and default behavior of the button.

type

Sets or retrieves the content type of the resource designated by the value attribute.

type

Sets or retrieves the MIME type for the associated scripting engine.

type

Retrieves the type of selection.

type

Retrieves the Cascading Style Sheets (CSS) language in which the style sheet is written.

type

Retrieves the CSS language in which the style sheet is written.

type

Retrieves the type of control.

type

Sets or retrieves the style of the list.

type

Sets or retrieves the event name from the event object.

type

Sets or retrieves the MIME type of the object.

type

Retrieves or initially sets the type of input control represented by the object.

type

Retrieves the type of select control based on the value of the MULTIPLE attribute.

typeDetail

Retrieves the name of the selection type.

unicodeBidi

Sets or retrieves the level of embedding with respect to the bidirectional algorithm.

uniqueID

Retrieves an autogenerated, unique identifier for the object.

uniqueNumber

Retrieves the element’s unique number.

units

Sets or retrieves the height and width units of the embed object.

UNSELECTABLE

Specifies that an element cannot be selected.

updateInterval

Sets or retrieves the update interval for the screen.

url

Sets or retrieves the fully qualified URL of the document that fired the event.

url

Sets or retrieves the URL property that will be loaded after the specified time has elapsed.

URL

Sets or gets the URL for the current document.

URLUnencoded

Gets the URL for the document, stripped of any character encoding.

urn

Sets or gets a URN for a target document.

useMap

Sets or retrieves the URL, often with a bookmark extension (#name), to use as a client-side image map.

userAgent

Retrieves the User Agent.

userAgent

Retrieves a string equivalent to the HTTP user-agent request header.

userLanguage

Retrieves the operating system’s natural language setting.

vAlign

Sets or retrieves whether the caption appears at the top or bottom of the table.

vAlign

Sets or retrieves how text and other content are vertically aligned within the object that contains them.

value

Sets or gets the value of the object.

value

Retrieves the file name of the input object after the text is set by user input.

value

Sets or retrieves the value of a list item.

value

Sets or retrieves the value of an input parameter for an element.

value

Retrieves or sets the text in the entry field of the textArea element.

value

Sets or retrieves the default or selected value of the control.

value

Sets or retrieves the value which is returned to the server when the form control is submitted.

value

Sets or retrieves the displayed value for the control object. This value is returned to the server when the control object is submitted.

valueType

Sets or retrieves the data type of the value attribute.

vcard_name

Sets or retrieves the vCard value of the object to use for the AutoComplete box.

version

Retrieves the version vector as a string.

version

Sets or retrieves the Document Type Definition (DTD) version that governs the current document.

version

Retrieves a string representing the version in the format “N.nnnn platform”, where N is an integer representing the major version number, nnnn is a number of characters representing the minor version number, and platform is the platform (win32, mac, alpha, and so on).

verticalAlign

Sets or retrieves the vertical alignment of the object.