Input: [Name] Subtract [Description]

Output: Returns a new TimeSpan object whose value is the difference between the specified TimeSpan object and this instance.


Input: [Name] ToString() [Description]

Output: Converts the value of the current TimeSpan object to its equivalent string representation. (Overrides ValueType.ToString().)


Input: [Name] ToString(String) [Description]

Output: Converts the value of the current TimeSpan object to its equivalent string representation by using the specified format.


Input: [Name] ToString(String, IFormatProvider) [Description]

Output: Converts the value of the current TimeSpan object to its equivalent string representation by using the specified format and culture-specific formatting information.


Input: [Name] TryParse(String, TimeSpan) [Description]

Output: Converts the string representation of a time interval to its TimeSpan equivalent and returns a value that indicates whether the conversion succeeded.


Input: [Name] TryParse(String, IFormatProvider, TimeSpan) [Description]

Output: Converts the string representation of a time interval to its TimeSpan equivalent by using the specified culture-specific formatting information, and returns a value that indicates whether the conversion succeeded.


Input: [Name] TryParseExact(String, String, IFormatProvider, TimeSpan) [Description]

Output: Converts the string representation of a time interval to its TimeSpan equivalent by using the specified format and culture-specific format information, and returns a value that indicates whether the conversion succeeded. The format of the string representation must match the specified format exactly.


Input: [Name] TryParseExact(String, String[], IFormatProvider, TimeSpan) [Description]

Output: Converts the specified string representation of a time interval to its TimeSpan equivalent by using the specified formats and culture-specific format information, and returns a value that indicates whether the conversion succeeded. The format of the string representation must match one of the specified formats exactly.


Input: [Name] TryParseExact(String, String, IFormatProvider, TimeSpanStyles, TimeSpan) [Description]

Output: Converts the string representation of a time interval to its TimeSpan equivalent by using the specified format, culture-specific format information, and styles, and returns a value that indicates whether the conversion succeeded. The format of the string representation must match the specified format exactly.


Input: [Name] TryParseExact(String, String[], IFormatProvider, TimeSpanStyles, TimeSpan) [Description]

Output: Converts the specified string representation of a time interval to its TimeSpan equivalent by using the specified formats, culture-specific format information, and styles, and returns a value that indicates whether the conversion succeeded. The format of the string representation must match one of the specified formats exactly.


Input: [Value] native [Description]

Output: Produces native-mode bulk copy program output of all tables. Not supported for Oracle Publishers.


Input: [Value] character [Description]

Output: Produces character-mode bulk copy program output of all tables. For an Oracle Publisher, character is valid only for snapshot replication.


Input: [Value] concurrent [Description]

Output: Produces native-mode bulk copy program output of all tables but does not lock tables during the snapshot. Only supported for transactional publications. Not supported for Oracle Publishers.


Input: [Value] concurrent_c [Description]

Output: Produces character-mode bulk copy program output of all tables but does not lock tables during the snapshot. Only supported for transactional publications.


Input: [Value] database snapshot [Description]

Output: Produces native-mode bulk copy program output of all tables from a database snapshot. This option requires SQL Server 2005 Enterprise Edition Service Pack 2 or a later version.


Input: [Value] database snapshot character [Description]

Output: Produces character-mode bulk copy program output of all tables from a database snapshot. This option requires SQL Server 2005 Enterprise Edition Service Pack 2 or a later version.


Input: [Value] NULL (default) [Description]

Output: Defaults to native for Microsoft SQL Server Publishers. For non-SQL Server Publishers, defaults to character when the value of repl_freq is Snapshot and to concurrent_c for all other cases.


Input: [Term] Closer Look: Understanding Properties, Methods, and Events [Definition]

Output: How properties, methods, and events work.

Introduction to the Visual Basic Programming Language


Input: [Term] Closer Look: Data Types [Definition]

Output: How data is stored using the different types of variables.

Introduction to the Visual Basic Programming Language


Input: [Term] Closer Look: Converting from One Variable Type to Another [Definition]

Output: How to convert data from one type to another, along with some common pitfalls of this process.

Introduction to the Visual Basic Programming Language


Input: [Term] Closer Look: Using Do...While and Do...Until to Repeat Until a Condition is Met [Definition]

Output: How to use the Do...While and Do...Until statements to repeat code based on certain conditions.

Introduction to the Visual Basic Programming Language


Input: [Term] Closer Look: Using Select Case to Decide Between Multiple Choices [Definition]

Output: How to run code based on multiple conditions, where there are many choices.

Introduction to the Visual Basic Programming Language


Input: [Term] Visual Basic Guided Tour [Definition]

Output: More of what you can do with the Visual Basic 2005 programming language

Introduction to the Visual Basic Programming Language


Input: [Description] Represents a placeholder (bookmark) within an event stream. You can use the placeholder to mark a position and return to this position in a stream of events. An instance of this object can be obtained from an EventRecord object, in which case it corresponds to the position of that event record. [Class]

Output: EventBookmark


Input: [Description] Represents a keyword for an event. Keywords are defined in an event provider and are used to group the event with other similar events (based on the usage of the events). [Class]

Output: EventKeyword


Input: [Description] Contains an event level that is defined in an event provider. The level signifies the severity of the event. [Class]

Output: EventLevel


Input: [Description] Contains static information and configuration settings for an event log. Many of the configurations settings were defined by the event provider that created the log. [Class]

Output: EventLogConfiguration


Input: [Description] Represents the base class for all the exceptions that are thrown when an error occurs while reading event log related information. [Class]

Output: EventLogException


Input: [Description] Allows you to access the run-time properties of active event logs and event log files. These properties include the number of events in the log, the size of the log, a value that determines whether the log is full, and the last time the log was written to or accessed. [Class]

Output: EventLogInformation


Input: [Description] Represents the exception thrown when an event provider publishes invalid data in an event. [Class]

Output: EventLogInvalidDataException


Input: [Description] Represents a link between an event provider and an event log that the provider publishes events into. This object cannot be instantiated. [Class]

Output: EventLogLink


Input: [Description] Represents the exception that is thrown when a requested event log (usually specified by the name of the event log or the path to the event log file) does not exist. [Class]

Output: EventLogNotFoundException


Input: [Description] Contains an array of strings that represent XPath queries for elements in the XML representation of an event, which is based on the Event Schema. The queries in this object are used to extract values from the event. [Class]

Output: EventLogPropertySelector


Input: [Description] Represents the exception that is thrown when a specified event provider name references a disabled event provider. A disabled event provider cannot publish events. [Class]

Output: EventLogProviderDisabledException


Input: [Description] Represents a query for events in an event log and the settings that define how the query is executed and on what computer the query is executed on. [Class]

Output: EventLogQuery


Input: [Description] Enables you to read events from an event log based on an event query. The events that are read by this object are returned as EventRecord objects. [Class]

Output: EventLogReader


Input: [Description] Represents an exception that is thrown when an error occurred while reading, querying, or subscribing to the events in an event log. [Class]

Output: EventLogReadingException


Input: [Description] Contains the properties of an event instance for an event that is received from an EventLogReader object. The event properties provide information about the event such as the name of the computer where the event was logged and the time that the event was created. [Class]

Output: EventLogRecord


Input: [Description] Used to access the Event Log service on the local computer or a remote computer so you can manage and gather information about the event logs and event providers on the computer. [Class]

Output: EventLogSession


Input: [Description] Contains the status code or error code for a specific event log. This status can be used to determine if the event log is available for an operation. [Class]

Output: EventLogStatus


Input: [Description] Allows you to subscribe to incoming events. Each time a desired event is published to an event log, the EventRecordWritten event is raised, and the method that handles this event will be executed. [Class]

Output: EventLogWatcher


Input: [Description] Contains the metadata (properties and settings) for an event that is defined in an event provider. [Class]

Output: EventMetadata


Input: [Description] Contains an event opcode that is defined in an event provider. An opcode defines a numeric value that identifies the activity or a point within an activity that the application was performing when it raised the event. [Class]

Output: EventOpcode


Input: [Description] Contains the value of an event property that is specified by the event provider when the event is published. [Class]

Output: EventProperty


Input: [Description] Defines the properties of an event instance for an event that is received from an EventLogReader object. The event properties provide information about the event such as the name of the computer where the event was logged and the time the event was created. This class is an abstract class. The EventLogRecord class implements this class. [Class]

Output: EventRecord


Input: [Description] When the EventRecordWritten event is raised, an instance of this object is passed to the delegate method that handles the event. This object contains the event that was published to the event log or the exception that occurred when the event subscription failed. [Class]

Output: EventRecordWrittenEventArgs


Input: [Description] Contains an event task that is defined in an event provider. The task identifies a portion of an application or a component that publishes an event. A task is a 16-bit value with 16 top values reserved. [Class]

Output: EventTask


Input: [Description] Contains static information about an event provider, such as the name and id of the provider, and the collection of events defined in the provider. [Class]

Output: ProviderMetadata


Input: [uCommand] HELP_COMMAND [dwData] Address of a string that specifies the name of the help macro(s) to run. If the string specifies multiple macro names, the names must be separated by semicolons. You must use the short form of the macro name for some macros because Windows Help does not support the long name. [Action]

Output: Executes a help macro or macro string.


Input: [uCommand] HELP_CONTENTS [dwData] Ignored; set to 0. [Action]

