Input: [Feature] Standalone use [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Standalone mixing component [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature group] Transforms (MFT or DMO) [Feature] Synchronous data processing [DirectShow] Yes [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Simple programming model [DirectShow] Yes [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Standalone use [DirectShow] Yes [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Multiple inputs and multiple outputs [DirectShow] Yes [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Dynamic number of streams [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Access to sample-level metadata [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] In-place processing [DirectShow] Yes [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Dynamic format changes [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Quality adjustment [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Feature] Rate change [DirectShow] No [Media Foundation]

Output: Yes

Migrating from DirectShow to Media Foundation


Input: [Use when] You need to support multiple versions of a service or may deploy an updated service in the future [Scenario]

Output: Service versioning


Input: [Use when] You must partition a service across multiple hosts [Scenario]

Output: Service data partitioning


Input: [Use when] You must dynamically reconfigure routing logic at runtime to handle changing service deployments [Scenario]

Output: Dynamic update


Input: [Use when] You must send one message to multiple endpoints [Scenario]

Output: Multicast


Input: [Use when] You receive messages over one transport protocol, and the destination endpoint uses a different protocol [Scenario]

Output: Protocol bridging


Input: [Use when] You need to provide resilience to network outages and communication failures [Scenario]

Output: Error Handling


Input: [Description] Gets or sets the list of Double values that represent the advance widths corresponding to the glyph indices. [Name]

Output: AdvanceWidths


Input: [Description] Gets or sets the baseline origin of the GlyphRun. [Name]

Output: BaselineOrigin


Input: [Description] Gets or sets the bidirectional nesting level of the GlyphRun. [Name]

Output: BidiLevel


Input: [Description] Gets or sets the list of Boolean values that determine whether there are caret stops for every UTF16 code point in the Unicode representing the GlyphRun. [Name]

Output: CaretStops


Input: [Description] Gets or sets the list of UTF16 code points that represent the Unicode content of the GlyphRun. [Name]

Output: Characters


Input: [Description] Gets or sets the list of UInt16 values that maps characters in the GlyphRun to glyph indices. [Name]

Output: ClusterMap


Input: [Description] Gets or sets the specific device font for which the GlyphRun has been optimized. [Name]

Output: DeviceFontName


Input: [Description] Gets or sets the em size used for rendering the GlyphRun. [Name]

Output: FontRenderingEmSize


Input: [Description] Gets or sets an array of UInt16 values that represent the glyph indices in the rendering physical font. [Name]

Output: GlyphIndices


Input: [Description] Gets or sets an array of Point values representing the offsets of the glyphs in the GlyphRun. [Name]

Output: GlyphOffsets


Input: [Description] Gets or sets the GlyphTypeface for the GlyphRun. [Name]

Output: GlyphTypeface


Input: [Description] Gets a value indicating whether there are any valid caret character hits within the GlyphRun. [Name]

Output: IsHitTestable


Input: [Description] Gets or sets a value indicating whether to rotate glyphs. [Name]

Output: IsSideways


Input: [Description] Gets or sets the XmlLanguage for the GlyphRun. [Name]

Output: Language


Input: [Folder] Build [Plug-in file] Build.xml [Description]

Output: Defines the tasks to configure the initial security permissions that are assigned to identities for Team Foundation Build and to upload the build template files.


Input: [Folder] Classification [Plug-in file] Classification.xml [Description]

Output: Defines the initial iterations and areas of a team project.


Input: [Folder] Groups and Permissions [Plug-in file] GroupsandPermissions.xml [Description]

Output: Defines the initial security groups of a team project and their permissions.


Input: [Folder] Lab [Plug-in file] Lab.xml [Description]

Output: Defines the tasks to configure the initial security permissions that are assigned to identities for Visual Studio Lab Management.


Input: [Folder] Reports [Plug-in file] ReportsTasks.xml [Description]

Output: Defines the initial reports for a team project and sets up the report site.


Input: [Folder] Test Management [Plug-in file] TestManagement.xml [Description]

Output: Defines the test management files to upload that will create the initial test variables, configurations, settings, and resolution states of a team project. These settings are used by Microsoft Test Manager.


Input: [Folder] Version Control [Plug-in file] VersionControl.xml [Description]

Output: Defines the initial security permissions for version control, check-in notes for a team project, and whether exclusive check-out is required.


Input: [Folder] WorkItem Tracking [Plug-in file] WorkItems.xml [Description]

Output: Defines the initial work item types, queries, and work item instances of a team project.


Input: [Folder] Windows SharePoint Services [Plug-in file] WssTasks.xml [Description]

Output: Defines the project portal for the team based on a template for a SharePoint site. Also defines template files and process guidance.


Input: [Resource] How Do I: Use MVVM in a Windows Phone Application [Description]

Output: A video that demonstrates how the MVVM pattern can be applied to Windows Phone applications.


Input: [Resource] Josh Smith Advanced MVVM [Description]

Output: Details on a book for developers looking to take their MVVM skills to the next level.


Input: [Resource] MVVM Light Toolkit [Description]

Output: A toolkit that comprises a set of components that help people get started with the MVVM pattern.


Input: [Resource] MVVM Foundation [Description]

Output: A small and concentrated library of classes that are useful when building MVVM applications.


Input: [Resource] John Grossman's MVVM Introduction [Description]

Output: An article with John Grossman's thoughts on using the MVVM pattern.


Input: [Resource] Karl Schifflett's MVVM in the box Training [Description]

Output: A feature extension that contains MVVM training that is consumed within Visual Studio 2010.


Input: [Resource] Windows Phone App Hub [Description]

Output: Additional documentation, code samples, and a community for Windows Phone development.


Input: [Resource] Windows Phone Development Documentation [Description]

Output: Official Windows Phone development documentation on MSDN.


Input: [Resource] Silverlight Documentation [Description]

Output: Official Silverlight and Silverlight for Windows Phone documentation on MSDN.


Input: [Resource] Code Samples for Windows Phone [Description]

Output: Downloadable code samples that supplement the Windows Phone documentation.


Input: [Resource] Windows Phone QuickStarts [Description]

Output: A collection of short topics that demonstrate tasks or features in Windows Phone development.


Input: [Resource] Windows Phone Developer Guide [Description]

Output: A developer guide that describes a scenario around a fictitious company that has decided to use Windows Phone 7 as a client device for their existing cloud-based application.


Input: [Resource] The Windows Phone Developer Blog [Description]

Output: A blog that contains current information and announcements straight from the Windows Phone team.


Input: [Resource] Jeff Wilcox Blog [Description]

Output: A blog about Silverlight, Silverlight Toolkit, and Silverlight for Windows Phone. Jeff Wilcox is a senior software developer at Microsoft on the Windows Phone team.


Input: [Resource] Jeff Prosise Blog [Description]

Output: A blog about various areas in .NET programming, including Silverlight and Windows Phone. Jeff Prosise is long-time Windows programmer and a cofounder of Wintellect.


Input: [Name] CheckCharacters [Description]

Output: Gets or sets a value indicating whether to do character checking.


Input: [Name] CloseOutput [Description]

Output: Gets or sets a value indicating whether the XmlWriter should also close the underlying stream or TextWriter when the Close method is called.


Input: [Name] ConformanceLevel [Description]

Output: Gets or sets the level of conformance which the XmlWriter complies with.


Input: [Name] Encoding [Description]

Output: Gets or sets the text encoding to use.


Input: [Name] Indent [Description]

Output: Gets or sets a value indicating whether to indent elements.


Input: [Name] IndentChars [Description]

Output: Gets or sets the character string to use when indenting. This setting is used when the Indent property is set to true.


Input: [Name] NewLineChars [Description]

Output: Gets or sets the character string to use for line breaks.


Input: [Name] NewLineHandling [Description]

Output: Gets or sets a value indicating whether to normalize line breaks in the output.


Input: [Name] NewLineOnAttributes [Description]

Output: Gets or sets a value indicating whether to write attributes on a new line.


Input: [Name] OmitXmlDeclaration [Description]

Output: Gets or sets a value indicating whether to write an XML declaration.


Input: [Name] OutputMethod [Description]

Output: Gets the method used to serialize the XmlWriter output.


Input: [Description] Gets or sets a value indicating whether to do character checking. [Name]

Output: CheckCharacters


Input: [Description] Gets or sets a value indicating whether the XmlWriter should also close the underlying stream or TextWriter when the Close method is called. [Name]

Output: CloseOutput


Input: [Description] Gets or sets the level of conformance which the XmlWriter complies with. [Name]

Output: ConformanceLevel


Input: [Description] Gets or sets the text encoding to use. [Name]

Output: Encoding


Input: [Description] Gets or sets a value indicating whether to indent elements. [Name]

Output: Indent


Input: [Description] Gets or sets the character string to use when indenting. This setting is used when the Indent property is set to true. [Name]

Output: IndentChars


Input: [Description] Gets or sets the character string to use for line breaks. [Name]

Output: NewLineChars


Input: [Description] Gets or sets a value indicating whether to normalize line breaks in the output. [Name]

Output: NewLineHandling


Input: [Description] Gets or sets a value indicating whether to write attributes on a new line. [Name]

Output: NewLineOnAttributes


Input: [Description] Gets or sets a value indicating whether to write an XML declaration. [Name]

Output: OmitXmlDeclaration


Input: [Description] Gets the method used to serialize the XmlWriter output. [Name]

Output: OutputMethod


Input: [Task] Getting started: Before you can use the features of the Team Foundation Server plug-in for Eclipse, you must first establish a connection to an instance of Visual Studio Team Foundation Server. [Supporting Content]

Output: Getting Started with Team Explorer Everywhere and Team Foundation Server

Team Foundation Server Plug-in for Eclipse


Input: [Task] Set up the local development environment: In most team development environments, you must obtain access to the correct version of the source code files. You then update your local computer with the source files for the parts of your application that you must update. [Supporting Content]

Output: Getting a Local Copy of Files from the Version Control Server (Team Explorer Everywhere) Using Source Control Explorer (Team Explorer Everywhere) Working with Team Foundation Server Workspaces (Team Explorer Everywhere) Using Version Control (Team Explorer Everywhere)

Team Foundation Server Plug-in for Eclipse


Input: [Task] Make code changes to accomplish a task or fix a bug: During a development cycle, you spend most of your time making code changes. This process includes selecting a task or bug, checking out the required files, modifying the code, and then verifying that your changes are correct before you check them in. This task includes making changes to both application code and database code. [Supporting Content]

Output: Perform Iterative Development Tasks Completing Development Tasks

Team Foundation Server Plug-in for Eclipse


Input: [Task] Create and request builds: You can use the integrated build system to perform automated builds on a scheduled basis or on demand. [Supporting Content]

Output: Building Applications (Team Explorer Everywhere)

Team Foundation Server Plug-in for Eclipse


Input: [Task] Define quality gates: You can specify check-in policies to help protect the quality of the source files that are checked into version control. [Supporting Content]

Output: Setting and Enforcing Quality Gates (Team Explorer Everywhere)

Team Foundation Server Plug-in for Eclipse


Input: [Task] Troubleshooting: If you encounter issues when you use Team Explorer Everywhere, you can find information about common issues and their resolutions. [Supporting Content]

Output: Troubleshooting Issues with Team Explorer Everywhere

Team Foundation Server Plug-in for Eclipse


Input: [Member name] AccessSystemSecurity [Description]

Output: The right to get or set permissions on a file.


Input: [Member name] ChangePermissions [Description]

Output: The right to change the security and audit rules associated with a file.


Input: [Member name] CopyOnWrite [Description]

Output: The right to read and write to a file with the restriction that write operations will not be seen by other processes.


Input: [Member name] Delete [Description]

Output: The right to delete a file.


Input: [Member name] Execute [Description]

Output: The right to run an application file.


Input: [Member name] FullControl [Description]

Output: The right to exert full control over a file, and to modify access control and audit rules. This value represents the right to do anything with a file and is the combination of all rights in this enumeration.


Input: [Member name] Read [Description]

Output: The right to open and copy a file as read-only.


Input: [Member name] ReadExecute [Description]

Output: The right to open and copy a folder or file as read-only, and to run application files. This right includes the Read right and the Execute right.


Input: [Member name] ReadPermissions [Description]

Output: The right to open and copy access and audit rules from a file. This does not include the right to read data, file system attributes, or extended file system attributes.


Input: [Member name] ReadWrite [Description]

Output: The right to open and copy a file, and the right to add data to a file or remove data from a file.


Input: [Member name] ReadWriteExecute [Description]

Output: The right to open and copy a file, the right to add data to a file or remove data from a file, and the right to run an application file.


Input: [Member name] TakeOwnership [Description]

Output: The right to change the owner of a file.


Input: [Member name] Write [Description]

Output: The right to add data to a file or remove data from a file.


Input: [Name] AdvanceWidths [Description]

Output: Gets or sets the list of Double values that represent the advance widths corresponding to the glyph indices.


Input: [Name] BaselineOrigin [Description]

Output: Gets or sets the baseline origin of the GlyphRun.


Input: [Name] BidiLevel [Description]

Output: Gets or sets the bidirectional nesting level of the GlyphRun.


Input: [Name] CaretStops [Description]

Output: Gets or sets the list of Boolean values that determine whether there are caret stops for every UTF16 code point in the Unicode representing the GlyphRun.


Input: [Name] Characters [Description]

Output: Gets or sets the list of UTF16 code points that represent the Unicode content of the GlyphRun.


Input: [Name] ClusterMap [Description]

Output: Gets or sets the list of UInt16 values that maps characters in the GlyphRun to glyph indices.


Input: [Name] DeviceFontName [Description]

Output: Gets or sets the specific device font for which the GlyphRun has been optimized.


Input: [Name] FontRenderingEmSize [Description]

Output: Gets or sets the em size used for rendering the GlyphRun.


Input: [Name] GlyphIndices [Description]

Output: Gets or sets an array of UInt16 values that represent the glyph indices in the rendering physical font.


Input: [Name] GlyphOffsets [Description]

Output: Gets or sets an array of Point values representing the offsets of the glyphs in the GlyphRun.


Input: [Name] GlyphTypeface [Description]

Output: Gets or sets the GlyphTypeface for the GlyphRun.


Input: [Name] IsHitTestable [Description]

Output: Gets a value indicating whether there are any valid caret character hits within the GlyphRun.


Input: [Name] IsSideways [Description]

Output: Gets or sets a value indicating whether to rotate glyphs.


Input: [Name] Language [Description]

Output: Gets or sets the XmlLanguage for the GlyphRun.


Input: [Description] SetGCStartupLimits returned successfully. [HRESULT]

Output: S_OK


Input: [Description] The common language runtime (CLR) has not been loaded into a process, or the CLR is in a state in which it cannot run managed code or process the call successfully. [HRESULT]

Output: HOST_E_CLRNOTAVAILABLE


Input: [Description] The call timed out. [HRESULT]

Output: HOST_E_TIMEOUT


Input: [Description] The caller does not own the lock. [HRESULT]

Output: HOST_E_NOT_OWNER


Input: [Description] An event was canceled while a blocked thread or fiber was waiting on it. [HRESULT]

Output: HOST_E_ABANDONED


Input: [Description] An unknown catastrophic failure occurred. After a method returns E_FAIL, the CLR is no longer usable within the process. Subsequent calls to hosting methods return HOST_E_CLRNOTAVAILABLE. [HRESULT]

Output: E_FAIL


Input: [Action] Insert a new line [Standard] ENTER or SHIFT+ENTER [SQL Server 2000]

Output: ENTER or SHIFT+ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Swap the characters on either side of the cursor (Does not apply to the SQL Editor.) [Standard] CTRL+T [SQL Server 2000]

Output: No equivalent

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete on character to the right of the cursor [Standard] DELETE [SQL Server 2000]

Output: DELETE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete one character to the left of the cursor [Standard] BACKSPACE or SHIFT+ BACKSPACE [SQL Server 2000]

Output: BACKSPACE or SHIFT+ BACKSPACE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert the number of spaces configured for the editor [Standard] TAB [SQL Server 2000]

Output: TAB

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert a blank line above the cursor [Standard] CTRL+ENTER [SQL Server 2000]

Output: CTRL+ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert a blank line below the cursor [Standard] CTRL+SHIFT+ ENTER [SQL Server 2000]

Output: CTRL+SHIFT+ ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Change the selected text to lowercase [Standard] CTRL+SHIFT+L [SQL Server 2000]

Output: CTRL+SHIFT+L

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Change the selected text to uppercase [Standard] CTRL+SHIFT+U [SQL Server 2000]

Output: CTRL+SHIFT+U

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Toggle between insertion mode and overtype mode [Standard] INSERT [SQL Server 2000]

Output: INSERT

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Move selected lines to the left on tab stop [Standard] SHIFT+TAB [SQL Server 2000]

Output: SHIFT+TAB

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete the word to the right of the cursor [Standard] CTRL+DELETE [SQL Server 2000]

Output: CTRL+DELETE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete the word to the left of the cursor [Standard] CTRL+BACKSPACE [SQL Server 2000]

Output: CTRL+BACKSPACE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Transpose the words on either side of the cursor (Does not apply to the SQL Editor.) [Standard] CTRL+SHIFT+T [SQL Server 2000]

Output: CTRL+SHIFT+T

SQL Server Management Studio Keyboard Shortcuts


Input: [Name] ActionUrl [Description]

Output: Gets or sets the target URL for the postback of a Web Forms page.


Input: [Name] Argument [Description]

Output: Gets or sets an optional argument that is transferred in the postback event.


Input: [Name] AutoPostBack [Description]

Output: Gets or sets a value that indicates whether the form will automatically post back to the server in response to a user action.


Input: [Name] ClientSubmit [Description]

Output: Gets or sets a value indicating whether the postback event should occur from client-side script.


Input: [Name] PerformValidation [Description]

Output: Gets or sets a value indicating whether client-side validation is required before the postback event occurs.


Input: [Name] RequiresJavaScriptProtocol [Description]

Output: Gets or sets a value indicating whether the javascript: prefix is generated for the client-side script.


Input: [Name] TargetControl [Description]

Output: Gets the control target that receives the postback event.


Input: [Name] TrackFocus [Description]

Output: Gets or sets a value indicating whether the postback event should return the page to the current scroll position and return focus to the current control.


Input: [Name] ValidationGroup [Description]

Output: Gets or sets the group of controls for which the PostBackOptions object causes validation when it posts back to the server.


Input: [Standard] ENTER or SHIFT+ENTER [SQL Server 2000] ENTER or SHIFT+ENTER [Action]

Output: Insert a new line

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+T [SQL Server 2000] No equivalent [Action]

Output: Swap the characters on either side of the cursor (Does not apply to the SQL Editor.)

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] DELETE [SQL Server 2000] DELETE [Action]

Output: Delete on character to the right of the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] BACKSPACE or SHIFT+ BACKSPACE [SQL Server 2000] BACKSPACE or SHIFT+ BACKSPACE [Action]

Output: Delete one character to the left of the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] TAB [SQL Server 2000] TAB [Action]

Output: Insert the number of spaces configured for the editor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+ENTER [SQL Server 2000] CTRL+ENTER [Action]

Output: Insert a blank line above the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+SHIFT+ ENTER [SQL Server 2000] CTRL+SHIFT+ ENTER [Action]

Output: Insert a blank line below the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+SHIFT+L [SQL Server 2000] CTRL+SHIFT+L [Action]

Output: Change the selected text to lowercase

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+SHIFT+U [SQL Server 2000] CTRL+SHIFT+U [Action]

Output: Change the selected text to uppercase

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] INSERT [SQL Server 2000] INSERT [Action]

Output: Toggle between insertion mode and overtype mode

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] SHIFT+TAB [SQL Server 2000] SHIFT+TAB [Action]

Output: Move selected lines to the left on tab stop

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+DELETE [SQL Server 2000] CTRL+DELETE [Action]

Output: Delete the word to the right of the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+BACKSPACE [SQL Server 2000] CTRL+BACKSPACE [Action]

Output: Delete the word to the left of the cursor

SQL Server Management Studio Keyboard Shortcuts


Input: [Standard] CTRL+SHIFT+T [SQL Server 2000] CTRL+SHIFT+T [Action]

Output: Transpose the words on either side of the cursor (Does not apply to the SQL Editor.)

SQL Server Management Studio Keyboard Shortcuts


Input: [Description] Navigation to a sibling object located below the starting object. [Member name]

Output: Down


Input: [Description] Navigation to the first child of the object. [Member name]

Output: FirstChild


Input: [Description] Navigation to the last child of the object. [Member name]

Output: LastChild


Input: [Description] Navigation to the sibling object located to the left of the starting object. [Member name]

Output: Left


Input: [Description] Navigation to the next logical object, typically from a sibling object to the starting object. [Member name]

Output: Next


Input: [Description] Navigation to the previous logical object, typically from a sibling object to the starting object. [Member name]

Output: Previous


Input: [Description] Navigation to the sibling object located to the right of the starting object. [Member name]

Output: Right


Input: [Description] Navigation to a sibling object located above the starting object. [Member name]

Output: Up


Input: [Name] AuthenticationScheme [Description]

Output: Gets or sets the authentication scheme to use to sign HTTP requests.


Input: [Name] BaseUri [Description]

Output: Gets the base URI for the Blob service client at the primary location.


Input: [Name] BufferManager [Description]

Output: Gets or sets a buffer manager that implements the IBufferManager interface, specifying a buffer pool for use with operations against the Blob service client.


Input: [Name] Credentials [Description]

Output: Gets the account credentials used to create the Blob service client.


Input: [Name] DefaultDelimiter [Description]

Output: Gets or sets the default delimiter that may be used to create a virtual directory structure of blobs.


Input: [Name] DefaultRequestOptions [Description]

Output: Gets or sets the default request options for requests made via the Blob service client.


Input: [Name] LocationMode [Description]

Output: Gets or sets the default location mode for requests made via the Blob service client. Obsolete.


Input: [Name] MaximumExecutionTime [Description]

Output: Gets or sets the maximum execution time across all potential retries. Obsolete.


Input: [Name] ParallelOperationThreadCount [Description]

Output: Gets or sets the number of blocks that may be simultaneously uploaded when uploading a blob that is greater than the value specified by the SingleBlobUploadThresholdInBytes property in size. Obsolete.


Input: [Name] RetryPolicy [Description]

Output: Gets or sets the default retry policy for requests made via the Blob service client. Obsolete.


Input: [Name] ServerTimeout [Description]

Output: Gets or sets the default server timeout for requests made via the Blob service client. Obsolete.


Input: [Name] SingleBlobUploadThresholdInBytes [Description]

Output: Gets or sets the maximum size of a blob in bytes that may be uploaded as a single blob. Obsolete.


Input: [Name] StorageUri [Description]

Output: Gets the Blob service endpoints for both the primary and secondary locations.


Input: [Description] Time sp_monitor was last run. [Column name]

Output: last_run


Input: [Description] Time sp_monitor is being run. [Column name]

Output: current_run


Input: [Description] Number of elapsed seconds since sp_monitor was run. [Column name]

Output: seconds


Input: [Description] Number of seconds that the server computer's CPU has been doing SQL Server work. [Column name]

Output: cpu_busy


Input: [Description] Number of seconds that SQL Server has spent doing input and output operations. [Column name]

Output: io_busy


Input: [Description] Number of seconds that SQL Server has been idle. [Column name]

Output: idle


Input: [Description] Number of input packets read by SQL Server. [Column name]

Output: packets_received


Input: [Description] Number of output packets written by SQL Server. [Column name]

Output: packets_sent


Input: [Description] Number of errors encountered by SQL Server while reading and writing packets. [Column name]

Output: packet_errors


Input: [Description] Number of reads by SQL Server. [Column name]

Output: total_read


Input: [Description] Number of writes by SQL Server. [Column name]

Output: total_write


Input: [Description] Number of errors encountered by SQL Server while reading and writing. [Column name]

Output: total_errors


Input: [Description] Number of logins or attempted logins to SQL Server. [Column name]

Output: connections


Input: [Value] The value of the attribute. [Node Type]

Output: Attribute


Input: [Value] The content of the CDATA section. [Node Type]

Output: CDATA


Input: [Value] The content of the comment. [Node Type]

Output: Comment


Input: [Value] The internal subset. [Node Type]

Output: DocumentType


Input: [Value] The entire content, excluding the target. [Node Type]

Output: ProcessingInstruction


Input: [Value] The white space between markup in a mixed content model. [Node Type]

Output: SignificantWhitespace


Input: [Value] The content of the text node. [Node Type]

Output: Text


Input: [Value] The white space between markup. [Node Type]

Output: Whitespace


Input: [Value] The content of the declaration. [Node Type]

Output: XmlDeclaration


Input: [To do this...] Create a text file.

Output: How to: Write Text to a File


Input: [To do this...] Write to a text file.

Output: How to: Write Text to a File


Input: [To do this...] Read from a text file.

Output: How to: Read Text from a File


Input: [To do this...] Append text to a file.

Output: How to: Open and Append to a Log File File.AppendText FileInfo.AppendText


Input: [To do this...] Rename or move a file.

Output: File.Move FileInfo.MoveTo


Input: [To do this...] Delete a file.

Output: File.Delete FileInfo.Delete


Input: [To do this...] Copy a file.

Output: File.Copy FileInfo.CopyTo


Input: [To do this...] Get the size of a file.

Output: FileInfo.Length


Input: [To do this...] Get the attributes of a file.

Output: File.GetAttributes


Input: [To do this...] Set the attributes of a file.

Output: File.SetAttributes


Input: [To do this...] Determine if a file exists.

Output: File.Exists


Input: [To do this...] Read from a binary file.

Output: How to: Read and Write to a Newly Created Data File


Input: [To do this...] Write to a binary file.

Output: How to: Read and Write to a Newly Created Data File


Input: [To do this...] Retrieve a file extension.

Output: Path.GetExtension


Input: [To do this...] Retrieve the fully qualified path of a file.

Output: Path.GetFullPath


Input: [To do this...] Retrieve the file name and extension from a path.

Output: Path.GetFileName


Input: [To do this...] Change the extension of a file.

Output: Path.ChangeExtension


Input: [Name] Add [Description]

Output: Adds the specified property to the property set.


Input: [Name] AddRange [Description]

Output: Adds the specified properties to the property set.


Input: [Name] Clear [Description]

Output: Removes all explicitly added properties from the property set.


Input: [Name] Contains [Description]

Output: Determines whether the specified property has been explicitly added to this property set by using the Add or AddRange methods.


Input: [Name] Equals [Description]

Output: (inherited from Object)


Input: [Name] Finalize [Description]

Output: (inherited from Object)


Input: [Name] GetEnumerator [Description]

Output: Returns an enumerator that iterates through the collection.


Input: [Name] GetHashCode [Description]

Output: (inherited from Object)


Input: [Name] GetType [Description]

Output: (inherited from Object)


Input: [Name] MemberwiseClone [Description]

Output: (inherited from Object)


Input: [Name] Remove [Description]

Output: Removes the specified property from the set.


Input: [Name] ToString [Description]

Output: (inherited from Object)


Input: [Name] CanDelete [Description]

Output: Gets a value that indicates whether the user is allowed to delete items from the table.


Input: [Name] CanInsert [Description]

Output: Gets a value that indicates whether the user is allowed to insert items into the table.


Input: [Name] CanRead [Description]

Output: Gets a value that indicates whether the user is allowed to read items in the table.


Input: [Name] CanUpdate [Description]

Output: Gets a value that indicates whether the user is allowed to update items in the table.


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

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


Input: [Name] EvaluateForeignKey [Description]

Output: Returns the value of a foreign key for the specified row.


Input: [Name] Finalize [Description]

Output: Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)


Input: [Name] GetHashCode [Description]

Output: Serves as the default hash function. (Inherited from Object.)


Input: [Name] GetQuery [Description]

Output: When overridden in a derived class, returns the System.Linq.IQueryable object that in turn returns the elements of the table.


Input: [Name] GetType [Description]

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


Input: [Name] GetTypeDescriptor [Description]

Output: Gets the type descriptor for the table.


Input: [Name] MemberwiseClone [Description]

Output: Creates a shallow copy of the current Object. (Inherited from Object.)


Input: [Name] ToString [Description]

Output: Returns the Name property of the TableProvider instance. (Overrides Object.ToString().)


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_VIDEOPROCFLAG_AUTO [Description]

Output: Camera driver uses its own processing logic for video.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_VIDEOPROCFLAG_MANUAL [Description]

Output: Camera driver uses a preset processing method or a temperature based method.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_VIDEOPROCFLAG_LOCK [Description]

Output: The current video processing method is locked.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_CONTINUOUS [Description]

Output: No converging focal point set.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_RANGE_MACRO [Description]

Output: Macro range focal convergence.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_RANGE_NORMAL [Description]

Output: Normal range focal convergence.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_RANGE_FULLRANGE [Description]

Output: Full range focal convergence.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_RANGE_INFINITY [Description]

Output: Infinite range focal convergence.


Input: [Processing and focus mode] KSCAMERA_EXTENDEDPROP_FOCUS_RANGE_HYPERFOCAL [Description]

Output: Hyperfocal range.


Input: [Meaning] TRUE if all of a set of comparisons are TRUE. [Operator]

Output: ALL


Input: [Meaning] TRUE if both Boolean expressions are TRUE. [Operator]

Output: AND


Input: [Meaning] TRUE if any one of a set of comparisons are TRUE. [Operator]

Output: ANY


Input: [Meaning] TRUE if the operand is within a range. [Operator]

Output: BETWEEN


Input: [Meaning] TRUE if a subquery contains any rows. [Operator]

Output: EXISTS


Input: [Meaning] TRUE if the operand is equal to one of a list of expressions. [Operator]

Output: IN


Input: [Meaning] TRUE if the operand matches a pattern. [Operator]

Output: LIKE


Input: [Meaning] Reverses the value of any other Boolean operator. [Operator]

Output: NOT


Input: [Meaning] TRUE if either Boolean expression is TRUE. [Operator]

Output: OR


Input: [Meaning] TRUE if some of a set of comparisons are TRUE. [Operator]

Output: SOME


Input: [Member name] Down [Description]

Output: Navigation to a sibling object located below the starting object.


Input: [Member name] FirstChild [Description]

Output: Navigation to the first child of the object.


Input: [Member name] LastChild [Description]

Output: Navigation to the last child of the object.


Input: [Member name] Left [Description]

Output: Navigation to the sibling object located to the left of the starting object.


Input: [Member name] Next [Description]

Output: Navigation to the next logical object, typically from a sibling object to the starting object.


Input: [Member name] Previous [Description]

Output: Navigation to the previous logical object, typically from a sibling object to the starting object.


Input: [Member name] Right [Description]

Output: Navigation to the sibling object located to the right of the starting object.


Input: [Member name] Up [Description]

Output: Navigation to a sibling object located above the starting object.


Input: [Class] Constants [Description]

Output: Contains storage constants.


Input: [Class] AnalyticsConstants [Description]

Output: Constants for analytics client


Input: [Class] ContinuationConstants [Description]

Output: Constants for Result Continuations


Input: [Class] HeaderConstants [Description]

Output: Constants for HTTP headers.


Input: [Class] QueryConstants [Description]

Output: Constants for query strings.


Input: [Class] VersionConstants [Description]

Output: Constants for version strings


Input: [Class] CorsProperties [Description]

Output: Class representing the service properties pertaining to CORS.


Input: [Class] CorsRule [Description]

Output: Class representing the service properties pertaining to CORS.


Input: [Class] GeoReplicationStats [Description]

Output: Class representing the geo-replication stats.


Input: [Class] ListingContext [Description]

Output: Represents the listing context for enumeration operations.


Input: [Class] LoggingProperties [Description]

Output: Class representing the service properties pertaining to logging.


Input: [Class] MetricsProperties [Description]

Output: Class representing the service properties pertaining to metrics.


Input: [Class] ResponseParsingBase [Description]

Output: Provides a base class that is used internally to parse XML streams from storage service operations.


Input: [Class] ServiceProperties [Description]

Output: Class representing a set of properties pertaining to a cloud storage service.


Input: [Class] ServiceStats [Description]

Output: Class representing a set of stats pertaining to a cloud storage service.


Input: [Class] StorageErrorCodeStrings [Description]

Output: Provides error code strings that are common to all storage services.


Input: [Description] Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source XAML content has been loaded, if the desired fragment is in different content. [Name]

Output: FragmentNavigation


Input: [Description] Occurs when content that was navigated to has been loaded, parsed, and has begun rendering. [Name]

Output: LoadCompleted


Input: [Description] Occurs when the content that is being navigated to has been found, and is available from the Content property, although it may not have completed loading. [Name]

Output: Navigated


Input: [Description] Occurs when a new navigation is requested. [Name]

Output: Navigating


Input: [Description] Occurs when an error occurs while navigating to the requested content. [Name]

Output: NavigationFailed


Input: [Description] Occurs periodically during a download to provide navigation progress information. [Name]

Output: NavigationProgress


Input: [Description] Occurs when the StopLoading method is called, or when a new navigation is requested while a current navigation is in progress. [Name]

Output: NavigationStopped


Input: [Action] Insert a new line [SQL Server 2000] ENTER or SHIFT+ENTER [Standard]

Output: ENTER or SHIFT+ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Swap the characters on either side of the cursor (Does not apply to the SQL Editor.) [SQL Server 2000] No equivalent [Standard]

Output: CTRL+T

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete on character to the right of the cursor [SQL Server 2000] DELETE [Standard]

Output: DELETE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete one character to the left of the cursor [SQL Server 2000] BACKSPACE or SHIFT+ BACKSPACE [Standard]

Output: BACKSPACE or SHIFT+ BACKSPACE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert the number of spaces configured for the editor [SQL Server 2000] TAB [Standard]

Output: TAB

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert a blank line above the cursor [SQL Server 2000] CTRL+ENTER [Standard]

Output: CTRL+ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Insert a blank line below the cursor [SQL Server 2000] CTRL+SHIFT+ ENTER [Standard]

Output: CTRL+SHIFT+ ENTER

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Change the selected text to lowercase [SQL Server 2000] CTRL+SHIFT+L [Standard]

Output: CTRL+SHIFT+L

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Change the selected text to uppercase [SQL Server 2000] CTRL+SHIFT+U [Standard]

Output: CTRL+SHIFT+U

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Toggle between insertion mode and overtype mode [SQL Server 2000] INSERT [Standard]

Output: INSERT

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Move selected lines to the left on tab stop [SQL Server 2000] SHIFT+TAB [Standard]

Output: SHIFT+TAB

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete the word to the right of the cursor [SQL Server 2000] CTRL+DELETE [Standard]

Output: CTRL+DELETE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Delete the word to the left of the cursor [SQL Server 2000] CTRL+BACKSPACE [Standard]

Output: CTRL+BACKSPACE

SQL Server Management Studio Keyboard Shortcuts


Input: [Action] Transpose the words on either side of the cursor (Does not apply to the SQL Editor.) [SQL Server 2000] CTRL+SHIFT+T [Standard]

Output: CTRL+SHIFT+T

SQL Server Management Studio Keyboard Shortcuts


Input: [Description] Represents a unique session with a data source. In the case of a client/server database system, the session may be equivalent to a network connection to the server. [Interface]

Output: IDbConnection

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Description] Represents a local transaction. [Interface]

Output: IDbTransaction

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Description] Represents a query or command that is used when connected to a data source. [Interface]

