### System.Configuration.Install.Installer Class Properties

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Descriptions for key properties of the `Installer` base class, which manages the installation process for components.

```APIDOC
Desc_Installer_HelpText: The help text for all the installers in the installer collection
Desc_Installer_Parent: The installer containing the collection that this installer belongs to
```

--------------------------------

### Common Installation Error and Warning Messages

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

A collection of string constants used for error reporting and warnings within the .NET installation framework, providing context for various installation failures or conditions.

```APIDOC
PerfInvalidCategoryName: Invalid category name. Its length must be in the range between '{0}' and '{1}'. Double quotes, control characters and leading or trailing spaces are not allowed.
NotCustomPerformanceCategory: You cannot create an installer for a system or a nonextensible PerformanceCategory.
RemovingInstallState: Remove InstallState file because there are no installers.
InstallUnableDeleteFile: Unable to delete file {0}.
InstallInitializeException: Exception occurred while initializing the installation:\r\n{0}: {1}.
InstallFileDoesntExist: File {0} does not exist.
InstallFileDoesntExistCommandLine: File {0} does not exist. If this parameter is used as an installer option, the format must be /key=[value].
WinNTRequired: Feature requires Windows NT.
WrappedExceptionSource: Wrapped Exception from System.Configuration.Install.Installer
InvalidProperty: Invalid value {1} for property {0}
CantAddSelf: An installer cannot be added to its own collection.
```

--------------------------------

### Non-Transacted Installation Phase Messages

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Messages indicating the execution phases (Install, Commit, Rollback, Uninstall) for non-transacted installations, providing insight into the installer's current operation.

```APIDOC
InstallRollbackNtRun: Running Rollback phase of non-transacted install.
InstallCommitNtRun: Running Commit phase of non-transacted install.
InstallUninstallNtRun: Running Uninstall phase of non-transacted install
InstallInstallNtRun: Running Install phase of non-transacted install
```

--------------------------------

### System.Diagnostics.EventLogInstaller Class Reference

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Messages and property descriptions for the `EventLogInstaller` class, which facilitates the installation and configuration of event log sources.

```APIDOC
Messages:
  NotAnEventLog: EventLogInstaller cannot copy properties from components that are not EventLogs.
  CreatingEventLog: Creating EventLog source {0} in log {1}...
  RestoringEventLog: Restoring event log to previous state for source {0}.
  RemovingEventLog: Removing EventLog source {0}.
  DeletingEventLog: Deleting event log {0}.
  LocalSourceNotRegisteredWarning: Warning: The source {0} is not registered on the local machine.

Properties:
  Desc_CategoryResourceFile: The path to the dll containing category names.
  Desc_CategoryCount: The number of categories contained in the CategoryResourceFile.
  Desc_Log: The name of the log to read from and write to.
  Desc_MessageResourceFile: The path to the resource dll containing event messages.
  Desc_ParameterResourceFile: The path to the dll containing the parameter replacement strings.
  Desc_Source: The application name (source name) to use when writing to the event log.
  Desc_UninstallAction: The action to take on the Log on uninstall.
```

--------------------------------

### System.Configuration.Install.AssemblyInstaller Class Properties

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Descriptions for properties specific to the `AssemblyInstaller` class, used for installing assemblies and managing their installation context.

```APIDOC
Desc_AssemblyInstaller_Assembly: The assembly to install
Desc_AssemblyInstaller_CommandLine: The command line to use when creating a new InstallContext object for the assembly's installation
Desc_AssemblyInstaller_Path: The path of the assembly to install
Desc_AssemblyInstaller_UseNewContext: Value indicating whether to create a new InstallContext object for the assembly's installation
```

--------------------------------

### InstallUtil Command-Line Usage and Options

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Detailed help message for the `InstallUtil` command-line utility, explaining its syntax, installation/uninstallation modes, transaction behavior, and how options are applied to assemblies.

```APIDOC
Usage: InstallUtil [/u | /uninstall] [option [...]] assembly [[option [...]] assembly] [...]]\r\n\r\nInstallUtil executes the installers in each given assembly.\r\nIf the /u or /uninstall switch is specified, it uninstalls\r\nthe assemblies, otherwise it installs them. Unlike other\r\noptions, /u applies to all assemblies, regardless of where it\r\nappears on the command line.\r\n\r\nInstallation is done in a transactioned way: If one of the\r\nassemblies fails to install, the installations of all other\r\nassemblies are rolled back. Uninstall is not transactioned.\r\n\r\nOptions take the form /switch=[value]. Any option that occurs\r\nbefore the name of an assembly will apply to that assembly's\r\ninstallation. Options are cumulative but overridable - options\r\nspecified for one assembly will apply to the next as well unless\r\nthe option is specified with a new value. The default for all\r\noptions is empty or false unless otherwise specified.\r\n\r\nOptions recognized:\r\n\r\nIndividual installers used within an assembly may recognize other\r\noptions. To learn about these options, run InstallUtil with the paths\r\nof the assemblies on the command line along with the /? or /help option.
```

--------------------------------

### System.Diagnostics.PerformanceCounterInstaller Class Reference

Source: https://github.com/microsoft/referencesource/blob/master/System.Configuration.Install/System.Configuration.Install.txt

Messages and property descriptions for the `PerformanceCounterInstaller` class, used for installing and managing performance counter categories and their associated counters.

```APIDOC
Messages:
  NotAPerformanceCounter: PerformanceCounterInstaller can only be used to install objects of type PerformanceCounter.
  NewCategory: PerformanceCounterInstaller can only install multiple counters in the same category. To install this counter, create a new instance of PerformanceCounterInstaller.
  RestoringPerformanceCounter: Restoring performance counter data to previous state for performance counter category {0}.
  CreatingPerformanceCounter: Creating performance counter category {0}.
  RemovingPerformanceCounter: Removing performance counter category {0}.

Properties:
  PCCategoryName: Category name of the performance counter object.
  PCCounterName: Counter name of the performance counter object.
  PCInstanceName: Instance name of the performance counter object.
  PCMachineName: Specifies the machine from where to read the performance data.
```