Output: Displays the topic specified by the Contents option in the [OPTIONS] section of the .hpj file. This command is for backward compatibility. New applications should provide a .cnt file and use the HELP_FINDER command.


Input: [uCommand] HELP_CONTEXT [dwData] Contains the context identifier for the topic. [Action]

Output: Displays the topic identified by the specified context identifier defined in the [MAP] section of the .hpj file.


Input: [uCommand] HELP_CONTEXTMENU [dwData] Address of an array of DWORD pairs. The first DWORD in each pair is the control identifier, and the second is the context identifier for the topic. The array must be terminated by a pair of zeros {0,0}. If you do not want to add help to a particular control, set its context identifier to -1. [Action]

Output: Displays the Help menu for the selected window, then displays the topic for the selected control in a pop-up window.


Input: [uCommand] HELP_CONTEXTPOPUP [dwData] Contains the context identifier for a topic. [Action]

Output: Displays the topic identified by the specified context identifier defined in the [MAP] section of the .hpj file in a pop-up window.


Input: [uCommand] HELP_FINDER [dwData] Ignored; set to 0. [Action]

Output: Displays the Help Topics dialog box.


Input: [uCommand] HELP_FORCEFILE [dwData] Ignored; set to 0. [Action]

Output: Ensures that Windows Help is displaying the correct help file. If the incorrect help file is being displayed, Windows Help opens the correct one; otherwise, there is no action.


Input: [uCommand] HELP_HELPONHELP [dwData] Ignored; set to 0. [Action]

Output: Displays help on how to use Windows Help, if the Winhlp32.hlp file is available.


Input: [uCommand] HELP_INDEX [dwData] Ignored; set to 0. [Action]

Output: Displays the topic specified by the Contents option in the [OPTIONS] section of the .hpj file. This command is for backward compatibility. New applications should use the HELP_FINDER command.


Input: [uCommand] HELP_KEY [dwData] Address of a keyword string. Multiple keywords must be separated by semicolons. [Action]

Output: Displays the topic in the keyword table that matches the specified keyword, if there is an exact match. If there is more than one match, displays the index with the topics listed in the Topics Found list box.


Input: [uCommand] HELP_MULTIKEY [dwData] Address of a MULTIKEYHELP structure that specifies a table footnote character and a keyword. [Action]

Output: Displays the topic specified by a keyword in an alternative keyword table.


Input: [uCommand] HELP_PARTIALKEY [dwData] Address of a keyword string. Multiple keywords must be separated by semicolons. [Action]

Output: Displays the topic in the keyword table that matches the specified keyword, if there is an exact match. If there is more than one match, displays the Topics Found dialog box. To display the index without passing a keyword, use a pointer to an empty string.


Input: [uCommand] HELP_QUIT [dwData] Ignored; set to 0. [Action]

Output: Informs Windows Help that it is no longer needed. If no other applications have asked for help, Windows closes Windows Help.


Input: [uCommand] HELP_SETCONTENTS [dwData] Contains the context identifier for the Contents topic. [Action]

Output: Specifies the Contents topic. Windows Help displays this topic when the user clicks the Contents button if the help file does not have an associated .cnt file.


Input: [uCommand] HELP_SETPOPUP_POS [dwData] Contains the position data. Use the MAKELONG macro to concatenate the horizontal and vertical coordinates into a single value. The pop-up window is positioned as if the mouse cursor were at the specified point when the pop-up window was invoked. [Action]

Output: Sets the position of the subsequent pop-up window.


Input: [uCommand] HELP_SETWINPOS [dwData] Address of a HELPWININFO structure that specifies the size and position of either a primary or secondary help window. [Action]

Output: Displays the Windows Help window, if it is minimized or in memory, and sets its size and position as specified.


Input: [uCommand] HELP_TCARD [dwData] Depends on the command with which this command is combined. [Action]

Output: Indicates that a command is for a training card instance of Windows Help. Combine this command with other commands using the bitwise OR operator.


Input: [uCommand] HELP_WM_HELP [dwData] Address of an array of DWORD pairs. The first DWORD in each pair is a control identifier, and the second is a context identifier for a topic. The array must be terminated by a pair of zeros {0,0}. If you do not want to add Help to a particular control, set its context identifier to -1. [Action]

Output: Displays the topic for the control identified by the hWndMain parameter in a pop-up window.


Input: [Supported feature] Multiple screen resolutions [Description]

Output: You can use the Windows Phone 8 emulator to test your app on the following screen resolutions: WVGA (800 × 480) WXGA (1280 × 768) 720p (1280 × 720) For more info, see Multi-resolution apps for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Screen configuration options [Description]

Output: Windows Phone Emulator supports the following screen configuration options: Changing from portrait to landscape mode. For more info, see How to change the orientation in the emulator for Windows Phone 8. Changing the zoom setting to fit the emulator to your desktop screen. For more info, see How to adjust the zoom setting in the emulator for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Memory-constrained devices [Description]

Output: You can use the emulator to test your app on images that emulate the following memory-constrained devices: Emulator WVGA 512MB, for apps that target Windows Phone 8. Emulator WVGA 512MB, Emulator 7.8 256MB, and Emulator 7.1 256MB, for apps that target Windows Phone OS 7.1. For more info, see Developing apps for lower-memory phones for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Networking [Description]

Output: Networking support is integrated with Windows Phone Emulator. Networking is enabled by default. You do not have to install network drivers for Windows Phone Emulator or configure networking options manually in most environments. For more info, see Networking in the Windows Phone 8 Emulator. You can also use Simulation Dashboard to simulate a poor network connection. For more info, see How to simulate a low-bandwidth connection or poor signal for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Language and region settings [Description]

Output: You can change the display language and region settings in Windows Phone Emulator for testing purposes. For more info, see How to test region settings in the emulator for Windows Phone 8 and How to test a localized app for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Application lifecycle and tombstoning [Description]

Output: You can test the behavior or your app when it is deactivated or tombstoned. For more info, see How to test app state changes for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Local folder (previously known as isolated storage) [Description]

Output: Data in isolated storage persists while the emulator is running, but is lost once the emulator closes. For more info about isolated storage, see Quickstart: Working with files and folders in Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Camera and video (with limitations) [Description]

Output: For more info about support for camera and video in Windows Phone 8 Emulator, see the section titled “Using the emulator” in each of the following topics: Capturing photos for Windows Phone 8 Capturing video for Windows Phone 8 This feature is not supported in the Windows Phone 7.1 Emulator.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Location (GPS) simulation [Description]

Output: For more info, see How to test apps that use location data for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Accelerometer simulation [Description]

Output: For more info, see How to test apps that use the accelerometer for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Multi-touch [Description]

Output: Requires a host computer that supports multi-touch input. Simulation of multi-touch by using the mouse is not supported in the emulator.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Microphone [Description]

Output: Requires and uses the microphone on the host computer.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Proximity (NFC) [Description]

Output: You can test proximity with the help of an additional download. For more info, see Proximity for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] In-app purchase [Description]

Output: You can test In-App Purchase with the help of an additional download. For more info, see In-app purchase testing for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Copy-and-paste [Description]

Output: For more info, see How to test copy-and-paste in the emulator for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Lock screen [Description]

Output: For more info, see How to simulate the lock screen for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Supported feature] Notifications [Description]

Output: For more info, see How to simulate a reminder for Windows Phone 8.

Windows Phone Emulator for Windows Phone 8


Input: [Area] Description [Report Designer] Report Designer in Business Intelligence Development Studio is a report authoring environment that is hosted in Microsoft Visual Studio. Use Report Designer project and solution files to organize and maintain a master copy of report definitions, report parts, shared data sources, shared datasets, and resource files such as images and ESRI shapefiles for maps. [Report Builder 3.0]

Output: Report Builder is a report authoring environment for business users who prefer to work in the Microsoft Office environment. You work with one report at a time. You can modify a published report directly from a report server. You can quickly build a report by adding items from the Report Part Gallery provided by report designers from your organization.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Getting Data [Report Designer] Publish a shared data source or shared dataset to a report server. To preview a report, define credentials that work with the local computer. After you publish a shared data source, you might need to modify the credentials to work from the report server. From project properties, you can control whether to publish shared data sources and shared datasets. Use configuration properties to create multiple sets of project properties for production or debug modes. Add a custom data extension and install it locally and on the report server. [Report Builder 3.0]

Output: Navigate to a report server, and add a reference to a shared data source or shared dataset on the report server. Create shared datasets in Shared Dataset View, and save them to the report server. For an embedded (local) dataset, write a query or build a query by using the relational query designer. You can retrieve data from any built-in data source type locally or any report server data source type from the report server. Custom data sources on the client are not supported. To preview a report, credentials must be valid on the client to run dataset queries and on the server to preview a report.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Tables, Matrices, and Lists [Report Designer] Manually add a table, matrix, or list to a report from the toolbox or from the right-click menu. [Report Builder 3.0]

Output: Use the Tablix Wizard to add a table, matrix, or list to a report.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Report Parts [Report Designer] Mark items as report parts. Publish them when you deploy the project. [Report Builder 3.0]

Output: Select from a list report parts on the report server. Publish items in a report as report parts.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Charts, Sparklines, and Data Bars [Report Designer] Manually add a chart to a report from the toolbox or from the right-click menu. [Report Builder 3.0]