Output: IDbCommand

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Description] Represents a parameter or name/value pair that is passed to a command or query. [Interface]

Output: IDataParameter

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Description] Represents a collection of all parameters relevant to a command or query. [Interface]

Output: IDataParameterCollection

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Description] Provides a method of reading a forward-only, read-only stream of data from your data source. [Interface]

Output: IDataReader

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Node Type] Attribute [Value]

Output: The value of the attribute.


Input: [Node Type] CDATA [Value]

Output: The content of the CDATA section.


Input: [Node Type] Comment [Value]

Output: The content of the comment.


Input: [Node Type] DocumentType [Value]

Output: The internal subset.


Input: [Node Type] ProcessingInstruction [Value]

Output: The entire content, excluding the target.


Input: [Node Type] SignificantWhitespace [Value]

Output: The white space between markup in a mixed content model.


Input: [Node Type] Text [Value]

Output: The content of the text node.


Input: [Node Type] Whitespace [Value]

Output: The white space between markup.


Input: [Node Type] XmlDeclaration [Value]

Output: The content of the declaration.


Input: [Interface] IDbConnection [Description]

Output: Represents a unique session with a data source. In the case of a client/server database system, the session may be equivalent to a network connection to the server.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Interface] IDbTransaction [Description]

Output: Represents a local transaction.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Interface] IDbCommand [Description]