--------------------------------

### Process Properties Reference

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Properties providing details about a running process, including memory usage, CPU time, priority, and various configuration options for starting and managing processes.

```APIDOC
ProcessMinWorkingSet: The minimum amount of physical memory the process has required since it was started.
ProcessNonpagedSystemMemorySize: The number of bytes of non pageable system  memory the process is using.
ProcessPagedMemorySize: The current amount of memory that can be paged to disk that the process is using.
ProcessPagedSystemMemorySize: The number of bytes of pageable system memory the process is using.
ProcessPeakPagedMemorySize: The maximum amount of memory that can be paged to disk that the process has used since it was started.
ProcessPeakWorkingSet: The maximum amount of physical memory the process has used since it was started.
ProcessPeakVirtualMemorySize: The maximum amount of virtual memory the process has allocated since it was started.
ProcessPriorityBoostEnabled: Whether this process would like a priority boost when the user interacts with it.
ProcessPriorityClass: The priority that the threads in the process run relative to.
ProcessPrivateMemorySize: The current amount of memory that the process has allocated that cannot be shared with other processes.
ProcessPrivilegedProcessorTime: The amount of CPU time the process spent inside the operating system core.
ProcessProcessName: The name of the process.
ProcessProcessorAffinity: A bit mask which represents the processors that the threads within the process are allowed to run on.
ProcessResponding: Whether this process is currently responding.
ProcessStandardError: Standard error stream of the process.
ProcessStandardInput: Standard input stream of the process.
ProcessStandardOutput: Standard output stream of the process.
ProcessStartInfo: Specifies information used to start a process.
ProcessStartTime: The time at which the process was started.
ProcessTotalProcessorTime: The amount of CPU time the process has used.
ProcessUserProcessorTime: The amount of CPU time the process spent outside the operating system core.
ProcessVirtualMemorySize: The amount of virtual memory the process has currently allocated.
ProcessWorkingSet: The current amount of physical memory the process is using.
ProcessVerb: The verb to apply to the document specified by the FileName property.
ProcessArguments: Command line arguments that will be passed to the application specified by the FileName property.
ProcessErrorDialog: Whether to show an error dialog to the user if there is an error.
ProcessWindowStyle: How the main window should be created when the process starts.
ProcessCreateNoWindow: Whether to start the process without creating a new window to contain it.
ProcessEnvironmentVariables: Set of environment variables that apply to this process and child processes.
ProcessRedirectStandardInput: Whether the process command input is read from the Process instance's StandardInput member.
ProcessRedirectStandardOutput: Whether the process output is written to the Process instance's StandardOutput member.
ProcessRedirectStandardError: Whether the process's error output is written to the Process instance's StandardError member.
ProcessUseShellExecute: Whether to use the operating system shell to start the process.
```

--------------------------------

### Process Component Properties and Events

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Documents properties and events for managing local and remote processes, including starting, stopping, monitoring exit status, and accessing process details like modules, threads, and memory usage.

```APIDOC
ProcessAssociated: Indicates if the process component is associated with a real process.
ProcessDesc: Provides access to local and remote processes, enabling starting and stopping of local processes.
ProcessExitCode: The value returned from the associated process when it terminated.
ProcessTerminated: Indicates if the associated process has been terminated.
ProcessExitTime: The time that the associated process exited.
ProcessHandle: Returns the native handle for this process. The handle is only available if the process was started using this component.
ProcessHandleCount: The number of native handles associated with this process.
ProcessId: The unique identifier for the process.
ProcessMachineName: The name of the machine the running the process.
ProcessMainModule: The main module for the associated process.
ProcessModules: The modules that have been loaded by the associated process.
ProcessSynchronizingObject: The object used to marshal the event handler calls issued as a result of a Process exit.
ProcessSessionId: The identifier for the session of the process.
ProcessThreads: The threads running in the associated process.
ProcessEnableRaisingEvents: Whether the process component should watch for the associated process to exit, and raise the Exited event.
ProcessExited: If the WatchForExit property is set to true, then this event is raised when the associated process exits.
ProcessFileName: The name of the application, document or URL to start.
ProcessWorkingDirectory: The initial working directory for the process.
ProcessBasePriority: The base priority computed based on the priority class that all threads run relative to.
ProcessMainWindowHandle: The handle of the main window for the process.
ProcessMainWindowTitle: The caption of the main window for the process.
ProcessMaxWorkingSet: The maximum amount of physical memory the process has required since it was started.
```

--------------------------------

### Thread Properties Reference

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Properties providing details about an individual thread's state, priority, CPU time, and start information.

```APIDOC
ThreadBasePriority: The current base priority of the thread.
ThreadCurrentPriority: The current priority level of the thread.
ThreadId: The unique identifier for the thread.
ThreadPriorityBoostEnabled: Whether the thread would like a priority boost when the user interacts with UI associated with the thread.
ThreadPriorityLevel: The priority level of the thread.
ThreadPrivilegedProcessorTime: The amount of CPU time the thread spent inside the operating system core.
ThreadStartAddress: The memory address of the function that was run when the thread started.
ThreadStartTime: The time the thread was started.
ThreadThreadState: The execution state of the thread.
ThreadTotalProcessorTime: The amount of CPU time the thread has consumed since it was started.
ThreadUserProcessorTime: The amount of CPU time the thread spent outside the operating system core.
ThreadWaitReason: The reason the thread is waiting, if it is waiting.
```

--------------------------------

### MSMQ Error Code C00E0044

Source: https://github.com/microsoft/referencesource/blob/master/System.Messaging/System.Messaging.txt

Object owner was invalid. For example, MQCreateQueue failed because the Queue Manager object is invalid.