Output: Use the Chart Wizard to add chart to a report.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Maps [Report Designer] Include ESRI shapefiles as resources in your project and publish them to the report server. [Report Builder 3.0]

Output: Publish ESRI shapefiles to the report server first, and then add a reference to an ESRI file from your report.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Images, Text Boxes, Rectangles, and Lines [Report Designer] Include images as resources in your project and publish them to the report server. [Report Builder 3.0]

Output: Publish image files to the report server first, and then add a reference to the image from your report.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Formatting Report Items [Report Designer] Use Visual Studio toolbars to format items on the design surface. [Report Builder 3.0]

Output: Use tabs and groups on the Ribbon to format items on the design surface.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Filtering, Grouping, and Sorting [Report Designer] Manually create groups by dragging fields from the Report Data pane to the Table and Matrix row group and column group panes or to the Chart category and series panes. By default, sort expressions are set to group expressions. In Solution Explorer, in the Shared Datasets folder, set dataset filters, and save them in the project. When you deploy the project, the shared datasets are saved to the report server or SharePoint site. [Report Builder 3.0]

Output: In Report Design mode, create groups by using the Table/Matrix and Chart wizard. By default, sort expressions are set to group expressions. In Shared Dataset mode, set dataset filter options, and then save the shared dataset to the report server or SharePoint site.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Drillthrough, Drilldown, Subreports, and Nested Data Regions [Report Designer] In local mode, add references to reports in the project for drillthrough targets or subreports. The Table or Matrix Wizard is not available. Manually add an expand/collapse action to an item on the Text Box Properties dialog box or the Group Dialog box from a group displayed in the Grouping pane. [Report Builder 3.0]

Output: Drillthrough and subreports are supported only in server mode. Not supported in local mode. Add an expand/collapse action to an item by using the Table or Matrix Wizard.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Expressions [Report Designer] Write expressions in Visual Basic. The expression editor provides IntelliSense syntax support. Use the Output window to view warnings and compile-time error messages. Add references to .NET Framework assemblies or to custom assemblies that contain your custom code. [Report Builder 3.0]

Output: Use default expressions to display, group, and sort data in the report. You can write expressions in Microsoft Visual Basic, but there are fewer options for debugging than in Report Designer.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Value] ERROR_INVALID_PARAMETER [Meaning]

Output: Some arguments passed in are incorrect or contradicting.


Input: [Value] ERROR_SUCCESS [Meaning]

Output: The function completed and all products are successfully patched. ERROR_SUCCESS is returned only if all the products eligible for the patches are patched successfully. If none of the new patches are applicable, MsiApplyMultiplePatches returns ERROR_SUCCESS and product state remains unchanged.


Input: [Value] ERROR_SUCCESS_REBOOT_INITIATED [Meaning]

Output: The restart initiated by the last transaction terminated this call to MsiApplyMultiplePatches. All the target products may not have been patched.


Input: [Value] ERROR_SUCCESS_REBOOT_REQUIRED [Meaning]

Output: The restart required by the last transaction terminated this call to MsiApplyMultiplePatches. All target products may not have been patched.


Input: [Value] ERROR_PATCH_PACKAGE_OPEN_FAILED [Meaning]

Output: One of the patch packages provide could not be opened.


Input: [Value] ERROR_PATCH_PACKAGE_INVALID [Meaning]

Output: One of the patch packages provide is not a valid one.


Input: [Value] ERROR_PATCH_PACKAGE_UNSUPPORTED [Meaning]

Output: One of the patch packages is unsupported.


Input: [Value] Any error in Winerror.h [Meaning]

Output: Implies possible partial completion or that one or more transactions failed.


Input: [Member] Auto [Value] 1 [Description]

Output: Indicates that the camera automatically determines the best settings and exposure when capturing a photo.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Macro [Value] 2 [Description]

Output: Indicates that the camera optimizes for macro photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Portrait [Value] 3 [Description]

Output: Indicates that the camera optimizes for portrait photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Sport [Value] 4 [Description]

Output: Indicates that the camera optimizes for sports photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Snow [Value] 5 [Description]

Output: Indicates that the camera optimizes for photos that include snow.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Night [Value] 6 [Description]

Output: Indicates that the camera optimizes for night photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Beach [Value] 7 [Description]

Output: Indicates that the camera optimizes for beach photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Sunset [Value] 8 [Description]

Output: Indicates that the camera optimizes for sunset photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Candlelight [Value] 9 [Description]

Output: Indicates that the camera optimizes for candlelight photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Landscape [Value] 10 [Description]

Output: Indicates that the camera optimizes for photos of landscape.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] NightPortrait [Value] 11 [Description]

Output: Indicates that the camera optimizes for low-light portrait photos.

CameraSceneMode enumeration (Windows Phone)


Input: [Member] Backlit [Value] 12 [Description]

Output: Indicates that the camera optimizes for photos that are backlit.

CameraSceneMode enumeration (Windows Phone)


Input: [Area] Description [Report Builder 3.0] Report Builder is a report authoring environment for business users who prefer to work in the Microsoft Office environment. You work with one report at a time. You can modify a published report directly from a report server. You can quickly build a report by adding items from the Report Part Gallery provided by report designers from your organization. [Report Designer]

Output: Report Designer in Business Intelligence Development Studio is a report authoring environment that is hosted in Microsoft Visual Studio. Use Report Designer project and solution files to organize and maintain a master copy of report definitions, report parts, shared data sources, shared datasets, and resource files such as images and ESRI shapefiles for maps.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Getting Data [Report Builder 3.0] Navigate to a report server, and add a reference to a shared data source or shared dataset on the report server. Create shared datasets in Shared Dataset View, and save them to the report server. For an embedded (local) dataset, write a query or build a query by using the relational query designer. You can retrieve data from any built-in data source type locally or any report server data source type from the report server. Custom data sources on the client are not supported. To preview a report, credentials must be valid on the client to run dataset queries and on the server to preview a report. [Report Designer]

Output: Publish a shared data source or shared dataset to a report server. To preview a report, define credentials that work with the local computer. After you publish a shared data source, you might need to modify the credentials to work from the report server. From project properties, you can control whether to publish shared data sources and shared datasets. Use configuration properties to create multiple sets of project properties for production or debug modes. Add a custom data extension and install it locally and on the report server.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Tables, Matrices, and Lists [Report Builder 3.0] Use the Tablix Wizard to add a table, matrix, or list to a report. [Report Designer]

Output: Manually add a table, matrix, or list to a report from the toolbox or from the right-click menu.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Report Parts [Report Builder 3.0] Select from a list report parts on the report server. Publish items in a report as report parts. [Report Designer]

Output: Mark items as report parts. Publish them when you deploy the project.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Charts, Sparklines, and Data Bars [Report Builder 3.0] Use the Chart Wizard to add chart to a report. [Report Designer]

Output: Manually add a chart to a report from the toolbox or from the right-click menu.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Maps [Report Builder 3.0] Publish ESRI shapefiles to the report server first, and then add a reference to an ESRI file from your report. [Report Designer]

Output: Include ESRI shapefiles as resources in your project and publish them to the report server.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Images, Text Boxes, Rectangles, and Lines [Report Builder 3.0] Publish image files to the report server first, and then add a reference to the image from your report. [Report Designer]

Output: Include images as resources in your project and publish them to the report server.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Formatting Report Items [Report Builder 3.0] Use tabs and groups on the Ribbon to format items on the design surface. [Report Designer]

Output: Use Visual Studio toolbars to format items on the design surface.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Filtering, Grouping, and Sorting [Report Builder 3.0] In Report Design mode, create groups by using the Table/Matrix and Chart wizard. By default, sort expressions are set to group expressions. In Shared Dataset mode, set dataset filter options, and then save the shared dataset to the report server or SharePoint site. [Report Designer]

Output: Manually create groups by dragging fields from the Report Data pane to the Table and Matrix row group and column group panes or to the Chart category and series panes. By default, sort expressions are set to group expressions. In Solution Explorer, in the Shared Datasets folder, set dataset filters, and save them in the project. When you deploy the project, the shared datasets are saved to the report server or SharePoint site.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Drillthrough, Drilldown, Subreports, and Nested Data Regions [Report Builder 3.0] Drillthrough and subreports are supported only in server mode. Not supported in local mode. Add an expand/collapse action to an item by using the Table or Matrix Wizard. [Report Designer]

Output: In local mode, add references to reports in the project for drillthrough targets or subreports. The Table or Matrix Wizard is not available. Manually add an expand/collapse action to an item on the Text Box Properties dialog box or the Group Dialog box from a group displayed in the Grouping pane.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Area] Expressions [Report Builder 3.0] Use default expressions to display, group, and sort data in the report. You can write expressions in Microsoft Visual Basic, but there are fewer options for debugging than in Report Designer. [Report Designer]

Output: Write expressions in Visual Basic. The expression editor provides IntelliSense syntax support. Use the Output window to view warnings and compile-time error messages. Add references to .NET Framework assemblies or to custom assemblies that contain your custom code.

Designing Reports in Report Designer and Report Builder 3.0 (SSRS)


Input: [Name] CanRead [Description]

Output: When overridden in a derived class, gets a value indicating whether the current stream supports reading.


Input: [Name] CanSeek [Description]

Output: When overridden in a derived class, gets a value indicating whether the current stream supports seeking.


Input: [Name] CanTimeout [Description]