Output: Represents a query or command that is used when connected to a data source.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Interface] IDataParameter [Description]

Output: Represents a parameter or name/value pair that is passed to a command or query.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Interface] IDataParameterCollection [Description]

Output: Represents a collection of all parameters relevant to a command or query.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Interface] IDataReader [Description]

Output: Provides a method of reading a forward-only, read-only stream of data from your data source.

Using an ADO.NET DataSet as a Reporting Services Data Source


Input: [Supporting Content] Getting Started with Team Explorer Everywhere and Team Foundation Server [Task]

Output: Getting started: Before you can use the features of the Team Foundation Server plug-in for Eclipse, you must first establish a connection to an instance of Visual Studio Team Foundation Server.

Team Foundation Server Plug-in for Eclipse


Input: [Supporting Content] Getting a Local Copy of Files from the Version Control Server (Team Explorer Everywhere) Using Source Control Explorer (Team Explorer Everywhere) Working with Team Foundation Server Workspaces (Team Explorer Everywhere) Using Version Control (Team Explorer Everywhere) [Task]

Output: Set up the local development environment: In most team development environments, you must obtain access to the correct version of the source code files. You then update your local computer with the source files for the parts of your application that you must update.

Team Foundation Server Plug-in for Eclipse


Input: [Supporting Content] Perform Iterative Development Tasks Completing Development Tasks [Task]