--------------------------------

### MSMQ Error Code C00E0020

Source: https://github.com/microsoft/referencesource/blob/master/System.Messaging/System.Messaging.txt

The specified format name does not support the requested operation. For example, a direct queue format name cannot be deleted.

```APIDOC
C00E0020=The specified format name does not support the requested operation. For example, a direct queue format name cannot be deleted.
```

--------------------------------

### XSD.exe Command-Line Options Reference

Source: https://github.com/microsoft/referencesource/blob/master/xsd/XsdRes.txt

Detailed reference for all available command-line options of the xsd.exe utility. Each option's purpose, short form, and expected arguments are described, covering aspects like code generation, output format, and language selection.

```APIDOC
OPTIONS:
- /classes (or /c): Generate classes for this schema.
- /dataset (or /d): Generate sub-classed DataSet for this schema.
- /element:<element> (or /e:<element>): Element from schema to process.
- /fields (or /f): Generate fields instead of properties.
- /order (or /o): Generate explicit order identifiers on all particle members.
- /enableDataBinding (or /edb): Implement INotifyPropertyChanged interface on all generated types to enable data binding.
- /enableLinqDataSet (or /eld): Generate LINQ-enabled sub-classed Dataset for the schemas provided.
- /language:<language> (or /l:<language>): The language to use for the generated code.
  - Supported values: 'CS' (CSharp), 'VB', 'JS', 'VJS', 'CPP'
  - Custom: Fully-qualified name for a class implementing System.CodeDom.Compiler.CodeDomProvider.
  - Default: 'CS'
- /namespace:<namespace> (or /n:<namespace>): The namespace for generated class files.
  - Default: Global namespace.
- /nologo: Suppresses the banner.
- /outputdir:<directoryName> (or /o:<directoryName>): The output directory to create files in.
  - Default: Current directory.
- /type:<type> (or /t:<type>): Type from assembly to generate schema for. Multiple types may be provided.
  - If no types are provided, then schemas for all types in an assembly are generated.
- /uri:<uri> (or /u:<uri>): Uri of elements from schema to process.

ADVANCED OPTIONS:
- /parameters:<file> (or /p:<file>): Read command-line options from the specified XML file.
```

--------------------------------

### Manual Steps for Rebuilding .NET Regex IL File

Source: https://github.com/microsoft/referencesource/blob/master/regexes/readme.txt

Detailed step-by-step instructions for developers to manually rebuild the System.Web.RegularExpressions.ilpp file after making changes to RegexPrecompiler.cs, involving specific build environments and tools like tf edit and RebuildRegExILFile.cmd.

```cmd
1. Make your changes to ndp\fx\src\xsp\regcomp\RegexPrecompiler.cs
2. Build from ndp\fx\src\xsp\regcomp from a razzle window
3. Open regexes\System.Web.RegularExpressions.ilpp for editing (using "tf edit")
4. Open a suite window
5. Go to ndp\fx\src\xsp\regexes
6. Run the batch file RebuildRegExILFile.cmd
7. Build -c from ndp\fx\src\xsp\regexes in a RAZZLE window to build System.Web.RegularExpressions.dll
8. Check in the modified System.Web.RegularExpressions.ilpp
```

--------------------------------

### Configuring RegexPreCompiler Runtime Version for .NET

Source: https://github.com/microsoft/referencesource/blob/master/regexes/readme.txt

Provides three methods to ensure RegexPreCompiler.exe uses the correct runtime version when the public runtime on the machine is outdated, including using a configuration file, setting environment variables, or executing from a ClrEnv window.

```xml
<configuration>
  <startup>
    <supportedRuntime version="v4.0.amd64chk" />
  </startup>
</configuration>
```

```cmd
set COMPLUS_DEFAULTVERSION=v4.0.amd64chk
set COMPLUS_VERSION=v4.0.amd64chk
# ... run RegexPreCompiler ...
set COMPLUS_DEFAULTVERSION=
set COMPLUS_VERSION=
```

```cmd
# Alternative: Run RebuildRegExILFile.cmd from a ClrEnv window.
# This environment is pre-configured with correct settings.
```

--------------------------------

### DesignTime Initialization Support Description

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Provides a description for the ISupportInitialize interface, which enables objects to support transacted initialization.

```APIDOC
ISupportInitializeDescr=Specifies support for transacted initialization.
```

--------------------------------

### XSD.exe Command-Line Arguments Description

Source: https://github.com/microsoft/referencesource/blob/master/xsd/XsdRes.txt

Describes the various types of input files that can be provided as arguments to the xsd.exe utility. This includes schema files, assembly files, XML instance files, and XDR schema files, highlighting their respective purposes.

```APIDOC
ARGUMENTS:
- <schema>.xsd: Name of a schema containing elements to import.
- <assembly>.dll|exe: Name of an assembly containing types to generate schema for.
- <instance>.xml: Name of an XML file to infer XSD schema from.
- <schema>.xdr: Name of an XDR schema to convert to XSD.

Note: Multiple file arguments of the same type may be provided.
```

--------------------------------

### XSD.exe Utility Description and Basic Usage

Source: https://github.com/microsoft/referencesource/blob/master/xsd/XsdRes.txt

Provides an overview of the xsd.exe utility, its purpose, and the general syntax for invoking it. It outlines the different modes of operation, including generating schemas from assemblies, classes from schemas, or inferring schemas from XML instances.

```APIDOC
Utility Name: Microsoft (R) Xml Schemas/DataTypes support utility
Description: Utility to generate schema or class files from given source.

Usage Patterns:
1. Generate classes/dataset from schema:
   xsd <schema>.xsd /classes|dataset [/e:] [/l:] [/n:] [/o:] [/s] [/uri:]
2. Generate schema from assembly:
   xsd <assembly>.dll|.exe [/outputdir:] [/type: [...]]
3. Infer schema from XML instance:
   xsd <instance>.xml [/outputdir:]
4. Convert XDR to XSD:
   xsd <schema>.xdr [/outputdir:]

More Help: Type "xsd {0}"
```