Output: Gets a value that determines whether the current stream can time out.


Input: [Name] CanWrite [Description]

Output: When overridden in a derived class, gets a value indicating whether the current stream supports writing.


Input: [Name] Length [Description]

Output: When overridden in a derived class, gets the length in bytes of the stream.


Input: [Name] Position [Description]

Output: When overridden in a derived class, gets or sets the position within the current stream.


Input: [Name] ReadTimeout [Description]

Output: Gets or sets a value that determines how long the stream will attempt to read before timing out.


Input: [Name] WriteTimeout [Description]

Output: Gets or sets a value that determines how long the stream will attempt to write before timing out.


Input: [Class] EventBookmark [Description]

Output: Represents a placeholder (bookmark) within an event stream. You can use the placeholder to mark a position and return to this position in a stream of events. An instance of this object can be obtained from an EventRecord object, in which case it corresponds to the position of that event record.


Input: [Class] EventKeyword [Description]

Output: Represents a keyword for an event. Keywords are defined in an event provider and are used to group the event with other similar events (based on the usage of the events).


Input: [Class] EventLevel [Description]

Output: Contains an event level that is defined in an event provider. The level signifies the severity of the event.


Input: [Class] EventLogConfiguration [Description]

Output: Contains static information and configuration settings for an event log. Many of the configurations settings were defined by the event provider that created the log.


Input: [Class] EventLogException [Description]

Output: Represents the base class for all the exceptions that are thrown when an error occurs while reading event log related information.


Input: [Class] EventLogInformation [Description]

Output: Allows you to access the run-time properties of active event logs and event log files. These properties include the number of events in the log, the size of the log, a value that determines whether the log is full, and the last time the log was written to or accessed.


Input: [Class] EventLogInvalidDataException [Description]

Output: Represents the exception thrown when an event provider publishes invalid data in an event.


Input: [Class] EventLogLink [Description]

Output: Represents a link between an event provider and an event log that the provider publishes events into. This object cannot be instantiated.


Input: [Class] EventLogNotFoundException [Description]

Output: Represents the exception that is thrown when a requested event log (usually specified by the name of the event log or the path to the event log file) does not exist.


Input: [Class] EventLogPropertySelector [Description]

Output: Contains an array of strings that represent XPath queries for elements in the XML representation of an event, which is based on the Event Schema. The queries in this object are used to extract values from the event.


Input: [Class] EventLogProviderDisabledException [Description]

Output: Represents the exception that is thrown when a specified event provider name references a disabled event provider. A disabled event provider cannot publish events.


Input: [Class] EventLogQuery [Description]

Output: Represents a query for events in an event log and the settings that define how the query is executed and on what computer the query is executed on.


Input: [Class] EventLogReader [Description]

Output: Enables you to read events from an event log based on an event query. The events that are read by this object are returned as EventRecord objects.


Input: [Class] EventLogReadingException [Description]

Output: Represents an exception that is thrown when an error occurred while reading, querying, or subscribing to the events in an event log.


Input: [Class] EventLogRecord [Description]

Output: Contains the properties of an event instance for an event that is received from an EventLogReader object. The event properties provide information about the event such as the name of the computer where the event was logged and the time that the event was created.


Input: [Class] EventLogSession [Description]

Output: Used to access the Event Log service on the local computer or a remote computer so you can manage and gather information about the event logs and event providers on the computer.


Input: [Class] EventLogStatus [Description]

Output: Contains the status code or error code for a specific event log. This status can be used to determine if the event log is available for an operation.


Input: [Class] EventLogWatcher [Description]

Output: Allows you to subscribe to incoming events. Each time a desired event is published to an event log, the EventRecordWritten event is raised, and the method that handles this event will be executed.


Input: [Class] EventMetadata [Description]

Output: Contains the metadata (properties and settings) for an event that is defined in an event provider.


Input: [Class] EventOpcode [Description]

Output: Contains an event opcode that is defined in an event provider. An opcode defines a numeric value that identifies the activity or a point within an activity that the application was performing when it raised the event.


Input: [Class] EventProperty [Description]

Output: Contains the value of an event property that is specified by the event provider when the event is published.


Input: [Class] EventRecord [Description]

Output: Defines the properties of an event instance for an event that is received from an EventLogReader object. The event properties provide information about the event such as the name of the computer where the event was logged and the time the event was created. This class is an abstract class. The EventLogRecord class implements this class.


Input: [Class] EventRecordWrittenEventArgs [Description]

Output: When the EventRecordWritten event is raised, an instance of this object is passed to the delegate method that handles the event. This object contains the event that was published to the event log or the exception that occurred when the event subscription failed.


Input: [Class] EventTask [Description]

Output: Contains an event task that is defined in an event provider. The task identifies a portion of an application or a component that publishes an event. A task is a 16-bit value with 16 top values reserved.


Input: [Class] ProviderMetadata [Description]

Output: Contains static information about an event provider, such as the name and id of the provider, and the collection of events defined in the provider.


Input: [Class] BinaryReader [Description]

Output: Reads primitive data types as binary values in a specific encoding.


Input: [Class] BinaryWriter [Description]

Output: Writes primitive types in binary to a stream and supports writing strings in a specific encoding.


Input: [Class] Directory [Description]

Output: Exposes static methods for creating, moving, and enumerating through directories and subdirectories. This class cannot be inherited.


Input: [Class] DirectoryInfo [Description]

Output: Exposes instance methods for creating, moving, and enumerating through directories and subdirectories. This class cannot be inherited.


Input: [Class] DirectoryNotFoundException [Description]

Output: Infrastructure. The exception that is thrown when part of a file or directory cannot be found.


Input: [Class] EndOfStreamException [Description]

Output: The exception that is thrown when reading is attempted past the end of a stream.


Input: [Class] File [Description]

Output: Provides static methods for the creation, copying, deletion, moving, and opening of files, and aids in the creation of FileStream objects.


Input: [Class] FileInfo [Description]

Output: Provides instance methods for the creation, copying, deletion, moving, and opening of files, and aids in the creation of FileStream objects. This class cannot be inherited.


Input: [Class] FileLoadException [Description]

Output: The exception that is thrown when a managed assembly is found but cannot be loaded.


Input: [Class] FileNotFoundException [Description]

Output: The exception that is thrown when an attempt to access a file that does not exist fails.


Input: [Class] FileStream [Description]

Output: Exposes a Stream around a file, supporting both synchronous and asynchronous read and write operations.


Input: [Class] FileSystemInfo [Description]

Output: Provides the base class for both FileInfo and DirectoryInfo objects.


Input: [Class] InvalidDataException [Description]

Output: The exception that is thrown when a data stream is in an invalid format.


Input: [Class] IOException [Description]

Output: The exception that is thrown when an I/O error occurs.


Input: [Class] MemoryStream [Description]

Output: Creates a stream whose backing store is memory.


Input: [Class] Path [Description]

Output: Performs operations on String instances that contain file or directory path information. These operations are performed in a cross-platform manner.


Input: [Class] PathTooLongException [Description]

Output: The exception that is thrown when a pathname or filename is longer than the system-defined maximum length.


Input: [Class] Stream [Description]

Output: Provides a generic view of a sequence of bytes.


Input: [Class] StreamReader [Description]

Output: Implements a TextReader that reads characters from a byte stream in a particular encoding.


Input: [Class] StreamWriter [Description]

Output: Implements a TextWriter for writing characters to a stream in a particular encoding.


Input: [Class] StringReader [Description]

Output: Implements a TextReader that reads from a string.


Input: [Class] StringWriter [Description]

Output: Implements a TextWriter for writing information to a string. The information is stored in an underlying StringBuilder.


Input: [Class] TextReader [Description]

Output: Represents a reader that can read a sequential series of characters.


Input: [Class] TextWriter [Description]

Output: Represents a writer that can write a sequential series of characters. This class is abstract.


Input: [Class] UnmanagedMemoryStream [Description]

Output: Infrastructure. Provides access to unmanaged blocks of memory from managed code.


Input: [Behavior] Transparency [Not supported] Some Windows Forms controls do not support transparency. For example, the TextBox and ComboBox controls will not be transparent when hosted by WPF. [Supported]

Output: Windows Forms control rendering supports transparency. The background of the parent WPF control can become the background of hosted Windows Forms controls.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Tabbing [Not supported] Not applicable. [Supported]

Output: Tab order for hosted Windows Forms controls is the same as when those controls are hosted in a Windows Forms-based application. Tabbing from a WPF control to a Windows Forms control with the TAB key and SHIFT+TAB keys works as usual. Windows Forms controls that have a TabStop property value of false do not receive focus when the user tabs through controls. Each WindowsFormsHost control has a TabIndex value, which determines when that WindowsFormsHost control will receive focus. Windows Forms controls that are contained inside a WindowsFormsHost container follow the order specified by the TabIndex property. Tabbing from the last tab index puts focus on the next WPF control, if one exists. If no other focusable WPF control exists, tabbing returns to the first Windows Forms control in the tab order. TabIndex values for controls inside the WindowsFormsHost are relative to sibling Windows Forms controls that are contained in the WindowsFormsHost control. Tabbing honors control-specific behavior. For example, pressing the TAB key in a TextBox control that has a AcceptsTab property value of true enters a tab in the text box instead of moving the focus.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Navigation with arrow keys [Not supported] Not applicable. [Supported]