Output: Make code changes to accomplish a task or fix a bug: During a development cycle, you spend most of your time making code changes. This process includes selecting a task or bug, checking out the required files, modifying the code, and then verifying that your changes are correct before you check them in. This task includes making changes to both application code and database code.

Team Foundation Server Plug-in for Eclipse


Input: [Supporting Content] Building Applications (Team Explorer Everywhere) [Task]

Output: Create and request builds: You can use the integrated build system to perform automated builds on a scheduled basis or on demand.

Team Foundation Server Plug-in for Eclipse


Input: [Supporting Content] Setting and Enforcing Quality Gates (Team Explorer Everywhere) [Task]

Output: Define quality gates: You can specify check-in policies to help protect the quality of the source files that are checked into version control.

Team Foundation Server Plug-in for Eclipse


Input: [Supporting Content] Troubleshooting Issues with Team Explorer Everywhere [Task]

Output: Troubleshooting: If you encounter issues when you use Team Explorer Everywhere, you can find information about common issues and their resolutions.

Team Foundation Server Plug-in for Eclipse


Input: [Plug-in file] Build.xml [Description] Defines the tasks to configure the initial security permissions that are assigned to identities for Team Foundation Build and to upload the build template files. [Folder]

Output: Build


Input: [Plug-in file] Classification.xml [Description] Defines the initial iterations and areas of a team project. [Folder]