--------------------------------

### AdRotator Control Properties and Events

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Documentation for properties and events of the AdRotator control, including file paths, key names for image and navigation URLs, keyword filtering, and the AdCreated event.

```APIDOC
AdRotator_AdvertisementFile=XML file that contains advertisements.
AdRotator_ImageKey=XML element name that specifies which image URL to retrieve.
AdRotator_NavigateUrlKey=XML element name that specifies which advertisement Web page URL to retrieve.
AdRotator_KeywordFilter=Keyword for limiting selection of advertisements.
AdRotator_AdCreated=Raises an event after an advertisement is retrieved from the AdvertisementFile.
```

--------------------------------

### Define Runtime Configuration and Debug Assertion Strings (Resource File)

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

This snippet defines various runtime configuration settings and messages used for debug assertions within the .NET Framework. It includes platform-specific messages for Unix and non-Unix systems, and different assertion titles for Silverlight and non-Silverlight environments.

```Resource File
; NOTE: do not use \", use ' instead
; NOTE: Use # or ; for comments

#if INCLUDE_RUNTIME
RTL=RTL_False
ContinueButtonText=Continue
DebugAssertBanner=---- DEBUG ASSERTION FAILED ----
DebugAssertShortMessage=---- Assert Short Message ----
DebugAssertLongMessage=---- Assert Long Message ----
#if PLATFORM_UNIX
DebugMessageTruncated={0}...\n<truncated>
#endif
#if !PLATFORM_UNIX
DebugMessageTruncated={0}...\r\n<truncated>
#endif // PLATFORM_UNIX else

#if SILVERLIGHT
DebugAssertTitleShort=Assertion Failed
DebugAssertTitle=Assertion Failed: Cancel=Debug, OK=Continue
#endif // SILVERLIGHT
#if !SILVERLIGHT
DebugAssertTitle=Assertion Failed: Abort=Quit, Retry=Debug, Ignore=Continue
#endif

#endif // INCLUDE_RUNTIME
```

--------------------------------

### System.Data.Entity.Design.PluralizationServices Documentation

Source: https://github.com/microsoft/referencesource/blob/master/System.Data.Entity.Design/System.Data.Entity.Design.txt

Documentation for the PluralizationServices, highlighting issues with duplicate entries in user dictionaries and limitations regarding supported locales for pluralization.

```APIDOC
System.Data.Entity.Design.PluralizationServices:
  DuplicateEntryInUserDictionary: The {0} value '{1}' already exists in the user-defined dictionary.
  UnsupportedLocaleForPluralizationServices: The culture '{0}' is not supported.   Pluralization is currently only supported for the English language.
```

--------------------------------

### General Configuration Messages

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Messages related to general configuration parsing and validation.

```APIDOC
BadConfigSwitchValue=The config value for Switch '{0}' was invalid.
```

```APIDOC
ConfigSectionsUnique=The '{0}' section can only appear once per config file.
```

```APIDOC
ConfigSectionsUniquePerSection=The '{0}' tag can only appear once per section.
```

--------------------------------

### Default Property Category Names for UI Components

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

A list of standard category names used to group properties in UI components, such as property grids, enhancing organization and discoverability.

```APIDOC
PropertyCategoryAction: Action
PropertyCategoryAppearance: Appearance
PropertyCategoryAsynchronous: Asynchronous
PropertyCategoryBehavior: Behavior
PropertyCategoryData: Data
PropertyCategoryDDE: DDE
PropertyCategoryDesign: Design
PropertyCategoryDragDrop: Drag Drop
PropertyCategoryFocus: Focus
PropertyCategoryFont: Font
PropertyCategoryFormat: Format
PropertyCategoryKey: Key
PropertyCategoryList: List
PropertyCategoryLayout: Layout
PropertyCategoryDefault: Misc
PropertyCategoryMouse: Mouse
PropertyCategoryPosition: Position
PropertyCategoryText: Text
PropertyCategoryScale: Scale
PropertyCategoryWindowStyle: Window Style
PropertyCategoryConfig: Configurations
```

--------------------------------

### System.IO.FileSystemWatcher Description Attributes

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Provides descriptions for properties and events of the `System.IO.FileSystemWatcher` component, detailing their purpose and behavior for monitoring file system changes.

```APIDOC
FSW_ChangedFilter=Flag to indicate which change event to monitor.
FSW_Enabled=Flag to indicate whether this component is active or not.
FSW_Filter=The file pattern filter.
FSW_IncludeSubdirectories=Flag to watch subdirectories.
FSW_Path=The path to the directory to monitor.
FSW_SynchronizingObject=The object used to marshal the event handler calls issued as a result of a Directory change.
FSW_Changed=Occurs when a file and/or directory change matches the filter.
FSW_Created=Occurs when a file and/or directory creation matches the filter.
FSW_Deleted=Occurs when a file and/or directory deletion matches the filter.
FSW_Renamed=Occurs when a file and/or directory rename matches the filter.
FSW_BufferOverflow=Too many changes at once in directory:{0}.
FileSystemWatcherDesc=Monitors file system change notifications and raises events when a directory or file changes.
```

--------------------------------

### Runtime Categories and Constants

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Defines various categories for actions, appearance, behavior, data, navigation, paging, and style, along with a 'Not Implemented' constant and RTL setting.

```APIDOC
RTL=RTL_False
Category_Action=Action
Category_Appearance=Appearance
Category_Behavior=Behavior
Category_Data=Data
Category_Navigation=Navigation
Category_Paging=Paging
Category_Style=Style
MSHTMLHost_Not_Implemented=Not Implemented
```

--------------------------------