Output: Navigation with arrow keys in the WindowsFormsHost control is the same as in an ordinary Windows Forms container control: The UP ARROW and LEFT ARROW keys select the previous control, and the DOWN ARROW and RIGHT ARROW keys select the next control. The UP ARROW and LEFT ARROW keys from the first control that is contained in the WindowsFormsHost control perform the same action as the SHIFT+TAB keyboard shortcut. If there is a focusable WPF control, focus moves outside the WindowsFormsHost control. This behavior differs from the standard ContainerControl behavior in that no wrapping to the last control occurs. If no other focusable WPF control exists, focus returns to the last Windows Forms control in the tab order. The DOWN ARROW and RIGHT ARROW keys from the last control that is contained in the WindowsFormsHost control perform the same action as the TAB key. If there is a focusable WPF control, focus moves outside the WindowsFormsHost control. This behavior differs from the standard ContainerControl behavior in that no wrapping to the first control occurs. If no other focusable WPF control exists, focus returns to the first Windows Forms control in the tab order.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Accelerators [Not supported] Duplicate accelerators across technologies do not work like ordinary duplicate accelerators. When an accelerator is duplicated across technologies, with at least one on a Windows Forms control and the other on a WPF control, the Windows Forms control always receives the accelerator. Focus does not toggle between the controls when the duplicate accelerator is pressed. [Supported]

Output: Accelerators work as usual, except where noted in the "Not supported" column.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Shortcut keys [Not supported] Windows Forms shortcut keys that are handled at the preprocessing stage always take precedence over WPF shortcut keys. For example, if you have a ToolStrip control with CTRL+S shortcut keys defined, and there is a WPF command bound to CTRL+S, the ToolStrip control handler is always invoked first, regardless of focus. Windows Forms shortcut keys that are handled by the KeyDown event are processed last in WPF. You can prevent this behavior by overriding the Windows Forms control's IsInputKey method or handling the PreviewKeyDown event. Return true from the IsInputKey method, or set the value of the System.Windows.Forms.PreviewKeyDownEventArgs.IsInputKey property to true in your PreviewKeyDown event handler. [Supported]

Output: Shortcut keys work as usual, except where noted in the "Not supported" column.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] AcceptsReturn, AcceptsTab, and other control-specific behavior [Not supported] Windows Forms controls that change default keyboard behavior by handling the KeyDown event are processed last in the host WPF control. Because these controls are processed last, they can produce unexpected behavior. [Supported]

Output: Properties that change the default keyboard behavior work as usual, assuming that the Windows Forms control overrides the IsInputKey method to return true.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Enter and Leave Events [Not supported] Enter and Leave events are not raised when the following focus changes occur: From inside to outside a WindowsFormsHost control. From outside to inside a WindowsFormsHost control. Outside a WindowsFormsHost control. From a Windows Forms control hosted in a WindowsFormsHost control to an ElementHost control hosted inside the same WindowsFormsHost. [Supported]

Output: When focus is not going to the containing ElementHost control, the Enter and Leave events are raised as usual when focus changes in a single WindowsFormsHost control.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Multithreading [Not supported] Both the Windows Forms and WPF technologies assume a single-threaded concurrency model. During debugging, calls to framework objects from other threads will raise an exception to enforce this requirement. [Supported]

Output: All varieties of multithreading are supported.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Security [Not supported] No interoperation scenarios are allowed in partial trust. [Supported]

Output: All interoperation scenarios require full trust.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Accessibility [Not supported] Not applicable. [Supported]

Output: All accessibility scenarios are supported. Assistive technology products function correctly when they are used for hybrid applications that contain both Windows Forms and WPF controls.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Clipboard [Not supported] Not applicable. [Supported]

Output: All Clipboard operations work as usual. This includes cutting and pasting between Windows Forms and WPF controls.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Behavior] Drag-and-drop feature [Not supported] Not applicable. [Supported]

Output: All drag-and-drop operations work as usual. This includes operations between Windows Forms and WPF controls.

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Name] Date [Description]

Output: Gets the date component of this instance.


Input: [Name] Day [Description]

Output: Gets the day of the month represented by this instance.


Input: [Name] DayOfWeek [Description]

Output: Gets the day of the week represented by this instance.


Input: [Name] DayOfYear [Description]

Output: Gets the day of the year represented by this instance.


Input: [Name] Hour [Description]

Output: Gets the hour component of the date represented by this instance.


Input: [Name] Kind [Description]

Output: Gets a value that indicates whether the time represented by this instance is based on local time, Coordinated Universal Time (UTC), or neither.


Input: [Name] Millisecond [Description]

Output: Gets the milliseconds component of the date represented by this instance.


Input: [Name] Minute [Description]

Output: Gets the minute component of the date represented by this instance.


Input: [Name] Month [Description]

Output: Gets the month component of the date represented by this instance.


Input: [Name] Now [Description]

Output: Gets a DateTime object that is set to the current date and time on this computer, expressed as the local time.


Input: [Name] Second [Description]

Output: Gets the seconds component of the date represented by this instance.


Input: [Name] Ticks [Description]

Output: Gets the number of ticks that represent the date and time of this instance.


Input: [Name] TimeOfDay [Description]

Output: Gets the time of day for this instance.


Input: [Name] Today [Description]

Output: Gets the current date.


Input: [Name] UtcNow [Description]

Output: Gets a DateTime object that is set to the current date and time on this computer, expressed as the Coordinated Universal Time (UTC).


Input: [Name] Year [Description]

Output: Gets the year component of the date represented by this instance.


Input: [Task] Describes how to create a unique constraint. [Topic]

Output: Create Unique Constraints

Unique Constraints and Check Constraints


Input: [Task] Describes how to modify a unique constraint. [Topic]

Output: Modify Unique Constraints

Unique Constraints and Check Constraints


Input: [Task] Describes how to delete a unique constraint. [Topic]

Output: Delete Unique Constraints

Unique Constraints and Check Constraints


Input: [Task] Describes how to disable a check constraint when a replication agent inserts or updates data in your table. [Topic]

Output: Disable Check Constraints for Replication

Unique Constraints and Check Constraints


Input: [Task] Describes how to disable a check constraint when data is added to, updated in, or deleted from a table. [Topic]

Output: Disable Check Constraints with INSERT and UPDATE Statements

Unique Constraints and Check Constraints


Input: [Task] Describes how to change the constraint expression or the options that enable or disable the constraint for specific conditions. [Topic]

Output: Modify Check Constraints

Unique Constraints and Check Constraints


Input: [Task] Describes how to delete a check constraint. [Topic]

Output: Delete Check Constraints

Unique Constraints and Check Constraints


Input: [Member name] Displayed [Description]

Output: Indicates the an element is currently displayed onscreen.


Input: [Member name] Frozen [Description]

Output: Indicates that an element cannot be scrolled through the UI.


Input: [Member name] None [Description]

Output: Indicates that an element is in its default state.


Input: [Member name] ReadOnly [Description]

Output: Indicates that an element will not accept user input to change its value.


Input: [Member name] Resizable [Description]

Output: Indicates that an element can be resized through the UI. This value is ignored except when combined with the ResizableSet value.


Input: [Member name] ResizableSet [Description]

Output: Indicates that an element does not inherit the resizable state of its parent.


Input: [Member name] Selected [Description]

Output: Indicates that an element is in a selected (highlighted) UI state.


Input: [Member name] Visible [Description]

Output: Indicates that an element is visible (displayable).


Input: [Supported] Windows Forms control rendering supports transparency. The background of the parent WPF control can become the background of hosted Windows Forms controls. [Not supported] Some Windows Forms controls do not support transparency. For example, the TextBox and ComboBox controls will not be transparent when hosted by WPF. [Behavior]

Output: Transparency

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] Tab order for hosted Windows Forms controls is the same as when those controls are hosted in a Windows Forms-based application. Tabbing from a WPF control to a Windows Forms control with the TAB key and SHIFT+TAB keys works as usual. Windows Forms controls that have a TabStop property value of false do not receive focus when the user tabs through controls. Each WindowsFormsHost control has a TabIndex value, which determines when that WindowsFormsHost control will receive focus. Windows Forms controls that are contained inside a WindowsFormsHost container follow the order specified by the TabIndex property. Tabbing from the last tab index puts focus on the next WPF control, if one exists. If no other focusable WPF control exists, tabbing returns to the first Windows Forms control in the tab order. TabIndex values for controls inside the WindowsFormsHost are relative to sibling Windows Forms controls that are contained in the WindowsFormsHost control. Tabbing honors control-specific behavior. For example, pressing the TAB key in a TextBox control that has a AcceptsTab property value of true enters a tab in the text box instead of moving the focus. [Not supported] Not applicable. [Behavior]

Output: Tabbing

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] Navigation with arrow keys in the WindowsFormsHost control is the same as in an ordinary Windows Forms container control: The UP ARROW and LEFT ARROW keys select the previous control, and the DOWN ARROW and RIGHT ARROW keys select the next control. The UP ARROW and LEFT ARROW keys from the first control that is contained in the WindowsFormsHost control perform the same action as the SHIFT+TAB keyboard shortcut. If there is a focusable WPF control, focus moves outside the WindowsFormsHost control. This behavior differs from the standard ContainerControl behavior in that no wrapping to the last control occurs. If no other focusable WPF control exists, focus returns to the last Windows Forms control in the tab order. The DOWN ARROW and RIGHT ARROW keys from the last control that is contained in the WindowsFormsHost control perform the same action as the TAB key. If there is a focusable WPF control, focus moves outside the WindowsFormsHost control. This behavior differs from the standard ContainerControl behavior in that no wrapping to the first control occurs. If no other focusable WPF control exists, focus returns to the first Windows Forms control in the tab order. [Not supported] Not applicable. [Behavior]