Output: Classification


Input: [Plug-in file] GroupsandPermissions.xml [Description] Defines the initial security groups of a team project and their permissions. [Folder]

Output: Groups and Permissions


Input: [Plug-in file] Lab.xml [Description] Defines the tasks to configure the initial security permissions that are assigned to identities for Visual Studio Lab Management. [Folder]

Output: Lab


Input: [Plug-in file] ReportsTasks.xml [Description] Defines the initial reports for a team project and sets up the report site. [Folder]

Output: Reports


Input: [Plug-in file] TestManagement.xml [Description] Defines the test management files to upload that will create the initial test variables, configurations, settings, and resolution states of a team project. These settings are used by Microsoft Test Manager. [Folder]

Output: Test Management


Input: [Plug-in file] VersionControl.xml [Description] Defines the initial security permissions for version control, check-in notes for a team project, and whether exclusive check-out is required. [Folder]

Output: Version Control


Input: [Plug-in file] WorkItems.xml [Description] Defines the initial work item types, queries, and work item instances of a team project. [Folder]

Output: WorkItem Tracking


Input: [Plug-in file] WssTasks.xml [Description] Defines the project portal for the team based on a template for a SharePoint site. Also defines template files and process guidance. [Folder]

Output: Windows SharePoint Services


Input: [Name] FragmentNavigation [Description]

Output: Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source XAML content has been loaded, if the desired fragment is in different content.


Input: [Name] LoadCompleted [Description]

Output: Occurs when content that was navigated to has been loaded, parsed, and has begun rendering.


Input: [Name] Navigated [Description]

Output: Occurs when the content that is being navigated to has been found, and is available from the Content property, although it may not have completed loading.


Input: [Name] Navigating [Description]

Output: Occurs when a new navigation is requested.


Input: [Name] NavigationFailed [Description]

Output: Occurs when an error occurs while navigating to the requested content.


Input: [Name] NavigationProgress [Description]

Output: Occurs periodically during a download to provide navigation progress information.


Input: [Name] NavigationStopped [Description]

Output: Occurs when the StopLoading method is called, or when a new navigation is requested while a current navigation is in progress.


Input: [Derived dialog class] CColorDialog [Purpose]

Output: Lets user select colors.


Input: [Derived dialog class] CFileDialog [Purpose]

Output: Lets user select a filename to open or to save.


Input: [Derived dialog class] CFindReplaceDialog [Purpose]

Output: Lets user initiate a find or replace operation in a text file.


Input: [Derived dialog class] CFontDialog [Purpose]

Output: Lets user specify a font.


Input: [Derived dialog class] CPrintDialog [Purpose]

Output: Lets user specify information for a print job.


Input: [Derived dialog class] CPrintDialogEx [Purpose]

Output: Windows 2000 print property sheet.


Input: [Description] Gets a Rect that specifies the axis-aligned bounding box of the Geometry. (Inherited from Geometry.) [Name]

Output: Bounds


Input: [Description] Gets the Dispatcher this object is associated with. (Inherited from DependencyObject.) [Name]

Output: Dispatcher


Input: [Description] Gets or sets the x-radius of the ellipse that is used to round the corners of the rectangle. [Name]

Output: RadiusX


Input: [Description] Gets or sets the y-radius of the ellipse that is used to round the corners of the rectangle. [Name]

Output: RadiusY


Input: [Description] Gets or sets the dimensions of the rectangle. [Name]

Output: Rect


Input: [Description] Gets or sets the Transform object applied to a Geometry. (Inherited from Geometry.) [Name]

Output: Transform


Input: [Class] AlternateMailbox [Description]

Output: Contains information about an alternate to one of a user's mailboxes; for example, an archive of a user's inbox.


Input: [Class] AlternateMailboxCollection [Description]

Output: Represents a collection of alternate mailboxes for a user.


Input: [Class] AutodiscoverError [Description]

Output: Represents an error that is returned by the Autodiscover service.


Input: [Class] AutodiscoverRemoteException [Description]

Output: Represents an exception that is thrown when the Autodiscover service returns an error.


Input: [Class] AutodiscoverResponse [Description]

Output: Represents the base class for all responses that are returned by the Autodiscover service.


Input: [Class] AutodiscoverResponseCollection [Description]

Output: Contains a collection of responses to a call to the Autodiscover service.


Input: [Class] AutodiscoverResponseException [Description]

Output: Represents an exception that is thrown from an Autodiscover error response.


Input: [Class] AutodiscoverService [Description]

Output: Represents a binding to the Exchange Autodiscover service.


Input: [Class] DocumentSharingLocation [Description]

Output: Contains the location (URL) and metadata associated with a document sharing web service. The DocumentSharingLocation class is applicable for clients that target Exchange Online and versions of Exchange starting with Exchange Server 2013.


Input: [Class] DocumentSharingLocationCollection [Description]

Output: Contains a collection of document sharing locations. The DocumentSharingLocationCollection class is applicable for clients that target Exchange Online and versions of Exchange starting with Exchange Server 2013.


Input: [Class] DomainSettingError [Description]

Output: Represents an error from a GetDomainSettings request.


Input: [Class] GetDomainSettingsResponse [Description]

Output: Represents the response to a GetDomainSettings call for an individual domain.


Input: [Class] GetDomainSettingsResponseCollection [Description]

Output: Represents a collection of responses to a GetDomainSettings call.


Input: [Class] GetUserSettingsResponse [Description]

Output: Represents the response to a GetUsersSettings call for an individual user.


Input: [Class] GetUserSettingsResponseCollection [Description]

Output: Represents a collection of responses to a GetUserSettings call.


Input: [Class] ProtocolConnection [Description]

Output: Defines the protocol connection setting for the POP, IMAP, and SMTP protocols.


Input: [Class] ProtocolConnectionCollection [Description]

Output: A user setting that is a collection of protocol connections.


Input: [Class] UserSettingError [Description]

Output: An error message that is associated with a user setting error.


Input: [Class] WebClientUrl [Description]

Output: Represents the URL of an Exchange Web client.


Input: [Class] WebClientUrlCollection [Description]

Output: Represents a user setting that is a collection of Exchange Web client URLs.


Input: [Column name] last_run [Description]

Output: Time sp_monitor was last run.


Input: [Column name] current_run [Description]

Output: Time sp_monitor is being run.


Input: [Column name] seconds [Description]

Output: Number of elapsed seconds since sp_monitor was run.


Input: [Column name] cpu_busy [Description]

Output: Number of seconds that the server computer's CPU has been doing SQL Server work.


Input: [Column name] io_busy [Description]

Output: Number of seconds that SQL Server has spent doing input and output operations.


Input: [Column name] idle [Description]

Output: Number of seconds that SQL Server has been idle.


Input: [Column name] packets_received [Description]

Output: Number of input packets read by SQL Server.


Input: [Column name] packets_sent [Description]

Output: Number of output packets written by SQL Server.


Input: [Column name] packet_errors [Description]

Output: Number of errors encountered by SQL Server while reading and writing packets.


Input: [Column name] total_read [Description]

Output: Number of reads by SQL Server.


Input: [Column name] total_write [Description]

Output: Number of writes by SQL Server.


Input: [Column name] total_errors [Description]

Output: Number of errors encountered by SQL Server while reading and writing.


Input: [Column name] connections [Description]

Output: Number of logins or attempted logins to SQL Server.


Input: [Field] FIELD_NAME [Contents] Field names from selected table (128 characters wide) [Field type]

Output: Character


Input: [Field] FIELD_TYPE [Contents] Field types:C = CharacterY = CurrencyN = NumericF = FloatI = IntegerB = DoubleD = DateT = DateTimeL = LogicalM = MemoG = General [Field type]

Output: Character


Input: [Field] FIELD_LEN [Contents] Field widths [Field type]

Output: Numeric


Input: [Field] FIELD_DEC [Contents] Number of decimal places in numeric fields [Field type]

Output: Numeric


Input: [Field] FIELD_NULL [Contents] Field null value support [Field type]

Output: Logical


Input: [Field] FIELD_NOCP [Contents] Code page translation not allowed (character and memo fields only) [Field type]

Output: Logical


Input: [Field] FIELD_DEFA [Contents] Field default values [Field type]

Output: Memo


Input: [Field] FIELD_RULE [Contents] Field validation rules [Field type]

Output: Memo


Input: [Field] FIELD_ERR [Contents] Field validation text [Field type]

Output: Memo


Input: [Field] TABLE_RULE [Contents] Table validation rule [Field type]

Output: Memo


Input: [Field] TABLE_ERR [Contents] Table validation text [Field type]

Output: Memo


Input: [Field] TABLE_NAME [Contents] Long table name (first record only) [Field type]

Output: Character


Input: [Field] INS_TRIG [Contents] Insert trigger expression (first record only) [Field type]

Output: Memo


Input: [Field] UPD_TRIG [Contents] Update trigger expression (first record only) [Field type]

Output: Memo


Input: [Field] DEL_TRIG [Contents] Delete trigger expression (first record only) [Field type]