### API Properties for ObjectList

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties for configuring an ObjectList control, including data source binding, field representation, command handling, and event management.

```APIDOC
ObjectList:
  DataSource: Data source that populates items in the list.
  LabelField: Field in the data source to use for a compact representation of the items in list view.
  TableFields: Fields in the data source to use for an expanded representation of the items in list view.
  AutoGenerateFields: Whether the fields are generated automatically at run time based on the associated data source.
  Fields: Collection of fields representing the items in details view.
  Commands: Collection of commands for each item in the list.
  OnItemCommand: Raises an event when the user selects a command associated with the item.
  OnItemSelect: Raises an event when the user selects an item in the list view.
  OnItemDataBind: Raises an event after an item is bound to a data source.
  OnShowItemCommands: Raises an event before showing the set of commands for an item.
  DefaultCommand: Command raised when an item is selected in list view.
  DetailsCommandText: Text for the link to details view.
  BackCommandText: Text for back link in details view.
  MoreText: Text for the link to more details and commands.
  CommandStyle: The style applied to the commands in the list.
  LabelStyle: The style applied to the header label.
```

--------------------------------

### Process Module Properties Reference

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Properties describing a module loaded by a process, such as its name, file path, base address, and memory size.

```APIDOC
ProcModModuleName: The name of the module.
ProcModFileName: The file name of the module.
ProcModBaseAddress: The memory address that the module loaded at.
ProcModModuleMemorySize: The amount of virtual memory required by the code and data in the module file.
ProcModEntryPointAddress: The memory address of the function that runs when the module is loaded.
```

--------------------------------

### Define General Debug and Not Supported Messages (Resource File)

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

This section defines common error messages related to unsupported operations, debugger launch failures, object disposal, trace output exceptions, and listener collection constraints. These strings are typically used in debug builds or for general error handling.

```Resource File
#if INCLUDE_DEBUG

#=------------------------------------------------------------------=
# Strings used by the debug class
#=------------------------------------------------------------------=

NotSupported=This operation is not supported.

#if !SILVERLIGHT
DebugLaunchFailed=Cannot launch the debugger.  Make sure that a Microsoft (R) .NET Framework debugger is properly installed.
DebugLaunchFailedTitle=Microsoft .NET Framework Debug Launch Failure
#endif

ObjectDisposed=Object {0} has been disposed and can no longer be used.
ExceptionOccurred=An exception occurred writing trace output to log file '{0}'. {1}
MustAddListener=Only TraceListeners can be added to a TraceListenerCollection.

ToStringNull=(null)
```

--------------------------------

### Image Control Properties

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties for the Image control, including alternate text, auto-formatting, screen coverage, image URL, navigation URL, and softkey label.

```APIDOC
Image_AlternateText=The alternate text displayed when the image cannot be rendered.
Image_AutoFormat=Whether the source image should be auto-formatted to match device capabilities.
Image_Coverage=Percentage of the screen area the image should use.
Image_ImageUrl=The URL of the image to be rendered.
Image_NavigateUrl=The URL or Form to navigate to.
Image_SoftkeyLabel=Label used for the image when rendered on a softkey. Only applies to devices that support softkeys.
```

--------------------------------

### System.Timers.Timer Description Attributes

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Provides descriptions for properties and events of the `System.Timers.Timer` component, outlining their function and usage for interval-based event triggering.

```APIDOC
NotSet=[Not Set]
TimerAutoReset=Indicates whether the timer will be restarted when it is enabled.
TimerEnabled=Indicates whether the timer is enabled to fire events at a defined interval.
TimerInterval=The number of milliseconds between timer events.
TimerIntervalElapsed=Occurs when the Interval has elapsed.
TimerSynchronizingObject=The object used to marshal the event handler calls issued when an interval has elapsed.
```

--------------------------------

### API Properties for Style

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties for defining visual styles, including alignment, colors, font, name, inheritance, and text wrapping behavior.

```APIDOC
Style:
  Alignment: Horizontal alignment of the control.
  BackColor: Background color of the control.
  Font: Font for text within the control.
  ForeColor: Color of the text within the control.
  Name: Name of the style.
  Reference: Reference to another style to inherit from.
  Wrapping: Wrapping behavior of text in the control.
```

--------------------------------

### StyleSheet Configuration and Property Errors

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Error messages for StyleSheet components, covering duplicate style elements, missing 'Name' attributes, external file validation, and issues with inaccessible, non-settable, or mismatched style properties.

```APIDOC
StyleSheet_DuplicateName: Duplicate Style elements named {0} found within a style sheet.
StyleSheet_MustContainID: Style elements must contain a 'Name' attribute.
StyleSheet_NoStyleSheetInExternalFile: External file does not contain a style sheet control.
StyleSheet_PropertyNotAccessible: The following style sheet property is not accessible: '{0}'
StyleSheet_PropertyNotSettable: The following style sheet property is not settable: '{0}'
StyleSheet_InvalidStyleName: Attempting to set Style named '{0}' into style sheet key '{1}'.  These values must match.
```

--------------------------------

### EntityStoreGeneratorSchemaNotLoaded Error

Source: https://github.com/microsoft/referencesource/blob/master/System.Data.Entity.Design/System.Data.Entity.Design.txt

This error indicates that the store metadata has not been generated yet. The 'GenerateStoreMetadata' method must be called first before attempting to access or use the store schema.

```Resource File
EntityStoreGeneratorSchemaNotLoaded=The store metadata has not been generated yet. Call GenerateStoreMetadata first.
```

--------------------------------

### Common String Constants

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Common string constants used in the application, such as default verb names.

```APIDOC
VerbEditorDefault: (Default)
```

--------------------------------

### Serial Port Property Descriptions

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Documents the key configurable properties of the SerialPort class, such as baud rate, data bits, flow control, and timeouts, explaining their purpose and impact on serial communication.