Output: Navigation with arrow keys

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] Accelerators work as usual, except where noted in the "Not supported" column. [Not supported] Duplicate accelerators across technologies do not work like ordinary duplicate accelerators. When an accelerator is duplicated across technologies, with at least one on a Windows Forms control and the other on a WPF control, the Windows Forms control always receives the accelerator. Focus does not toggle between the controls when the duplicate accelerator is pressed. [Behavior]

Output: Accelerators

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] Shortcut keys work as usual, except where noted in the "Not supported" column. [Not supported] Windows Forms shortcut keys that are handled at the preprocessing stage always take precedence over WPF shortcut keys. For example, if you have a ToolStrip control with CTRL+S shortcut keys defined, and there is a WPF command bound to CTRL+S, the ToolStrip control handler is always invoked first, regardless of focus. Windows Forms shortcut keys that are handled by the KeyDown event are processed last in WPF. You can prevent this behavior by overriding the Windows Forms control's IsInputKey method or handling the PreviewKeyDown event. Return true from the IsInputKey method, or set the value of the System.Windows.Forms.PreviewKeyDownEventArgs.IsInputKey property to true in your PreviewKeyDown event handler. [Behavior]

Output: Shortcut keys

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] Properties that change the default keyboard behavior work as usual, assuming that the Windows Forms control overrides the IsInputKey method to return true. [Not supported] Windows Forms controls that change default keyboard behavior by handling the KeyDown event are processed last in the host WPF control. Because these controls are processed last, they can produce unexpected behavior. [Behavior]

Output: AcceptsReturn, AcceptsTab, and other control-specific behavior

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] When focus is not going to the containing ElementHost control, the Enter and Leave events are raised as usual when focus changes in a single WindowsFormsHost control. [Not supported] Enter and Leave events are not raised when the following focus changes occur: From inside to outside a WindowsFormsHost control. From outside to inside a WindowsFormsHost control. Outside a WindowsFormsHost control. From a Windows Forms control hosted in a WindowsFormsHost control to an ElementHost control hosted inside the same WindowsFormsHost. [Behavior]

Output: Enter and Leave Events

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] All varieties of multithreading are supported. [Not supported] Both the Windows Forms and WPF technologies assume a single-threaded concurrency model. During debugging, calls to framework objects from other threads will raise an exception to enforce this requirement. [Behavior]

Output: Multithreading

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] All interoperation scenarios require full trust. [Not supported] No interoperation scenarios are allowed in partial trust. [Behavior]

Output: Security

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] All accessibility scenarios are supported. Assistive technology products function correctly when they are used for hybrid applications that contain both Windows Forms and WPF controls. [Not supported] Not applicable. [Behavior]

Output: Accessibility

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] All Clipboard operations work as usual. This includes cutting and pasting between Windows Forms and WPF controls. [Not supported] Not applicable. [Behavior]

Output: Clipboard

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [Supported] All drag-and-drop operations work as usual. This includes operations between Windows Forms and WPF controls. [Not supported] Not applicable. [Behavior]

Output: Drag-and-drop feature

Supported Scenarios in Windows Presentation Foundation and Windows Forms Interoperation


Input: [VisualState Name] Normal [Description] The default state. [VisualStateGroup Name]

Output: CommonStates


Input: [VisualState Name] MouseOver [Description] The mouse pointer is positioned over the control. [VisualStateGroup Name]

Output: CommonStates


Input: [VisualState Name] Pressed [Description] The control is pressed. [VisualStateGroup Name]

Output: CommonStates


Input: [VisualState Name] Disabled [Description] The control is disabled. [VisualStateGroup Name]

Output: CommonStates


Input: [VisualState Name] Focused [Description] IsFocused is true. [VisualStateGroup Name]

Output: FocusStates


Input: [VisualState Name] Unfocused [Description] IsFocused is false. [VisualStateGroup Name]

Output: FocusStates


Input: [VisualState Name] Checked [Description] IsChecked is true. [VisualStateGroup Name]

Output: CheckStates


Input: [VisualState Name] Unchecked [Description] IsChecked is false. [VisualStateGroup Name]

Output: CheckStates


Input: [VisualState Name] Indeterminate [Description] IsThreeState is true, and IsChecked is null. [VisualStateGroup Name]

Output: CheckStates


Input: [VisualState Name] Valid [Description] The control is valid. [VisualStateGroup Name]

Output: ValidationStates


Input: [VisualState Name] InvalidUnfocused [Description] The control is not valid and does not have focus. [VisualStateGroup Name]

Output: ValidationStates


Input: [VisualState Name] InvalidFocused [Description] The control is not valid and has focus. [VisualStateGroup Name]

Output: ValidationStates


Input: [uCommand] HELP_COMMAND [Action] Executes a help macro or macro string. [dwData]

Output: Address of a string that specifies the name of the help macro(s) to run. If the string specifies multiple macro names, the names must be separated by semicolons. You must use the short form of the macro name for some macros because Windows Help does not support the long name.


Input: [uCommand] HELP_CONTENTS [Action] Displays the topic specified by the Contents option in the [OPTIONS] section of the .hpj file. This command is for backward compatibility. New applications should provide a .cnt file and use the HELP_FINDER command. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_CONTEXT [Action] Displays the topic identified by the specified context identifier defined in the [MAP] section of the .hpj file. [dwData]

Output: Contains the context identifier for the topic.


Input: [uCommand] HELP_CONTEXTMENU [Action] Displays the Help menu for the selected window, then displays the topic for the selected control in a pop-up window. [dwData]

Output: Address of an array of DWORD pairs. The first DWORD in each pair is the control identifier, and the second is the context identifier for the topic. The array must be terminated by a pair of zeros {0,0}. If you do not want to add help to a particular control, set its context identifier to -1.


Input: [uCommand] HELP_CONTEXTPOPUP [Action] Displays the topic identified by the specified context identifier defined in the [MAP] section of the .hpj file in a pop-up window. [dwData]

Output: Contains the context identifier for a topic.


Input: [uCommand] HELP_FINDER [Action] Displays the Help Topics dialog box. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_FORCEFILE [Action] Ensures that Windows Help is displaying the correct help file. If the incorrect help file is being displayed, Windows Help opens the correct one; otherwise, there is no action. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_HELPONHELP [Action] Displays help on how to use Windows Help, if the Winhlp32.hlp file is available. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_INDEX [Action] Displays the topic specified by the Contents option in the [OPTIONS] section of the .hpj file. This command is for backward compatibility. New applications should use the HELP_FINDER command. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_KEY [Action] Displays the topic in the keyword table that matches the specified keyword, if there is an exact match. If there is more than one match, displays the index with the topics listed in the Topics Found list box. [dwData]

Output: Address of a keyword string. Multiple keywords must be separated by semicolons.


Input: [uCommand] HELP_MULTIKEY [Action] Displays the topic specified by a keyword in an alternative keyword table. [dwData]

Output: Address of a MULTIKEYHELP structure that specifies a table footnote character and a keyword.


Input: [uCommand] HELP_PARTIALKEY [Action] Displays the topic in the keyword table that matches the specified keyword, if there is an exact match. If there is more than one match, displays the Topics Found dialog box. To display the index without passing a keyword, use a pointer to an empty string. [dwData]

Output: Address of a keyword string. Multiple keywords must be separated by semicolons.


Input: [uCommand] HELP_QUIT [Action] Informs Windows Help that it is no longer needed. If no other applications have asked for help, Windows closes Windows Help. [dwData]

Output: Ignored; set to 0.


Input: [uCommand] HELP_SETCONTENTS [Action] Specifies the Contents topic. Windows Help displays this topic when the user clicks the Contents button if the help file does not have an associated .cnt file. [dwData]

Output: Contains the context identifier for the Contents topic.


Input: [uCommand] HELP_SETPOPUP_POS [Action] Sets the position of the subsequent pop-up window. [dwData]

Output: Contains the position data. Use the MAKELONG macro to concatenate the horizontal and vertical coordinates into a single value. The pop-up window is positioned as if the mouse cursor were at the specified point when the pop-up window was invoked.


Input: [uCommand] HELP_SETWINPOS [Action] Displays the Windows Help window, if it is minimized or in memory, and sets its size and position as specified. [dwData]

Output: Address of a HELPWININFO structure that specifies the size and position of either a primary or secondary help window.


Input: [uCommand] HELP_TCARD [Action] Indicates that a command is for a training card instance of Windows Help. Combine this command with other commands using the bitwise OR operator. [dwData]

Output: Depends on the command with which this command is combined.


Input: [uCommand] HELP_WM_HELP [Action] Displays the topic for the control identified by the hWndMain parameter in a pop-up window. [dwData]

Output: Address of an array of DWORD pairs. The first DWORD in each pair is a control identifier, and the second is a context identifier for a topic. The array must be terminated by a pair of zeros {0,0}. If you do not want to add Help to a particular control, set its context identifier to -1.