Output: Memo


Input: [Field] TABLE_CMT [Contents] Table comment (first record only) [Field type]

Output: Memo


Input: [Name] ContentLength [Description]

Output: When overridden in a descendant class, gets or sets the content length of data being received.


Input: [Name] ContentType [Description]

Output: When overridden in a derived class, gets or sets the content type of the data being received.


Input: [Name] Headers [Description]

Output: When overridden in a derived class, gets a collection of header name-value pairs associated with this request.


Input: [Name] IsFromCache [Description]

Output: Gets a Boolean value that indicates whether this response was obtained from the cache.


Input: [Name] IsMutuallyAuthenticated [Description]

Output: Gets a Boolean value that indicates whether mutual authentication occurred.


Input: [Name] ResponseUri [Description]

Output: When overridden in a derived class, gets the URI of the Internet resource that actually responded to the request.


Input: [Description] The ability to add a certificate to a store. For security reasons, this ability should be granted only to highly trusted code. [Member name]

Output: AddToStore


Input: [Description] The ability to perform all certificate and store operations. [Member name]

Output: AllFlags


Input: [Description] The ability to create a new store. New stores are created by calling the X509Store.Open method. [Member name]

Output: CreateStore


Input: [Description] The ability to delete a store. This functionality is not exposed by the X509Store class. [Member name]

Output: DeleteStore


Input: [Description] The ability to enumerate the certificates in a store. For privacy reasons, this ability should be granted only to fully trusted code. [Member name]

Output: EnumerateCertificates


Input: [Description] The ability to enumerate the stores on a computer. This functionality is not exposed by the X509Store class. [Member name]

Output: EnumerateStores


Input: [Description] Permission is not given to perform any certificate or store operations. [Member name]

Output: NoFlags


Input: [Description] The ability to open a store. The ability to open a store does not include the ability to enumerate certificates (which raises privacy concerns) or to add or remove certificates (which raises security concerns). [Member name]

Output: OpenStore


Input: [Description] The ability to remove a certificate from a store. This ability should be granted only to highly trusted code because removing a certificate can result in a denial of service. [Member name]

Output: RemoveFromStore


Input: [Interface] IControlDesignerBehavior [Description]

Output: Enables the extension of specific behaviors of a control designer.


Input: [Interface] IDataSourceProvider [Description]

Output: Defines an interface that a control designer can implement to provide access to a data source.


Input: [Interface] IHtmlControlDesignerBehavior [Description]

Output: Defines an interface that enables the extension of specific behaviors of an HTML control designer.


Input: [Interface] ITemplateEditingFrame [Description]

Output: Provides an interface to manage a template editing area.


Input: [Interface] ITemplateEditingService [Description]

Output: Provides services for editing control templates at design time.


Input: [Interface] IWebFormReferenceManager [Description]

Output: Provides an interface that can lookup information about the types used in the current Web Forms project.


Input: [Interface] IWebFormsBuilderUIService [Description]

Output: Provides methods to start specific user interfaces for building properties at design-time.


Input: [Interface] IWebFormsDocumentService [Description]

Output: Provides methods to access services for tracking the loading state of a Web Forms document, handling events at load time, accessing a document's location, managing a document's undo service, and setting a new selection within the document.


Input: [Class and members to use] The System.Environment class is the most complete source for these, either through its static methods, such as SystemDirectory, or through the GetFolderPath method, using one of the Environment.SpecialFolder enumerated values. [Path or program category]

Output: Standard Windows paths, such as Program Files, MyDocuments, the Desktop and so on


Input: [Class and members to use] The Application class has static members to obtain certain paths, such as StartupPath, ExecutablePath, LocalUserAppDataPath, and CommonAppDataPath. The GetTempPath method of the System.IO.Path returns the path of the temporary folder. The GetCurrentDirectory method of the System.IO.Directory class returns the application's current executing directory. The RootDirectory property of the DriveInfo class represents the specified drive's root directory. [Path or program category]

Output: Paths related to the current application


Input: [Class and members to use] Access the corresponding applications settings property of the wrapper class derived from ApplicationSettingsBase. For more information, see Application Settings for Windows Forms. [Path or program category]

Output: Paths stored as application settings


Input: [Class and members to use] Some applications store directory information in the registry. The Application class has the CommonAppDataPath and LocalUserAppDataPath properties that resolve to a RegistryKey value. [Path or program category]

Output: Registry storage


Input: [Class and members to use] For ClickOnce applications, use Application class members such as UserAppDataPath, which will return a pointer to the ClickOnce data directory. For more information, see Accessing Local and Remote Data in ClickOnce Applications. [Path or program category]

Output: ClickOnce applications


Input: [Class and members to use] For international applications, retrieve the relative path portion from a string resource in your application by using the System.Resources.ResourceReader class. For more information about globalization and localization, see the topic Encoding and Localization. [Path or program category]

Output: International applications


Input: [Reserved path and file names] /Package.appxmanifest [Use]

Output: Reserved file name for the developer-authored app package manifest

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Reserved path and file names] /AppxBlockMap.xml [Use]

Output: Reserved file name for app package block map

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Reserved path and file names] /AppxSignature.p7x [Use]

Output: Reserved file name for app package Microsoft Authenticode digital signature

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Reserved path and file names] /[Content_Types].xml [Use]

Output: Reserved file name for content types metadata required by OPC for the app package

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Reserved path and file names] /AppxMetadata/ [Use]

Output: Reserved folder path for app package metadata files

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Reserved path and file names] /Microsoft.System.Package.Metadata/ [Use]

Output: Reserved folder path for Microsoft metadata files about deployed app packages

App packages and deployment (Windows Runtime apps) - Windows app development


Input: [Capability scenario] Music [Capability usage]

Output: The musicLibrary capability provides programmatic access to the user's Music, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in jukebox apps that make use of the entire Music library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the musicLibrary capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically.

App capability declarations - Windows app development


Input: [Capability scenario] Pictures [Capability usage]

Output: The picturesLibrary capability provides programmatic access to the user's Pictures, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in photo apps that make use of the entire Pictures library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the picturesLibrary capability only when the scenarios for your app require programmatic access and can't be realized them by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically.

App capability declarations - Windows app development


Input: [Capability scenario] Videos [Capability usage]

Output: The videosLibrary capability provides programmatic access to the user's Videos, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in movie-playback apps that make use of the entire Videos library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the videosLibrary capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically.

App capability declarations - Windows app development


Input: [Capability scenario] Removable Storage [Capability usage]

Output: The removableStorage capability provides programmatic access to files on removable storage, like USB keys and external hard drives, filtered to the file-type associations declared in the package manifest. For example, if a document-reader app declares a .doc file-type association, it can open .doc files on the removable storage device, but not other types of files. Be careful when declaring this capability, because users may include a variety of info in their removable storage devices, and will expect your app to provide a valid justification for programmatic access to the removable storage for all files of the declared type. Users will expect your app to handle any file associations that you declare. So don't declare file associations that your app cannot handle responsibly. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the removableStorage capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker.

App capability declarations - Windows app development


Input: [Capability scenario] Internet and public networks [Capability usage]

Output: There are two capabilities that provide different levels of access to the Internet and public networks. These capabilities grant different access depending on if the app is running on Windows or Windows Phone. On Windows, the internetClient capability indicates that apps can receive incoming data from the Internet. Cannot act as a server. No local network access. On Windows, the internetClientServer capability indicates that apps can receive incoming data from the Internet. Can act as a server. No local network access. On Windows Phone, the internetClient capability indicates that apps have full local and Internet access and can act as a server. Inbound access to critical ports is always blocked. On Windows Phone, the internetClientServer capability indicates that apps have full local and Internet access and can act as a server. Inbound access to critical ports is always blocked. On Windows, most apps that have a web service component will use internetClient. Apps that enable peer-to-peer (P2P) scenarios where the app needs to listen for incoming network connections should use internetClientServer. The internetClientServer capability includes the access that the internetClient capability provides, so you don't need to specify internetClient when you specify internetClientServer. Note Windows Phone Store apps have a single network capability that enables all network access for the app. The internetClientServer capability enables complete access to the network for both client operations (outbound access) and server operations (inbound access). However, if any of the network capabilities (internetClient, internetClientServer, or privateNetworkClientServer) are specified in the Package.appxmanifest file, a Windows Phone Store app has complete access to the network at run time for both client and server operations. While you’re developing and testing your Windows Phone Store app app in Visual Studio, you get the networking capability (Internet (Client & Server)) when you run the app, even if you haven’t specified this capability in the app manifest file. When you publish your app, however, your app does not automatically get the networking capability. Make sure you check the Internet (Client & Server) capability on the Capabilities page of Manifest Designer if your app requires network connectivity.

App capability declarations - Windows app development


Input: [Capability scenario] Homes and work networks [Capability usage]

Output: The privateNetworkClientServer capability provides inbound and outbound access to home and work networks through the firewall. This capability is typically used for games that communicate across the local area network (LAN), and for apps that share data across a variety of local devices. If your app specifies musicLibrary, picturesLibrary, or videosLibrary, you don't need to use this capability to access the corresponding library in a Home Group. On Windows, this capability does not provide access to the Internet. On Windows Phone, this capability provides the same access as internetClient or internetClientServer.

App capability declarations - Windows app development


Input: [Capability scenario] Appointments [Capability usage]

Output: The appointments capability provides access to the user’s appointment store. This capability allows read access to appointments obtained from the synced network accounts and to other apps that write to the appointment store. With this capability, your app can create new calendars and write appointments to calendars that it creates.

App capability declarations - Windows app development


Input: [Capability scenario] Contacts [Capability usage]

Output: The contacts capability provides access to the aggregated view of the contacts from various contacts stores. This capability gives the app limited access (network permitting rules apply) to contacts that were synced from various networks and the local contact store.