```APIDOC
BaudRate=The baud rate to use on this serial port.
DataBits=The number of data bits per transmitted/received byte.
DiscardNull=Whether to discard null bytes received on the port before adding to serial buffer.
DtrEnable=Whether to enable the Data Terminal Ready (DTR) line during communications.
Encoding=The encoding to use when reading and writing strings.
Handshake=The handshaking protocol for flow control in data exchange, which can be None.
NewLine=The string used by ReadLine and WriteLine to denote a new line.
Parity=The scheme for parity checking each received byte and marking each transmitted byte.
ParityReplace=Byte with which to replace bytes received with parity errors.
PortName=The name of the communications port to open.
ReadBufferSize=The size of the read buffer in bytes.  This is the maximum number of read bytes which can be buffered.
ReadTimeout=The read timeout in Milliseconds.
```

--------------------------------

### System.CommandLine Parameter Binding Exception Messages

Source: https://github.com/microsoft/referencesource/blob/master/System.Core/System.Core.txt

Defines resource strings for ParameterBindingException errors within the System.CommandLine component, addressing issues such as ambiguous parameter names, parameters specified multiple times, and unknown parameters.

```Resource File
ParameterBindingException_AmbiguousParameterName=Prefix {0} resolves to multiple parameters: {1}. Use a more specific prefix for this parameter. 
ParameterBindingException_ParameterValueAlreadySpecified=Parameter {0} already given value of {1}.
ParameterBindingException_UnknownParameteName=Unknown parameter {0}.
```

--------------------------------

### Link Control Properties

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties for the Link control, including the navigation URL and softkey label.

```APIDOC
Link_NavigateUrl=The URL or Form to link to.
Link_SoftkeyLabel=Label used for the link when rendered on a softkey. Only used on devices that support softkeys.
```

--------------------------------

### PartialMethodToDelegate Error

Source: https://github.com/microsoft/referencesource/blob/master/Microsoft.CSharp/Microsoft/CSharp/ManagedBinder/Errors/Microsoft.CSharp.RuntimeBinder.Errors.txt

Reports that a delegate cannot be created from partial method '{0}' because it lacks an implementing declaration, making it incomplete.

```APIDOC
Error Code: PartialMethodToDelegate
Description: Cannot create delegate from method '{0}' because it is a partial method without an implementing declaration
```

--------------------------------

### EventLog Component Properties and Events

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Provides documentation for properties and events related to interacting with Windows event logs, including reading, writing, monitoring, and accessing individual log entry details.

```APIDOC
EventLogDesc: Provides interaction with Windows event logs.
ErrorDataReceived: User event handler to call for async IO with StandardError stream.
LogEntries: The contents of the log.
LogLog: Gets or sets the name of the log to read from and write to.
LogMachineName: The name of the machine on which to read or write events.
LogMonitoring: Indicates if the component monitors the event log for changes.
LogSynchronizingObject: The object used to marshal the event handler calls issued as a result of an EventLog change.
LogSource: The application name (source name) to use when writing to the event log.
LogEntryWritten: Raised each time any application writes an entry to the event log.
LogEntryMachineName: The machine on which this event log resides.
LogEntryData: The binary data associated with this entry in the event log.
LogEntryIndex: The sequence of this entry in the event log.
LogEntryCategory: The category for this message.
LogEntryCategoryNumber: An application-specific category number assigned to this entry.
LogEntryEventID: The number identifying the message for this source.
LogEntryEntryType: The type of entry - Information, Warning, etc.
LogEntryMessage: The text of the message for this entry
LogEntrySource: The name of the application that wrote this entry.
LogEntryReplacementStrings: The application-supplied strings used in the message.
LogEntryResourceId: The full number identifying the message in the event message dll.
LogEntryTimeGenerated: The time at which the application logged this entry.
LogEntryTimeWritten: The time at which the system logged this entry to the event log.
LogEntryUserName: The username of the account associated with this entry by the writing application.
OutputDataReceived: User event handler to call for async IO with StandardOutput stream.
```

--------------------------------

### Command Control Properties and Events

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties and events for the Command control, such as command argument, command name, validation invocation, OnClick and OnItemCommand events, softkey label, and visual format.

```APIDOC
Command_CommandArgument=The argument associated with the command.
Command_CommandName=The name associated with the command.
Command_CausesValidation=Whether to invoke validation on the form when activated.
Command_OnClick=Raises an event when the user activates the command.
Command_OnItemCommand=Raises an event when the user activates the command. The event is bubbled up to parent controls.
Command_SoftkeyLabel=Label used for the command when rendered on a softkey. Only applies to devices that support softkeys.
Command_Format=The visual appearance of the control.
```

--------------------------------

### General Control Properties

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

General properties applicable to controls, such as the AccessKey used for focus on i-mode phones.

```APIDOC
Control_AccessKey=The access key used to give focus to the control on i-mode phones, using the directkey function.
```

--------------------------------

### AppSettingsReader Exception Messages

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Error messages related to the AppSettingsReader, indicating issues like missing keys, invalid parsers, or malformed values in configuration.

```APIDOC
AppSettingsReaderNoKey: The key '{0}' does not exist in the appSettings configuration section.
AppSettingsReaderNoParser: Type '{0}' does not have a Parse method.
AppSettingsReaderCantParse: The value '{0}' was found in the appSettings configuration section for key '{1}', and this value is not a valid {2}.
AppSettingsReaderEmptyString: (empty string)
```

--------------------------------

### System.Data.Entity.Design.MetadataItemCollectionFactory Documentation

Source: https://github.com/microsoft/referencesource/blob/master/System.Data.Entity.Design/System.Data.Entity.Design.txt

Documentation for the MetadataItemCollectionFactory, specifically addressing schema version compatibility requirements for the target Entity Framework version.

```APIDOC
System.Data.Entity.Design.MetadataItemCollectionFactory:
  TargetVersionSchemaVersionMismatch: The target Entity Framework version requires the edmx schema version {0} or lower. The specified schema is version {1}.
```