Input: [Description] Provides information about a given codec. This is an abstract class. [Class]

Output: BitmapCodecInfo


Input: [Description] Represents a container for bitmap frames. Each bitmap frame is a BitmapSource. This abstract class provides a base set of functionality for all derived decoder objects. [Class]

Output: BitmapDecoder


Input: [Description] Encodes a collection of BitmapFrame objects to an image stream. This is an abstract class. [Class]

Output: BitmapEncoder


Input: [Description] Represents image data returned by a decoder and accepted by encoders. This is an abstract class. [Class]

Output: BitmapFrame


Input: [Description] Provides a specialized BitmapSource that is optimized for loading images using Extensible Application Markup Language (XAML). [Class]

Output: BitmapImage


Input: [Description] Provides support for reading and writing metadata to and from a bitmap image. [Class]

Output: BitmapMetadata


Input: [Description] Provides a placeholder for metadata items that cannot be converted from C# to an underlying data type that persists metadata. The blob is converted into an array of bytes to preserve the content. [Class]

Output: BitmapMetadataBlob


Input: [Description] Defines the available color palette for a supported image type. [Class]

Output: BitmapPalette


Input: [Description] Defines several color palettes that are commonly used by bitmap images. [Class]

Output: BitmapPalettes


Input: [Description] Defines size-related attributes of a cached bitmap image. A bitmap is scaled based on values that are defined by this class. [Class]

Output: BitmapSizeOptions


Input: [Description] Represents a single, constant set of pixels at a certain size and resolution. This is an abstract class. [Class]

Output: BitmapSource


Input: [Description] Defines a decoder for bitmap (BMP) encoded images. This class cannot be inherited. [Class]

Output: BmpBitmapDecoder


Input: [Description] Defines an encoder that is used to encode bitmap (BMP) format images. [Class]

Output: BmpBitmapEncoder


Input: [Description] Provides caching functionality for a BitmapSource. [Class]

Output: CachedBitmap


Input: [Description] Changes the color space of a BitmapSource. This class cannot be inherited. [Class]

Output: ColorConvertedBitmap


Input: [Description] Crops a BitmapSource. This class cannot be inherited. [Class]

Output: CroppedBitmap


Input: [Description] Provides data for the BitmapSource.DownloadProgress and BitmapDecoder.DownloadProgress events. [Class]

Output: DownloadProgressEventArgs


Input: [Description] Provides pixel format conversion functionality for a BitmapSource. This class cannot be inherited. [Class]

Output: FormatConvertedBitmap


Input: [Description] Defines a decoder for Graphics Interchange Format (GIF) encoded images. [Class]

Output: GifBitmapDecoder


Input: [Description] Defines an encoder that is used to encode Graphics Interchange Format (GIF) images. [Class]

Output: GifBitmapEncoder


Input: [Description] Defines a specialized decoder for icon (.ico) encoded images. This class cannot be inherited. [Class]

Output: IconBitmapDecoder


Input: [Description] Enables in-place updates to existing blocks of BitmapMetadata. This class cannot be inherited. [Class]

Output: InPlaceBitmapMetadataWriter


Input: [Description] Defines a decoder for Joint Photographics Experts Group (JPEG) encoded images. This class cannot be inherited. [Class]

Output: JpegBitmapDecoder


Input: [Description] Defines an encoder that is used to encode Joint Photographics Experts Group (JPEG) format images. This class cannot be inherited. [Class]

Output: JpegBitmapEncoder


Input: [Description] Defines a decoder that requires delayed bitmap creation such as asynchronous image downloads. This class cannot be inherited. [Class]

Output: LateBoundBitmapDecoder


Input: [Description] Defines a decoder for Portable Network Graphics (PNG) encoded images. This class cannot be inherited. [Class]

Output: PngBitmapDecoder


Input: [Description] Defines an encoder that is used to encode Portable Network Graphics (PNG) format images. This class cannot be inherited. [Class]

Output: PngBitmapEncoder


Input: [Description] Used to convert a Visual object into a bitmap. [Class]

Output: RenderTargetBitmap


Input: [Description] Defines a decoder for Tagged Image File Format (TIFF) encoded images. This class cannot be inherited. [Class]

Output: TiffBitmapDecoder


Input: [Description] Defines an encoder that is used to encode Tagged Image File Format (TIFF) format images. [Class]

Output: TiffBitmapEncoder


Input: [Description] Scales and rotates a BitmapSource. This class cannot be inherited. [Class]

Output: TransformedBitmap


Input: [Description] Defines a decoder for Microsoft Windows Media Photo encoded images. This class cannot be inherited. [Class]

Output: WmpBitmapDecoder


Input: [Description] Defines an encoder that is used to encode Microsoft Windows Media Photo images. [Class]

Output: WmpBitmapEncoder


Input: [Description] Provides a BitmapSource that can be written to and updated. [Class]

Output: WriteableBitmap


Input: [Name] Abort() [Description]

Output: Raises a ThreadAbortException in the thread on which it is invoked, to begin the process of terminating the thread. Calling this method usually terminates the thread.


Input: [Name] Abort(Object) [Description]

Output: Raises a ThreadAbortException in the thread on which it is invoked, to begin the process of terminating the thread while also providing exception information about the thread termination. Calling this method usually terminates the thread.


Input: [Name] AllocateDataSlot [Description]

Output: Allocates an unnamed data slot on all the threads. For better performance, use fields that are marked with the ThreadStaticAttribute attribute instead.


Input: [Name] AllocateNamedDataSlot [Description]

Output: Allocates a named data slot on all threads. For better performance, use fields that are marked with the ThreadStaticAttribute attribute instead.


Input: [Name] BeginCriticalRegion [Description]

Output: Notifies a host that execution is about to enter a region of code in which the effects of a thread abort or unhandled exception might jeopardize other tasks in the application domain.


Input: [Name] BeginThreadAffinity [Description]

Output: Notifies a host that managed code is about to execute instructions that depend on the identity of the current physical operating system thread.


Input: [Name] DisableComObjectEagerCleanup [Description]

Output: Turns off automatic cleanup of runtime callable wrappers (RCW) for the current thread.


Input: [Name] EndCriticalRegion [Description]

Output: Notifies a host that execution is about to enter a region of code in which the effects of a thread abort or unhandled exception are limited to the current task.


Input: [Name] EndThreadAffinity [Description]

Output: Notifies a host that managed code has finished executing instructions that depend on the identity of the current physical operating system thread.


Input: [Name] Equals(Object) [Description]

Output: Determines whether the specified object is equal to the current object. (Inherited from Object.)


Input: [Name] Finalize [Description]

Output: Ensures that resources are freed and other cleanup operations are performed when the garbage collector reclaims the Thread object. (Overrides CriticalFinalizerObject.Finalize().)


Input: [Name] FreeNamedDataSlot [Description]

Output: Eliminates the association between a name and a slot, for all threads in the process. For better performance, use fields that are marked with the ThreadStaticAttribute attribute instead.


Input: [Name] GetApartmentState [Description]

Output: Returns an ApartmentState value indicating the apartment state.


Input: [Name] GetCompressedStack [Description]

Output: Obsolete. Returns a CompressedStack object that can be used to capture the stack for the current thread.


Input: [Name] GetData [Description]

Output: Retrieves the value from the specified slot on the current thread, within the current thread's current domain. For better performance, use fields that are marked with the ThreadStaticAttribute attribute instead.


Input: [Name] GetDomain [Description]

Output: Returns the current domain in which the current thread is running.


Input: [Name] GetDomainID [Description]

Output: Returns a unique application domain identifier.


Input: [Name] GetHashCode [Description]

Output: Returns a hash code for the current thread. (Overrides Object.GetHashCode().) In XNA Framework 3.0, this member is inherited from Object.GetHashCode(). In Portable Class Library Portable Class Library, this member is inherited from Object.GetHashCode().


Input: [Name] GetNamedDataSlot [Description]

Output: Looks up a named data slot. For better performance, use fields that are marked with the ThreadStaticAttribute attribute instead.


Input: [Name] GetType [Description]

Output: Gets the Type of the current instance. (Inherited from Object.)


Input: [Name] Interrupt [Description]

Output: Interrupts a thread that is in the WaitSleepJoin thread state.


Input: [Name] Join() [Description]

Output: Blocks the calling thread until a thread terminates, while continuing to perform standard COM and SendMessage pumping.


Input: [Name] Join(Int32) [Description]

Output: Blocks the calling thread until a thread terminates or the specified time elapses, while continuing to perform standard COM and SendMessage pumping.


Input: [Name] Join(TimeSpan) [Description]

Output: Blocks the calling thread until a thread terminates or the specified time elapses, while continuing to perform standard COM and SendMessage pumping.


Input: [Name] MemoryBarrier [Description]

Output: Synchronizes memory access as follows: The processor executing the current thread cannot reorder instructions in such a way that memory accesses prior to the call to MemoryBarrier execute after memory accesses that follow the call to MemoryBarrier.


Input: [Name] ResetAbort [Description]

Output: Cancels an Abort requested for the current thread.


Input: [Name] Resume [Description]

Output: Obsolete. Resumes a thread that has been suspended.


Input: [Name] SetApartmentState [Description]

Output: Sets the apartment state of a thread before it is started.


Input: [Name] SetCompressedStack [Description]