App capability declarations - Windows app development


Input: [Capability scenario] Code generation [Capability usage]

Output: The codeGeneration capability allows apps to generate code dynamically.

App capability declarations - Windows app development


Input: [Capability scenario] AllJoyn [Capability usage]

Output: The allJoyn capability allows AllJoyn-enabled apps and devices on a network to discover and interact with each other. All apps that access APIs in the Windows.Devices.AllJoyn namespace must use this capability..

App capability declarations - Windows app development


Input: [Capability scenario] Phone calls [Capability usage]

Output: The phoneCall capability allows apps to access all of the phone lines on the device and perform the following functions. Place a call on the phone line and show the system dialer without prompting the user. Access line-related metadata. Access line-related triggers. Allows the user-selected spam filter app to set and check block list and call origin information.

App capability declarations - Windows app development


Input: [Capability scenario] Recorded Calls Folder [Capability usage]

Output: The recordedCallsFolder device capability allows apps to access the recorded calls folder.

App capability declarations - Windows app development


Input: [Capability scenario] User Account Information [Capability usage]

Output: The userAccountInformation capability gives apps the ability to access the user's name and picture. This capability is required to access some APIs in the Windows.System.User namespace.

App capability declarations - Windows app development


Input: [Capability scenario] VOIP calling [Capability usage]

Output: The voipCall capability allows apps to access the VOIP calling APIs in the Windows.ApplicationModel.Calls namespace.

App capability declarations - Windows app development


Input: [Capability scenario] 3D Objects [Capability usage]

Output: The objects3d capability allows apps to have programmatic access to the 3D object files. This capability is typically used in 3D apps and games that need access to the entire 3D objects library. This capability is required to access the folder that contains the 3d objects using APIs in the Windows.Storage namespace.

App capability declarations - Windows app development


Input: [Capability scenario] Read Blocked Messages [Capability usage]

Output: The blockedChatMessages capability allows apps to read SMS and MMS messages that have been blocked by the Spam Filter app. This capability is required to access the blocked messages using APIs in the Windows.ApplicationModel.Chat namespace.

App capability declarations - Windows app development


Input: [Capability scenario] Chat Message Access [Capability usage]

Output: The chat capability allows apps to read and delete text messages. This capability also allows apps to store chat messages in the system datastore. This capability is required to use APIs in the Windows.ApplicationModel.Chat namespace.

App capability declarations - Windows app development


Input: [Method] AddVisual [Description]

Output: Adds a new child visual to the children list of this visual.


Input: [Method] RemoveAllVisuals [Description]

Output: Removes all visuals from the children list of this visual.


Input: [Method] RemoveVisual [Description]

Output: Removes a child visual from the children list of this visual.


Input: [Method] SetBitmapInterpolationMode [Description]

Output: Sets the BitmapInterpolationMode property, which specifies the mode for DirectComposition to use when interpolating pixels from bitmaps that are not axis-aligned or drawn exactly at scale.


Input: [Method] SetBorderMode [Description]

Output: Sets the BorderMode property, which specifies how to compose the edges of bitmaps and clips associated with this visual, or with visuals in the subtree rooted at this visual.


Input: [Method] SetClip [Description]

Output: Overloaded. Sets the Clip property of this visual to the specified rectangular region or clip object.


Input: [Method] SetCompositeMode [Description]

Output: Sets the blending mode for this visual.


Input: [Method] SetContent [Description]

Output: Sets the Content property of this visual to the specified bitmap or window wrapper.


Input: [Method] SetEffect [Description]

Output: Sets the Effect property of this visual.


Input: [Method] SetOffsetX [Description]

Output: Overloaded. Changes or animates the value of the OffsetX property of this visual, altering the horizontal position of the visual relative to its parent.


Input: [Method] SetOffsetY [Description]

Output: Overloaded. Changes or animates the value of the OffsetY property of this visual, altering the vertical position of the visual relative to its parent.


Input: [Method] SetTransform [Description]

Output: Overloaded. Sets the Transform property of this visual. The Transform property specifies a 2D transform used to modify the coordinate system of this visual. The property can specify either a 3-by-2 transform matrix or a transform object.


Input: [Method] SetTransformParent [Description]

Output: Sets the TransformParent property of this visual. The TransformParent property establishes the coordinate system relative to which this visual is composed.


Input: [Name] Add [Description]

Output: Adds the specified value to the dictionary by using the specified key.


Input: [Name] Clear [Description]

Output: Removes all keys and values from the dictionary.


Input: [Name] ContainsKey [Description]

Output: Determines whether the dictionary contains the specified key.


Input: [Name] ContainsValue [Description]

Output: Determines whether the dictionary contains a specific value.


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: Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)


Input: [Name] GetEnumerator [Description]

Output: Returns an enumerator that you can use to iterate through the dictionary.


Input: [Name] GetHashCode [Description]

Output: Serves as the default hash function. (Inherited from Object.)


Input: [Name] GetType [Description]

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


Input: [Name] MemberwiseClone [Description]

Output: Creates a shallow copy of the current Object. (Inherited from Object.)


Input: [Name] Remove [Description]

Output: Removes the value that has the specified key from the dictionary.


Input: [Name] ToString [Description]

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


Input: [Name] TryGetValue [Description]

Output: Gets a value that indicates whether a value is associated with the specified key.


Input: [Name] CertificatePolicy [Description]

Output: Obsolete. Gets or sets policy for server certificates.


Input: [Name] CheckCertificateRevocationList [Description]

Output: Gets or sets a Boolean value that indicates whether the certificate is checked against the certificate authority revocation list.


Input: [Name] DefaultConnectionLimit [Description]

Output: Gets or sets the maximum number of concurrent connections allowed by a ServicePoint object.


Input: [Name] DnsRefreshTimeout [Description]

Output: Gets or sets a value that indicates how long a Domain Name Service (DNS) resolution is considered valid.


Input: [Name] EnableDnsRoundRobin [Description]

Output: Gets or sets a value that indicates whether a Domain Name Service (DNS) resolution rotates among the applicable Internet Protocol (IP) addresses.


Input: [Name] EncryptionPolicy [Description]

Output: Gets the System.Net.Security.EncryptionPolicy for this ServicePointManager instance.


Input: [Name] Expect100Continue [Description]

Output: Gets or sets a Boolean value that determines whether 100-Continue behavior is used.


Input: [Name] MaxServicePointIdleTime [Description]

Output: Gets or sets the maximum idle time of a ServicePoint object.


Input: [Name] MaxServicePoints [Description]

Output: Gets or sets the maximum number of ServicePoint objects to maintain at any time.


Input: [Name] SecurityProtocol [Description]

Output: Gets or sets the security protocol used by the ServicePoint objects managed by the ServicePointManager object.


Input: [Name] ServerCertificateValidationCallback [Description]

Output: Gets or sets the callback to validate a server certificate.


Input: [Name] UseNagleAlgorithm [Description]

Output: Determines whether the Nagle algorithm is used by the service points managed by this ServicePointManager object.


Input: [Capability usage] The musicLibrary capability provides programmatic access to the user's Music, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in jukebox apps that make use of the entire Music library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the musicLibrary capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically. [Capability scenario]

Output: Music

App capability declarations - Windows app development


Input: [Capability usage] The picturesLibrary capability provides programmatic access to the user's Pictures, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in photo apps that make use of the entire Pictures library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the picturesLibrary capability only when the scenarios for your app require programmatic access and can't be realized them by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically. [Capability scenario]

Output: Pictures

App capability declarations - Windows app development


Input: [Capability usage] The videosLibrary capability provides programmatic access to the user's Videos, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in movie-playback apps that make use of the entire Videos library. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the videosLibrary capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker. For an example of how to access files in a library, see Quickstart: Accessing files programmatically. [Capability scenario]

Output: Videos

App capability declarations - Windows app development


Input: [Capability usage] The removableStorage capability provides programmatic access to files on removable storage, like USB keys and external hard drives, filtered to the file-type associations declared in the package manifest. For example, if a document-reader app declares a .doc file-type association, it can open .doc files on the removable storage device, but not other types of files. Be careful when declaring this capability, because users may include a variety of info in their removable storage devices, and will expect your app to provide a valid justification for programmatic access to the removable storage for all files of the declared type. Users will expect your app to handle any file associations that you declare. So don't declare file associations that your app cannot handle responsibly. The file picker provides a robust UI mechanism that lets users open files for use with an app. Declare the removableStorage capability only when the scenarios for your app require programmatic access and can't be realized by using the file picker. [Capability scenario]

Output: Removable Storage

App capability declarations - Windows app development


Input: [Capability usage] There are two capabilities that provide different levels of access to the Internet and public networks. These capabilities grant different access depending on if the app is running on Windows or Windows Phone. On Windows, the internetClient capability indicates that apps can receive incoming data from the Internet. Cannot act as a server. No local network access. On Windows, the internetClientServer capability indicates that apps can receive incoming data from the Internet. Can act as a server. No local network access. On Windows Phone, the internetClient capability indicates that apps have full local and Internet access and can act as a server. Inbound access to critical ports is always blocked. On Windows Phone, the internetClientServer capability indicates that apps have full local and Internet access and can act as a server. Inbound access to critical ports is always blocked. On Windows, most apps that have a web service component will use internetClient. Apps that enable peer-to-peer (P2P) scenarios where the app needs to listen for incoming network connections should use internetClientServer. The internetClientServer capability includes the access that the internetClient capability provides, so you don't need to specify internetClient when you specify internetClientServer. Note Windows Phone Store apps have a single network capability that enables all network access for the app. The internetClientServer capability enables complete access to the network for both client operations (outbound access) and server operations (inbound access). However, if any of the network capabilities (internetClient, internetClientServer, or privateNetworkClientServer) are specified in the Package.appxmanifest file, a Windows Phone Store app has complete access to the network at run time for both client and server operations. While you’re developing and testing your Windows Phone Store app app in Visual Studio, you get the networking capability (Internet (Client & Server)) when you run the app, even if you haven’t specified this capability in the app manifest file. When you publish your app, however, your app does not automatically get the networking capability. Make sure you check the Internet (Client & Server) capability on the Capabilities page of Manifest Designer if your app requires network connectivity. [Capability scenario]