--------------------------------

### NoSuchMemberOrExtension Error

Source: https://github.com/microsoft/referencesource/blob/master/Microsoft.CSharp/Microsoft/CSharp/ManagedBinder/Errors/Microsoft.CSharp.RuntimeBinder.Errors.txt

Reports that type '{0}' does not contain a definition for '{1}', and no applicable extension method '{1}' could be found (suggesting a missing using directive or assembly reference).

```APIDOC
Error Code: NoSuchMemberOrExtension
Description: '{0}' does not contain a definition for '{1}' and no extension method '{1}' accepting a first argument of type '{0}' could be found (are you missing a using directive or an assembly reference?)
```

--------------------------------

### System.CommandLine General Resource Strings

Source: https://github.com/microsoft/referencesource/blob/master/System.Core/System.Core.txt

Defines general resource strings for the System.CommandLine component, including common labels like 'Aliases', 'Error' message prefixes, and 'Usage' help message prefixes.

```Resource File
CommandLineParser_Aliases=Aliases
CommandLineParser_ErrorMessagePrefix=Error
CommandLineParser_HelpMessagePrefix=Usage
```

--------------------------------

### System.IO.FileSystemWatcher Exception Messages

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Defines common exception messages related to file system operations within the `System.IO.FileSystemWatcher` component, providing context for various error scenarios.

```APIDOC
InvalidDirName=The directory name {0} is invalid.
FSW_IOError=Error reading the {0} directory.
PatternInvalidChar=The character '{0}' in the pattern provided is not valid.
BufferSizeTooLarge=The specified buffer size is too large. FileSystemWatcher cannot allocate {0} bytes for the internal buffer.
```

--------------------------------

### Proxy and JScript Configuration Errors

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

This section covers error messages related to issues encountered during the initialization of proxy JScript files or invalid proxy settings, such as incorrect time or URL formats.

```Error Message
net_jscript_load=The proxy JScript file threw an exception while being initialized: {0}.
```

```Error Message
net_proxy_not_gmt=The specified value is not a valid GMT time.
```

```Error Message
net_proxy_invalid_dayofweek=The specified value is not a valid day of the week.
```

```Error Message
net_proxy_invalid_url_format=The system proxy settings contain an invalid proxy server setting: '{0}'.
```

--------------------------------

### XmlSerializer Temporary Directory Access Denied

Source: https://github.com/microsoft/referencesource/blob/master/System.Xml/System.Xml.txt

Reports a permission issue where the XmlSerializer cannot access the temporary directory required for dynamic assembly compilation. This prevents serialization and suggests checking process permissions or using `Path.GetTempPath()` to find the directory.

```APIDOC
Access to the temp directory is denied. The process under which XmlSerializer is running does not have sufficient permission to access the temp directory. CodeDom will use the user account the process is using to do the compilation, so if the user doesn’t have access to system temp directory, you will not be able to compile. Use Path.GetTempPath() API to find out the temp directory location.
```

--------------------------------

### Mobile Page Configuration and Runtime Errors

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Error messages related to invalid application URLs, missing forms, unfound forms, and session state requirements for mobile pages.

```APIDOC
MobilePage_InvalidApplicationUrl: Invalid application URL - {0}
MobilePage_AtLeastOneFormInPage: Page must contain at least one Form.
MobilePage_FormNotFound: Form not found: '{0}'
MobilePage_RequiresSessionState: The page needs to save viewstate, but session state is disabled or readonly. Enable session state, or disable viewstate for the page.
```

--------------------------------

### Performance Counter Component Properties

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Details properties for defining and interacting with performance counters, including their type, name, help information, and raw value access.

```APIDOC
CounterType: The type of this counter.
CounterName: The name of this counter.
CounterHelp: Help information for this counter.
PC_CounterHelp: The description message for this counter.
PC_CounterType: The counter type indicates how to interpret the value of the counter, for example an actual count or a rate of change.
PC_ReadOnly: Indicates if the counter is read only. Remote counters and counters not created using this component are read-only.
PC_RawValue: Directly accesses the raw value of this counter. The counter must have been created using this component.
```

--------------------------------

### Schema Validation: Any from Any Restriction (NSSubset Rule 3)

Source: https://github.com/microsoft/referencesource/blob/master/System.Xml/System.Xml.txt

This rule states that the derived wildcard's 'processContents' must be identical to or stronger than the base wildcard's 'processContents', where 'strict' is stronger than 'lax' and 'lax' is stronger than 'skip', according to Any:Any -- NSSubset Rule 3.

```APIDOC
Sch_AnyFromAnyRule3: The derived wildcard's 'processContents' must be identical to or stronger than the base wildcard's 'processContents', where 'strict' is stronger than 'lax' and 'lax' is stronger than 'skip', Any:Any -- NSSubset Rule 3.
```

--------------------------------

### Peer Collaboration System Messages and Error Strings

Source: https://github.com/microsoft/referencesource/blob/master/System.Net/System.Net.txt

A comprehensive list of predefined string constants used for error reporting, status updates, and general messaging within a peer collaboration framework. These strings cover various aspects such as initialization failures, contact management issues, event registration problems, and application/object lifecycle events.