Output: Obsolete. Applies a captured CompressedStack to the current thread.


Input: [Name] SetData [Description]

Output: Sets the data in the specified slot on the currently running thread, for that thread's current domain. For better performance, use fields marked with the ThreadStaticAttribute attribute instead.


Input: [Name] SetProcessorAffinity [Description]

Output: In the .NET Compact Framework for Xbox 360, sets the processor affinity for a managed thread. Processor affinity determines the processors on which a thread runs.


Input: [Name] Sleep(Int32) [Description]

Output: Suspends the current thread for the specified number of milliseconds.


Input: [Name] Sleep(TimeSpan) [Description]

Output: Suspends the current thread for the specified amount of time.


Input: [Name] SpinWait [Description]

Output: Causes a thread to wait the number of times defined by the iterations parameter.


Input: [Name] Start() [Description]

Output: Causes the operating system to change the state of the current instance to ThreadState.Running.


Input: [Name] Start(Object) [Description]

Output: Causes the operating system to change the state of the current instance to ThreadState.Running, and optionally supplies an object containing data to be used by the method the thread executes.


Input: [Name] Suspend [Description]

Output: Obsolete. Either suspends the thread, or if the thread is already suspended, has no effect.


Input: [Name] ToString [Description]

Output: Returns a string that represents the current object. (Inherited from Object.)


Input: [Name] TrySetApartmentState [Description]

Output: Sets the apartment state of a thread before it is started.


Input: [Name] VolatileRead(Byte) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Double) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Int16) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Int32) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Int64) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(IntPtr) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Object) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(SByte) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(Single) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(UInt16) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(UInt32) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(UInt64) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileRead(UIntPtr) [Description]

Output: Reads the value of a field. The value is the latest written by any processor in a computer, regardless of the number of processors or the state of processor cache.


Input: [Name] VolatileWrite(Byte, Byte) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Double, Double) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Int16, Int16) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Int32, Int32) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Int64, Int64) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(IntPtr, IntPtr) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Object, Object) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(SByte, SByte) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(Single, Single) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(UInt16, UInt16) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(UInt32, UInt32) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(UInt64, UInt64) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] VolatileWrite(UIntPtr, UIntPtr) [Description]

Output: Writes a value to a field immediately, so that the value is visible to all processors in the computer.


Input: [Name] Yield [Description]

Output: Causes the calling thread to yield execution to another thread that is ready to run on the current processor. The operating system selects the thread to yield to.


Input: [Description] Represents the result of custom processing on submitted documents. [Enumeration]

Output: CustomRouterResult


Input: [Description] Specifies whether there was a collision, whether an existing file with the same file name as the document being routed at the document's final routing destination when determining the final routing destination of a document, and what the router settings say to do if there is a collision. [Enumeration]

Output: DocumentRoutingCollisionSetting


Input: [Description] Result from calling the GetFinalRoutingDestinationFolderUrl Web service to route a document. [Enumeration]

Output: DocumentRoutingResultType


Input: [Description] Enumerates the possible permission levels required for declaring and undeclaring records. [Enumeration]

Output: RecordDeclarationPermissions


Input: [Description] Enumerates the possible statuses of custom record declaration and undeclaration processing. [Enumeration]

Output: RecordOperationResult


Input: [Description] Enumerates the possible restrictions imposed on record items. [Enumeration]

Output: RecordRestrictions


Input: [Class] BitmapCodecInfo [Description]

Output: Provides information about a given codec. This is an abstract class.


Input: [Class] BitmapDecoder [Description]

Output: Represents a container for bitmap frames. Each bitmap frame is a BitmapSource. This abstract class provides a base set of functionality for all derived decoder objects.


Input: [Class] BitmapEncoder [Description]

Output: Encodes a collection of BitmapFrame objects to an image stream. This is an abstract class.


Input: [Class] BitmapFrame [Description]

Output: Represents image data returned by a decoder and accepted by encoders. This is an abstract class.


Input: [Class] BitmapImage [Description]

Output: Provides a specialized BitmapSource that is optimized for loading images using Extensible Application Markup Language (XAML).


Input: [Class] BitmapMetadata [Description]

Output: Provides support for reading and writing metadata to and from a bitmap image.


Input: [Class] BitmapMetadataBlob [Description]

Output: Provides a placeholder for metadata items that cannot be converted from C# to an underlying data type that persists metadata. The blob is converted into an array of bytes to preserve the content.


Input: [Class] BitmapPalette [Description]

Output: Defines the available color palette for a supported image type.


Input: [Class] BitmapPalettes [Description]

Output: Defines several color palettes that are commonly used by bitmap images.


Input: [Class] BitmapSizeOptions [Description]

Output: Defines size-related attributes of a cached bitmap image. A bitmap is scaled based on values that are defined by this class.


Input: [Class] BitmapSource [Description]

Output: Represents a single, constant set of pixels at a certain size and resolution. This is an abstract class.


Input: [Class] BmpBitmapDecoder [Description]

Output: Defines a decoder for bitmap (BMP) encoded images. This class cannot be inherited.


Input: [Class] BmpBitmapEncoder [Description]

Output: Defines an encoder that is used to encode bitmap (BMP) format images.


Input: [Class] CachedBitmap [Description]

Output: Provides caching functionality for a BitmapSource.


Input: [Class] ColorConvertedBitmap [Description]

Output: Changes the color space of a BitmapSource. This class cannot be inherited.


Input: [Class] CroppedBitmap [Description]

Output: Crops a BitmapSource. This class cannot be inherited.


Input: [Class] DownloadProgressEventArgs [Description]

Output: Provides data for the BitmapSource.DownloadProgress and BitmapDecoder.DownloadProgress events.


Input: [Class] FormatConvertedBitmap [Description]

Output: Provides pixel format conversion functionality for a BitmapSource. This class cannot be inherited.


Input: [Class] GifBitmapDecoder [Description]

Output: Defines a decoder for Graphics Interchange Format (GIF) encoded images.


Input: [Class] GifBitmapEncoder [Description]

Output: Defines an encoder that is used to encode Graphics Interchange Format (GIF) images.


Input: [Class] IconBitmapDecoder [Description]

Output: Defines a specialized decoder for icon (.ico) encoded images. This class cannot be inherited.


Input: [Class] InPlaceBitmapMetadataWriter [Description]

Output: Enables in-place updates to existing blocks of BitmapMetadata. This class cannot be inherited.


Input: [Class] JpegBitmapDecoder [Description]

Output: Defines a decoder for Joint Photographics Experts Group (JPEG) encoded images. This class cannot be inherited.


Input: [Class] JpegBitmapEncoder [Description]

Output: Defines an encoder that is used to encode Joint Photographics Experts Group (JPEG) format images. This class cannot be inherited.


Input: [Class] LateBoundBitmapDecoder [Description]

Output: Defines a decoder that requires delayed bitmap creation such as asynchronous image downloads. This class cannot be inherited.


Input: [Class] PngBitmapDecoder [Description]

Output: Defines a decoder for Portable Network Graphics (PNG) encoded images. This class cannot be inherited.


Input: [Class] PngBitmapEncoder [Description]

Output: Defines an encoder that is used to encode Portable Network Graphics (PNG) format images. This class cannot be inherited.


Input: [Class] RenderTargetBitmap [Description]

Output: Used to convert a Visual object into a bitmap.


Input: [Class] TiffBitmapDecoder [Description]

Output: Defines a decoder for Tagged Image File Format (TIFF) encoded images. This class cannot be inherited.


Input: [Class] TiffBitmapEncoder [Description]

Output: Defines an encoder that is used to encode Tagged Image File Format (TIFF) format images.


Input: [Class] TransformedBitmap [Description]

Output: Scales and rotates a BitmapSource. This class cannot be inherited.


Input: [Class] WmpBitmapDecoder [Description]

Output: Defines a decoder for Microsoft Windows Media Photo encoded images. This class cannot be inherited.


Input: [Class] WmpBitmapEncoder [Description]

Output: Defines an encoder that is used to encode Microsoft Windows Media Photo images.


Input: [Class] WriteableBitmap [Description]

Output: Provides a BitmapSource that can be written to and updated.


Input: [Class] DocumentRouterAutoFolderSettings [Description]

Output: Configures automatic folder creation in a content organizer site.


Input: [Class] DocumentRoutingFeatureNotActiveException [Description]

Output: Indicates that the Content Organizer feature is not active.


Input: [Class] DocumentRoutingResult [Description]

Output: Represents the results of a document routing action performed by the content organizer.


Input: [Class] EcmDocumentRouter [Description]

Output: The EcmDocumentRouter class represents a content organizer that routes documents submitted to a Web site.


Input: [Class] EcmDocumentRouterRule [Description]

Output: Represents a rule that defines document-routing behavior for the content organizer.


Input: [Class] EcmDocumentRouterRuleCollection [Description]

Output: Represents the collection of rules that are used by the content organizer to organize submitted documents.


Input: [Class] EcmDocumentRoutingWeb [Description]

Output: Represents a repository abstraction that can be configured to automatically organize and manage incoming content.


Input: [Class] HoldingZoneExpirationAction [Description]

Output: Obsolete. This class and its members are reserved for internal use and are not intended to be used in your code.


Input: [Class] ItemCannotBeDeclaredUndeclaredRecordException [Description]

Output: Thrown when an item cannot be declared or when an item is undeclared as record.