Output: Internet and public networks

App capability declarations - Windows app development


Input: [Capability usage] The privateNetworkClientServer capability provides inbound and outbound access to home and work networks through the firewall. This capability is typically used for games that communicate across the local area network (LAN), and for apps that share data across a variety of local devices. If your app specifies musicLibrary, picturesLibrary, or videosLibrary, you don't need to use this capability to access the corresponding library in a Home Group. On Windows, this capability does not provide access to the Internet. On Windows Phone, this capability provides the same access as internetClient or internetClientServer. [Capability scenario]

Output: Homes and work networks

App capability declarations - Windows app development


Input: [Capability usage] The appointments capability provides access to the user’s appointment store. This capability allows read access to appointments obtained from the synced network accounts and to other apps that write to the appointment store. With this capability, your app can create new calendars and write appointments to calendars that it creates. [Capability scenario]

Output: Appointments

App capability declarations - Windows app development


Input: [Capability usage] The contacts capability provides access to the aggregated view of the contacts from various contacts stores. This capability gives the app limited access (network permitting rules apply) to contacts that were synced from various networks and the local contact store. [Capability scenario]

Output: Contacts

App capability declarations - Windows app development


Input: [Capability usage] The codeGeneration capability allows apps to generate code dynamically. [Capability scenario]

Output: Code generation

App capability declarations - Windows app development


Input: [Capability usage] The allJoyn capability allows AllJoyn-enabled apps and devices on a network to discover and interact with each other. All apps that access APIs in the Windows.Devices.AllJoyn namespace must use this capability.. [Capability scenario]

Output: AllJoyn

App capability declarations - Windows app development


Input: [Capability usage] The phoneCall capability allows apps to access all of the phone lines on the device and perform the following functions. Place a call on the phone line and show the system dialer without prompting the user. Access line-related metadata. Access line-related triggers. Allows the user-selected spam filter app to set and check block list and call origin information. [Capability scenario]

Output: Phone calls

App capability declarations - Windows app development


Input: [Capability usage] The recordedCallsFolder device capability allows apps to access the recorded calls folder. [Capability scenario]

Output: Recorded Calls Folder

App capability declarations - Windows app development


Input: [Capability usage] The userAccountInformation capability gives apps the ability to access the user's name and picture. This capability is required to access some APIs in the Windows.System.User namespace. [Capability scenario]

Output: User Account Information

App capability declarations - Windows app development


Input: [Capability usage] The voipCall capability allows apps to access the VOIP calling APIs in the Windows.ApplicationModel.Calls namespace. [Capability scenario]

Output: VOIP calling

App capability declarations - Windows app development


Input: [Capability usage] The objects3d capability allows apps to have programmatic access to the 3D object files. This capability is typically used in 3D apps and games that need access to the entire 3D objects library. This capability is required to access the folder that contains the 3d objects using APIs in the Windows.Storage namespace. [Capability scenario]

Output: 3D Objects

App capability declarations - Windows app development


Input: [Capability usage] The blockedChatMessages capability allows apps to read SMS and MMS messages that have been blocked by the Spam Filter app. This capability is required to access the blocked messages using APIs in the Windows.ApplicationModel.Chat namespace. [Capability scenario]

Output: Read Blocked Messages

App capability declarations - Windows app development


Input: [Capability usage] The chat capability allows apps to read and delete text messages. This capability also allows apps to store chat messages in the system datastore. This capability is required to use APIs in the Windows.ApplicationModel.Chat namespace. [Capability scenario]

Output: Chat Message Access

App capability declarations - Windows app development


Input: [0] Functionality [1] UWF [2] EWF [3]

Output: FBWF


Input: [0] File/folder exclusions [1] Yes [2] No [3]

Output: Yes


Input: [0] Registry key exclusions [1] Yes [2] No* [3]

Output: No*


Input: [0] Sector-based filtering [1] Yes [2] Yes [3]

Output: No


Input: [0] Supports Hibernate Once/Resume Many (HORM) [1] Yes [2] No [3]

Output: No


Input: [0] RAM-based overlay [1] Yes [2] Yes [3]

Output: Yes


Input: [0] Providers for Windows Management Instrumentation (WMI) version 2 [1] Yes [2] No [3]

Output: No


Input: [0] Disk-backed overlay [1] Yes [2] No [3]

Output: No


Input: [0] Commit volume [1] No [2] Yes [3]

Output: No


Input: [0] Commit file [1] Yes [2] No [3]

Output: Yes


Input: [Component] Database Engine server components [Default path1, 2] \Program Files\Microsoft SQL Server\MSSQL10.\ [Configurable3 or Fixed Path]

Output: Configurable

File Locations for Default and Named Instances of SQL Server


Input: [Component] Database Engine data files [Default path1, 2] \Program Files\Microsoft SQL Server\MSSQL10.\ [Configurable3 or Fixed Path]

Output: Configurable

File Locations for Default and Named Instances of SQL Server


Input: [Component] Analysis Services server [Default path1, 2] \Program Files\Microsoft SQL Server\MSAS10.\ [Configurable3 or Fixed Path]

Output: Configurable

File Locations for Default and Named Instances of SQL Server


Input: [Component] Analysis Services data files [Default path1, 2] \Program Files\Microsoft SQL Server\MSAS10.\ [Configurable3 or Fixed Path]

Output: Configurable

File Locations for Default and Named Instances of SQL Server


Input: [Component] Reporting Services report server [Default path1, 2] \Program Files\Microsoft SQL Server\MSRS10.\Reporting Services\ReportServer\Bin\ [Configurable3 or Fixed Path]

Output: Configurable

File Locations for Default and Named Instances of SQL Server


Input: [Component] Reporting Services report manager [Default path1, 2] \Program Files\Microsoft SQL Server\MSRS10.\Reporting Services\ReportManager\ [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] Integration Services [Default path1, 2] \100\DTS\ [Configurable3 or Fixed Path]

Output: Configurable4

File Locations for Default and Named Instances of SQL Server


Input: [Component] Client Components [Default path1, 2] \100\Tools\ [Configurable3 or Fixed Path]

Output: Configurable4

File Locations for Default and Named Instances of SQL Server


Input: [Component] Replication and server-side COM objects [Default path1, 2] :\Program Files\Microsoft SQL Server\100\COM\5 [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] Integration Services component DLLs for the Data Transformation Run-time engine, the Data Transformation Pipeline engine, and the dtexec command prompt utility [Default path1, 2] :\Program Files\Microsoft SQL Server\100\DTS\Binn [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] DLLs that provide managed connection support for Integration Services [Default path1, 2] :\Program Files\Microsoft SQL Server\100\DTS\Connections [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] DLLs for each type of enumerator that Integration Services supports [Default path1, 2] :\Program Files\Microsoft SQL Server\100\DTS\ForEachEnumerators [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] SQL Server Browser Service, WMI providers [Default path1, 2] :\Program Files\Microsoft SQL Server\100\Shared\ [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Component] Components that are shared between all instances of SQL Server [Default path1, 2] :\Program Files\Microsoft SQL Server\100\Shared\ [Configurable3 or Fixed Path]

Output: Fixed path

File Locations for Default and Named Instances of SQL Server


Input: [Option] @ [Purpose]

Output: Specifies a response file.


Input: [Option] /ALIGN [Purpose]

Output: Specifies the alignment of each section.


Input: [Option] /ALLOWBIND [Purpose]

Output: Specifies that a DLL cannot be bound.


Input: [Option] /ALLOWISOLATION [Purpose]

Output: Specifies behavior for manifest lookup.


Input: [Option] /APPCONTAINER [Purpose]

Output: Specifies whether the app must run within an appcontainer process environment.


Input: [Option] /ASSEMBLYDEBUG [Purpose]

Output: Adds the DebuggableAttribute to a managed image.


Input: [Option] /ASSEMBLYLINKRESOURCE [Purpose]

Output: Creates a link to a managed resource.


Input: [Option] /ASSEMBLYMODULE [Purpose]

Output: Specifies that a Microsoft intermediate language (MSIL) module should be imported into the assembly.


Input: [Option] /ASSEMBLYRESOURCE [Purpose]

Output: Embeds a managed resource file in an assembly.


Input: [Option] /BASE [Purpose]

Output: Sets a base address for the program.


Input: [Option] /CGTHREADS [Purpose]

Output: Sets number of cl.exe threads to use for optimization and code generation when link-time code generation is specified.


Input: [Option] /CLRIMAGETYPE [Purpose]

Output: Sets the type (IJW, pure, or safe) of a CLR image.


Input: [Option] /CLRSUPPORTLASTERROR [Purpose]

Output: Preserves the last error code of functions that are called through the P/Invoke mechanism.


Input: [Option] /CLRTHREADATTRIBUTE [Purpose]

Output: Specifies the threading attribute to apply to the entry point of your CLR program.


Input: [Option] /CLRUNMANAGEDCODECHECK [Purpose]

Output: Specifies whether the linker will apply the SuppressUnmanagedCodeSecurity attribute to linker-generated PInvoke stubs that call from managed code into native DLLs.


Input: [Option] /DEBUG [Purpose]

Output: Creates debugging information.


Input: [Option] /DEBUGTYPE [Purpose]

Output: Specifies which data to include in debugging information.


Input: [Option] /DEF [Purpose]

Output: Passes a module-definition (.def) file to the linker.