```Resource Strings
Collab_StartupFailed=Peer collaboration startup failed.
Collab_CredentialsError=Credentials Error. Cannot open certificate store from credentials.
Collab_PresenceChangedRegFailed=Peer collaboration presence change event register failed.
Collab_GetPresenceChangedDataFailed=Peer collaboration get presence changed event data failed.
Collab_PeerNearMeChangedRegFailed=Peer collaboration peer near me change event register failed.
Collab_GetPeerNearMeChangedDataFailed=Peer collaboration get peer near me changed event data failed.
Collab_ApplicationChangedRegFailed=Peer collaboration application change event register failed.
Collab_GetApplicationChangedDataFailed=Peer collaboration get application event data failed.
Collab_ObjectChangedRegFailed=Peer collaboration object change event register failed.
Collab_GetObjectChangedDataFailed=Peer collaboration get object changed event data failed.
Collab_ReqStatusChangedRegFailed=Peer collaboration request status change event register failed.
Collab_SubListChangedRegFailed=Peer collaboration subscription list change event register failed.
Collab_GetSubListChangedDataFailed=Peer collaboration get subscription list changed event data failed.
Collab_NameChangedRegFailed=Peer collaboration name change event register failed.
Collab_GetNameChangedDataFailed=Peer collaboration get name changed event data failed.
Collab_GetContactsFailed=Peer collaboration get contacts failed.
Collab_ContactNotFound=Contact not found in contact manager.
Collab_ContactExists=Contact already exists in contact manager.
Collab_GetContactFailed=Peer collaboration get contact failed.
Collab_NoEndpointFound=Could not find a PeerEndPoint or Endpoint to use for operation.
Collab_NoEndPointInPeerEndPoint=No EndPoint specified in PeerEndPoint.
Collab_CreateContactFailed=Peer collaboration create contact failed.
Collab_AddContactFailed=Peer collaboration add contact failed.
Collab_AddContactFailedNoXml=Add contact failed. No XML data present. Create this contact again and retry.
Collab_DeleteContactFailed=Peer collaboration delete contact failed.
Collab_NoPeerNameInContact=No PeerName found in PeerContact.
Collab_UpdateContactFailed=Peer collaboration update contact failed.
Collab_SubscribeLocalContactFailed=Cannot set subscribe on local contact. Value is always Allowed.
Collab_DuplicateSubscribeAsync=Another SubscribeAsync operation already in progress.
Collab_DuplicateRefreshAsync=Another RefreshDataAsync operation already in progress.
Collab_UnsubscribeLocalContactFail=Cannot unsubscribe from local contact. It is always subscribed.
Collab_GetPresenceFailed=Peer collaboration get presence information failed.
Collab_GetObjectsFailed=Peer collaboration get objects failed.
Collab_GetAppsFailed=Peer collaboration get application failed.
Collab_InviteFailed=Peer collaboration send invite failed.
Collab_AsyncInviteFailed=Peer collaboration async invite failed.
Collab_AsyncInviteException=Exception occurred while async inviting an endpoint.
Collab_SetLocalPresenceFailed=Peer collaboration LocalPresenceInfo set failed.
Collab_SetLocalEndPointNameFailed=Peer collaboration LocalEndPointName change failed.
Collab_SignInWithNone=Cannot SignIn with None scope.
Collab_SignInFailed=Peer collaboration SignIn failed.
Collab_SignOutFailed=Peer collaboration SignOut failed.
Collab_GetPeersNearMeFailed=Peer collaboration get peers near me failed.
Collab_AppRegNoPathError=Path in PeerApplication is required for registration.
Collab_AppRegFailed=Peer collaboration register application failed.
Collab_AppExists=Application already registered.
Collab_EmptyGuidError=Cannot specify empty Guid.
Collab_AppUnregFailed=Peer collaboration unregister application failed.
Collab_GetLocalAppsFailed=Peer collaboration get local registered applications failed.
Collab_ObjectSetFailed=Peer collaboration set object failed.
Collab_ObjectExists=Object already exists.
Collab_ObjectDeleteFailed=Peer collaboration delete object failed.
Collab_GetLocalObjectsFailed=Peer collaboration get local objects failed.
Collab_PermissionUnionError=Cannot union with non peer collaboration permission objects.
Collab_PermissionIntersectError=Cannot intersect with non peer collaboration permission objects.
Collab_BadPermissionTarget=Target is not a peer collaboration permission.
Collab_ContactToXmlFailed=Peer collaboration contact to xml failed.
Collab_ContactFromXmlFailed=Peer collaboration contact from xml failed.
Collab_NoGuidForCurrApp=No Guid found to send invite for. Current application may not be registered in Collaboration.
Collab_EndPointNotIPv6Error=Peer Collaboration endpoints have to be IPv6.
Collab_AddToContactMgrFailed=Add to Contact Manager failed.
Collab_AddToContactMgrFailedUpdate=Base contact from peer added but display name, nick name and email address not updated.
Collab_EndPointNotAPeerNearMe=Given Endpoint is not an endpoint of any PeerNearMe.
```

--------------------------------

### API Properties for PagedControl

Source: https://github.com/microsoft/referencesource/blob/master/System.Web.Mobile/System.Web.Mobile.txt

Properties for managing pagination behavior in controls, including item counts per page and custom paging events.

```APIDOC
PagedControl:
  ItemCount: Number of items to render in the control. The value '0' indicates automatic pagination.
  ItemsPerPage: Number of items to render in each page of the control. The value '0' indicates default pagination.
  OnLoadItems: Raises an event when the control uses custom paging and requests more data.
```

--------------------------------

### SerialPort Component Properties and Events

Source: https://github.com/microsoft/referencesource/blob/master/System/System.txt

Documents the properties and events associated with the `SerialPort` component, enabling control over serial communication, buffer management, and event handling for data and error reception.

```APIDOC
ReceivedBytesThreshold: Number of bytes required to be available before the Read event is fired.
RtsEnable: Whether to enable the Request To Send (RTS) line during communications.
SerialPortDesc: Represents a serial port resource.
StopBits: The number of stop bits per transmitted/received byte.
WriteBufferSize: The size of the write buffer in bytes. This is the maximum number of bytes which can be queued for write.
WriteTimeout: The write timeout in milliseconds.
SerialErrorReceived: Raised each time when an error is received from the SerialPort.
SerialPinChanged: Raised each time when pin is changed on the SerialPort.
SerialDataReceived: Raised each time when data is received from the SerialPort.
```