diff --git a/xml/Microsoft.VisualBasic.ApplicationServices/AssemblyInfo.xml b/xml/Microsoft.VisualBasic.ApplicationServices/AssemblyInfo.xml index 594e550e9b1..2c9d1cb83d6 100644 --- a/xml/Microsoft.VisualBasic.ApplicationServices/AssemblyInfo.xml +++ b/xml/Microsoft.VisualBasic.ApplicationServices/AssemblyInfo.xml @@ -841,7 +841,6 @@ The application does not have sufficient permissions to access the assembly version. - Objects (Visual Basic) diff --git a/xml/Microsoft.VisualBasic.ApplicationServices/User.xml b/xml/Microsoft.VisualBasic.ApplicationServices/User.xml index 5688a505fbd..c881c458ba3 100644 --- a/xml/Microsoft.VisualBasic.ApplicationServices/User.xml +++ b/xml/Microsoft.VisualBasic.ApplicationServices/User.xml @@ -38,7 +38,7 @@ The `My.User` property also provides access to the for the current user. A principal object represents the user's security context, including that user's identity and any roles to which the user belongs. - For Windows applications, this property provides the same functionality as the property. For Web applications, this property provides the same functionality as the property of the object returned by the property. + For Windows applications, this property provides the same functionality as the property. > [!NOTE] > For Windows applications, only projects built on the **Windows Application** template initialize the `My.User` object by default. In all other Windows project types, you must initialize the `My.User` object by calling the method explicitly or by assigning a value to . @@ -52,8 +52,6 @@ - - Objects (Visual Basic) @@ -365,7 +363,6 @@ ]]> - Objects (Visual Basic) diff --git a/xml/Microsoft.VisualBasic.Devices/Computer.xml b/xml/Microsoft.VisualBasic.Devices/Computer.xml index f9f110da96c..453d0fbf6ff 100644 --- a/xml/Microsoft.VisualBasic.Devices/Computer.xml +++ b/xml/Microsoft.VisualBasic.Devices/Computer.xml @@ -65,7 +65,6 @@ - Objects (Visual Basic) diff --git a/xml/Microsoft.VisualBasic.Devices/ServerComputer.xml b/xml/Microsoft.VisualBasic.Devices/ServerComputer.xml index 2b8af9e725a..45d8d3fc24b 100644 --- a/xml/Microsoft.VisualBasic.Devices/ServerComputer.xml +++ b/xml/Microsoft.VisualBasic.Devices/ServerComputer.xml @@ -65,7 +65,6 @@ - Objects (Visual Basic) diff --git a/xml/System.IdentityModel.Claims/ClaimTypes.xml b/xml/System.IdentityModel.Claims/ClaimTypes.xml index 0b584e655b5..0397c9822ed 100644 --- a/xml/System.IdentityModel.Claims/ClaimTypes.xml +++ b/xml/System.IdentityModel.Claims/ClaimTypes.xml @@ -122,7 +122,6 @@ The string returned by this property is `http://schemas.xmlsoap.org/ws/2005/05/i ]]> - @@ -160,7 +159,6 @@ The string returned by this property is `http://schemas.xmlsoap.org/ws/2005/05/i ]]> - @@ -272,7 +270,6 @@ The string returned by this property is `http://schemas.xmlsoap.org/ws/2005/05/i ]]> - @@ -348,7 +345,6 @@ The string returned by this property is `http://schemas.xmlsoap.org/ws/2005/05/i ]]> - diff --git a/xml/System.IdentityModel.Selectors/SecurityTokenRequirement.xml b/xml/System.IdentityModel.Selectors/SecurityTokenRequirement.xml index a2f35aca310..ff8cf33a29d 100644 --- a/xml/System.IdentityModel.Selectors/SecurityTokenRequirement.xml +++ b/xml/System.IdentityModel.Selectors/SecurityTokenRequirement.xml @@ -205,7 +205,6 @@ ]]> The property is set to a value less than 0. - @@ -281,7 +280,6 @@ ]]> - @@ -358,7 +356,6 @@ ]]> - @@ -396,7 +393,6 @@ ]]> - @@ -578,8 +574,6 @@ ]]> - - diff --git a/xml/System.IdentityModel.Tokens/SecurityToken.xml b/xml/System.IdentityModel.Tokens/SecurityToken.xml index 82f8733f288..bb7ac870dd7 100644 --- a/xml/System.IdentityModel.Tokens/SecurityToken.xml +++ b/xml/System.IdentityModel.Tokens/SecurityToken.xml @@ -95,10 +95,7 @@ You must override the , , , and properties. The , , , and methods all support key identifiers of type . You must override these methods to support other key identifier types in your derived class. - - - @@ -175,7 +172,6 @@ ]]> - @@ -225,7 +221,6 @@ ]]> - @@ -317,7 +312,6 @@ ]]> - @@ -365,7 +359,6 @@ When you inherit from , and implement the method and cannot be resolved, return . An exception should not be thrown from the method. - diff --git a/xml/System.ServiceModel.Description/DataContractSerializerOperationBehavior.xml b/xml/System.ServiceModel.Description/DataContractSerializerOperationBehavior.xml index 6852f9564c1..1d60088263a 100644 --- a/xml/System.ServiceModel.Description/DataContractSerializerOperationBehavior.xml +++ b/xml/System.ServiceModel.Description/DataContractSerializerOperationBehavior.xml @@ -74,7 +74,6 @@ ]]> - Data Contract Surrogates diff --git a/xml/System.ServiceModel.Dispatcher/FaultContractInfo.xml b/xml/System.ServiceModel.Dispatcher/FaultContractInfo.xml index 6b67caa8a7a..c9e0b9d4255 100644 --- a/xml/System.ServiceModel.Dispatcher/FaultContractInfo.xml +++ b/xml/System.ServiceModel.Dispatcher/FaultContractInfo.xml @@ -49,7 +49,6 @@ ]]> - diff --git a/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml b/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml index 4057ed47c89..5ee46fd9d6a 100644 --- a/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml +++ b/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml @@ -140,7 +140,6 @@ ]]> - @@ -716,7 +715,6 @@ Gets the key for the token requirement property whose value is the URI that the service endpoint making the request is listening at (service only). The key for the token requirement property whose value is the URI that the service endpoint making the request is listening at. To be added. - @@ -765,7 +763,6 @@ ]]> - @@ -1377,7 +1374,6 @@ Gets the key for the token requirement property whose value indicates whether to ignore errors that occur when recording the results of the authentication (service only). The key for the token requirement property whose value indicates whether to ignore errors that occur when recording the results of the authentication. To be added. - diff --git a/xml/System.ServiceModel/ServiceSecurityContext.xml b/xml/System.ServiceModel/ServiceSecurityContext.xml index 4b7ac29c4a4..c4caaa4ee9b 100644 --- a/xml/System.ServiceModel/ServiceSecurityContext.xml +++ b/xml/System.ServiceModel/ServiceSecurityContext.xml @@ -78,7 +78,6 @@ - How To: Examine the Security Context Authorization Policy Securing Services diff --git a/xml/System.ServiceProcess/ServiceBase.xml b/xml/System.ServiceProcess/ServiceBase.xml index a5a93191a2b..7cf0b11f24d 100644 --- a/xml/System.ServiceProcess/ServiceBase.xml +++ b/xml/System.ServiceProcess/ServiceBase.xml @@ -51,11 +51,11 @@ ## Remarks Derive from when defining your service class in a service application. Any useful service overrides the and methods. For additional functionality, you can override and with specific behavior in response to changes in the service state. - A service is a long-running executable that does not support a user interface, and which might not run under the logged-on user account. The service can run without any user being logged on to the computer. + A service is a long-running executable that doesn't support a user interface, and which might not run under the logged-on user account. The service can run without any user being logged on to the computer. - By default, services run under the System account, which is not the same as the Administrator account. You cannot change the rights of the System account. Alternatively, you can use a to specify a user account under which the service will run. + By default, services run under the System account, which is not the same as the Administrator account. You cannot change the rights of the System account. - An executable can contain more than one service but must contain a separate for each service. The instance registers the service with the system. The installer also associates each service with an event log that you can use to record service commands. The `main()` function in the executable defines which services should run. The current working directory of the service is the system directory, not the directory in which the executable is located. + An executable can contain more than one service. The `main()` function in the executable defines which services should run. The current working directory of the service is the system directory, not the directory in which the executable is located. When you start a service, the system locates the executable and runs the method for that service, contained within the executable. However, running the service is not the same as running the executable. The executable only loads the service. The service is accessed (for example, started and stopped) through the Service Control Manager. @@ -65,17 +65,15 @@ You can use the class to do programmatically what the SCM does using a user interface. You can automate the tasks available in the console. If , , or is `true` but you have not implemented a corresponding command-handling method (such as ) the system throws an exception and ignores the command. - You do not have to implement , , or any other method in . However, the service's behavior is described in , so at minimum, this member should be overridden. The `main()` function of the executable registers the service in the executable with the Service Control Manager by calling the method. The property of the object passed to the method must match the property of the service installer for that service. + You do not have to implement , , or any other method in . However, the service's behavior is described in , so at minimum, this member should be overridden. The `main()` function of the executable registers the service in the executable with the Service Control Manager by calling the method. You can use the `sc create` command to install services. > [!NOTE] -> You can specify a log other than the Application event log to receive notification of service calls, but neither the nor the property can write to a custom log. Set to `false` if you do not want to use automatic logging. +> You can specify a log other than the Application event log to receive notification of service calls, but the and properties can't write to a custom log. Set to `false` if you don't want to use automatic logging. ]]> - - @@ -114,7 +112,7 @@ If the executable contains multiple services, calling Start on one service causes the constructors to be called for all services in the executable, but only the specified service is started. Destructors for the services are run together when all services have been stopped, not individually when each service is stopped. > [!NOTE] -> If you override the base class constructor, you should explicitly call it in the constructor of your derived class. +> If you override the base class constructor, you should explicitly call it in the constructor of your derived class. ]]> @@ -164,7 +162,7 @@ To report information to a custom event log rather than the Application log, set to `false` and write instructions within the command-handling methods , , or to post to the appropriate log. > [!NOTE] -> The , which supplies the source string for the event log, must be set before the service attempts to write to the event log. Trying to access the event log before the source name is set throws an exception. +> The , which supplies the source string for the event log, must be set before the service attempts to write to the event log. Trying to access the event log before the source name is set throws an exception. ]]> @@ -357,7 +355,7 @@ If is `true`, the service is notified when the system is shutting down. At shutdown, the method is called if it has been implemented in your derived class. > [!NOTE] -> Only the system should cause the method to execute; the service can call it, but this is not recommended. +> Only the system should cause the method to execute; the service can call it, but this is not recommended. ]]> @@ -453,7 +451,7 @@ Call in your derived class (and through it, in the class) when you are finished using the derived class. The method leaves the derived class in an unusable state. After calling , you must release all references to the derived class and so the memory they were occupying can be reclaimed by garbage collection. > [!NOTE] -> Always call before you release your last reference to the class derived from . Otherwise, the resources and the derived class are using will not be freed until garbage collection calls the objects' destructors. +> Always call before you release your last reference to the class derived from . Otherwise, the resources and the derived class are using will not be freed until garbage collection calls the objects' destructors. is often implemented to process the code in , combined with a call to . If you choose to do this in your derived class, it is customary to implement to allocate whatever released. @@ -902,9 +900,7 @@ Use to specify the processing that occurs when the service receives a Start command. is the method in which you specify the behavior of the service. can take arguments as a way to pass data, but this usage is rare. > [!CAUTION] -> Do not use the constructor to perform processing that should be in . Use to handle all initialization of your service. The constructor is called when the application's executable runs, not when the service runs. The executable runs before . When you continue, for example, the constructor is not called again because the SCM already holds the object in memory. If releases resources allocated in the constructor rather than in , the needed resources would not be created again the second time the service is called. - - Services can be set to start automatically when the computer reboots by setting the on the service's installer to . In such a situation, would be called at system startup. +> Do not use the constructor to perform processing that should be in . Use to handle all initialization of your service. The constructor is called when the application's executable runs, not when the service runs. The executable runs before . When you continue, for example, the constructor is not called again because the SCM already holds the object in memory. If releases resources allocated in the constructor rather than in , the needed resources would not be created again the second time the service is called. is expected to be overridden in the derived class. For the service to be useful, and should both be implemented in your service class. @@ -1244,7 +1240,7 @@ identifies the service to the Service Control Manager. The value of this property must be identical to the name recorded for the service in the property of the corresponding installer class. In code, the of the service is usually set in the `main()` function of the executable. + The identifies the service to the Service Control Manager. In code, the of the service is usually set in the `main()` function of the executable. The is also used to specify the associated with the property. This is an instance that writes service command information to the Application log. @@ -1254,7 +1250,6 @@ The service has already been started. The property cannot be changed once the service has started. The specified name is a zero-length string or is longer than , or the specified name contains forward slash or backslash characters. - diff --git a/xml/System.ServiceProcess/ServiceStartMode.xml b/xml/System.ServiceProcess/ServiceStartMode.xml index eeb147dbf3a..5e16f1799ed 100644 --- a/xml/System.ServiceProcess/ServiceStartMode.xml +++ b/xml/System.ServiceProcess/ServiceStartMode.xml @@ -47,8 +47,6 @@ ]]> - - diff --git a/xml/System.Web.Services.Description/ServiceDescriptionFormatExtension.xml b/xml/System.Web.Services.Description/ServiceDescriptionFormatExtension.xml index 06204d39625..1bf66e1e9ae 100644 --- a/xml/System.Web.Services.Description/ServiceDescriptionFormatExtension.xml +++ b/xml/System.Web.Services.Description/ServiceDescriptionFormatExtension.xml @@ -103,16 +103,7 @@ Gets or sets a value indicating whether the is used by the import process when the extensibility element is imported. if the is used by the import process; otherwise, . The default is . - - by using the method (which is used by the wsdl.exe tool). You can also use a custom class derived from the class to extend the import process to handle custom extensibility elements. - - ]]> - - - + To be added. diff --git a/xml/System.Web.Services/WsiProfiles.xml b/xml/System.Web.Services/WsiProfiles.xml index 29a3bb1343c..a5342025309 100644 --- a/xml/System.Web.Services/WsiProfiles.xml +++ b/xml/System.Web.Services/WsiProfiles.xml @@ -35,15 +35,7 @@ Describes the Web services interoperability (WSI) specification to which a Web service claims to conform. - - property of the attribute to indicate the WSI specification to which the Web service claims to conform. - - ]]> - - + The WS-I organization publishes non-proprietary Web services specifications to promote the interoperability of Web services across platforms. diff --git a/xml/System.Web/HttpUtility.xml b/xml/System.Web/HttpUtility.xml index 71752c56fd6..a1751d00da1 100644 --- a/xml/System.Web/HttpUtility.xml +++ b/xml/System.Web/HttpUtility.xml @@ -59,11 +59,10 @@ class is used internally by the class, whose methods and properties are exposed through the intrinsic ASP.NET object. Additionally, the class contains encoding and decoding utility methods that are not accessible from the . - - To encode or decode values outside of a web application, use the class. +The class contains encoding and decoding utility methods. +To encode or decode values outside of a web application, use the class. ## Examples The following code example demonstrates the use of the , and methods of the class. @@ -73,9 +72,6 @@ ]]> - - - How to: Protect Against Script Exploits in a Web Application by Applying HTML Encoding to Strings diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml index 68a480c983a..fc5bf67ed26 100644 --- a/xml/System/AppDomain.xml +++ b/xml/System/AppDomain.xml @@ -984,7 +984,7 @@ The for the format of `assemblyName`. See the property for the format of `typeName`. > [!NOTE] -> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. +> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. @@ -992,7 +992,7 @@ The . The `Worker` class defines a method that displays the name of the application domain in which it is executing. The example creates instances of `Worker` in the default application domain and in a new application domain. > [!NOTE] -> The assembly that contains `Worker` must be loaded into both application domains, but it can load other assemblies that exist only in the new application domain. +> The assembly that contains `Worker` must be loaded into both application domains, but it can load other assemblies that exist only in the new application domain. :::code language="cpp" source="~/snippets/cpp/VS_Snippets_CLR/CreateInstanceAndUnwrap2/cpp/source.cpp" id="Snippet1"::: :::code language="csharp" source="~/snippets/csharp/System/AppDomain/CreateInstanceAndUnwrap/source.cs" id="Snippet1"::: @@ -1094,7 +1094,7 @@ The for the format of `assemblyName`. See the property for the format of `typeName`. > [!NOTE] -> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. +> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. @@ -1209,7 +1209,7 @@ The for the format of `assemblyName`. See the property for the format of `typeName`. > [!NOTE] -> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. +> If you make an early-bound call to a method `M` of an object of type `T1` that was returned by , and that method makes an early-bound call to a method of an object of type `T2` in an assembly `C` other than the current assembly or the assembly containing `T1`, assembly `C` is loaded into the current application domain. This loading occurs even if the early-bound call to `T1.M()` was made in the body of a , or in other dynamically generated code. If the current domain is the default domain, assembly `C` cannot be unloaded until the process ends. If the current domain later attempts to load assembly `C`, the load might fail. @@ -1329,7 +1329,7 @@ The method overload to load the example assembly into the target application domain and create an instance of `MarshalableExample`. > [!NOTE] -> The path is absolute in this example, but a relative path would also work because the method is used to load the assembly. +> The path is absolute in this example, but a relative path would also work because the method is used to load the assembly. After unwrapping the object handle, the example demonstrates three ways to use an object in a target application domain: @@ -2015,7 +2015,7 @@ The delegate does not identify the domain that is being unloaded. > [!NOTE] -> This event is never raised in the default application domain. +> This event is never raised in the default application domain. Do not make assumptions about the thread the event is raised on. The event can be raised on a different thread than the one that called the method. @@ -2074,37 +2074,7 @@ The Gets the directory that the assembly resolver uses to probe for dynamically created assemblies. The directory that the assembly resolver uses to probe for dynamically created assemblies. - - property of the object that will be used to create the new application domain. The base directory path you assign to the property is modified by the addition of a subdirectory whose simple name is the hash code of the string you assign to the property, so the format of the base directory is *original path*\\*hash code*. The dynamic directory is a subdirectory of this base directory. Its simple name is the value of the property, so its format is *original path*\\*hash code*\\*application name*. - - - -## Examples - The following example creates an application domain with a directory for dynamic assemblies, emits a dynamic assembly and stores it in the dynamic directory, and then loads the assembly into the new application domain and uses it. - - The example creates an object and sets its property to "Example" and its property to "C:\DynamicAssemblyDir". The example then displays the property, to show that the hash code of the application name has been appended as a subdirectory of the path that was originally assigned. - -> [!NOTE] -> The base directory in this example is intended to be outside the probing path for the example application. Be sure to compile the example in a different location. Delete the base directory and all its subdirectories each time you run the example. - - The example creates a new application domain, using the object. The example uses the property to retrieve the name of the directory, so it can create the directory. (The example could just as easily create the directory beforehand by concatenating the original path, the hash code of the application name, and the application name.) - - The example has a `GenerateDynamicAssembly` method that emits an assembly named `DynamicHelloWorld.dll` and stores it in the new application domain's dynamic directory. The dynamic assembly contains one type, `HelloWorld`, that has a static method (`Shared` method in Visual Basic) named `HelloFromAD`. Calling this method displays the name of the application domain. - - The `Example` class derives from , so the example can create an instance of the class in the new application domain and call its `Test` method. The `Test` method loads the dynamic assembly by its display name and calls the static `HelloFromAD` method. - - You can show that the dynamic directory is searched after the normal probing paths by writing code for an assembly named `DynamicHelloWorld.dll` and compiling it in the same directory as this example. The assembly must have a class named `HelloWorld` with a static method named `HelloFromAD`. This method does not have to have the same functionality as the one in the example; it can simply display a string to the console. The assembly must also have an attribute that sets its version to 1.0.0.0. When you run the example, the assembly you compiled in the current directory is found before the dynamic directory is searched. - - :::code language="cpp" source="~/snippets/cpp/VS_Snippets_CLR/ADDynamicBase/CPP/addynamicbase.cpp" id="Snippet1"::: - :::code language="csharp" source="~/snippets/csharp/System/AppDomain/DynamicDirectory/addynamicbase.cs" id="Snippet1"::: - :::code language="fsharp" source="~/snippets/fsharp/System/AppDomain/DynamicDirectory/addynamicbase.fs" id="Snippet1"::: - :::code language="vb" source="~/snippets/visualbasic/System/AppDomain/DynamicDirectory/addynamicbase.vb" id="Snippet1"::: - - ]]> - + To be added. The operation is attempted on an unloaded application domain. @@ -2679,7 +2649,7 @@ The event is handled in all application domains except `AD1`. > [!NOTE] -> In addition to this example, which demonstrates first-chance exception notifications in multiple application domains, you can find simple use cases in [How to: Receive First-Chance Exception Notifications](/dotnet/framework/app-domains/how-to-receive-first-chance-exception-notifications). +> In addition to this example, which demonstrates first-chance exception notifications in multiple application domains, you can find simple use cases in [How to: Receive First-Chance Exception Notifications](/dotnet/framework/app-domains/how-to-receive-first-chance-exception-notifications). When the application domains have been created, the default application domain calls the `TestException` method for the first application domain. Each `Worker` object calls the `TestException` method for the next application domain, until the last `Worker` throws an exception that is either handled or unhandled. Thus, the current thread passes through all the application domains, and `TestException` is added to the stack in each application domain. @@ -2688,7 +2658,7 @@ The event is raised in each application domain that has an event handler. After each event handler has finished, the stack continues to unwind until the exception is caught by the default application domain. > [!NOTE] -> To see how the stack display grows as the event is raised closer and closer to the default application domain, change `e.Exception.Message` to `e.Exception` in the `FirstChanceHandler` event handlers. Notice that when `TestException` is called across application domain boundaries, it appears twice: once for the proxy and once for the stub. +> To see how the stack display grows as the event is raised closer and closer to the default application domain, change `e.Exception.Message` to `e.Exception` in the `FirstChanceHandler` event handlers. Notice that when `TestException` is called across application domain boundaries, it appears twice: once for the proxy and once for the stub. :::code language="csharp" source="~/snippets/csharp/System/AppDomain/FirstChanceException/example.cs" id="Snippet1"::: :::code language="fsharp" source="~/snippets/fsharp/System/AppDomain/FirstChanceException/example.fs" id="Snippet1"::: @@ -2955,29 +2925,21 @@ The friendly name of the default application domain is the file name of the proc The following table describes the `name` of each predefined system entry and its corresponding property. -|Value of 'name'|Property| -|---------------------|--------------| -|"APPBASE"|| -|"APP_CONFIG_FILE"|| -|"APP_LAUNCH_URL"|(no property)

"APP_LAUNCH_URL" represents the URL originally requested by the user, before any redirection. It is available only when the application has been launched with a browser. Not all browsers provide this value.| -|"APP_NAME"|| -|"BINPATH_PROBE_ONLY"|| -|"CACHE_BASE"|| -|"CODE_DOWNLOAD_DISABLED"|| -|"DEV_PATH"|(no property)| -|"DISALLOW_APP"|| -|"DISALLOW_APP_BASE_PROBING"|| -|"DISALLOW_APP_REDIRECTS"|| -|"DYNAMIC_BASE"|| -|"FORCE_CACHE_INSTALL"|| -|"LICENSE_FILE", or an application-specific string|| -|"LOADER_OPTIMIZATION"|| -|"LOCATION_URI"|(no property)| -|"PRIVATE_BINPATH"|| -|"REGEX_DEFAULT_MATCH_TIMEOUT"|

"REGEX_DEFAULT_MATCH_TIMEOUT" is not a system entry, and its value can be set by calling the method.| -|"SHADOW_COPY_DIRS"|| - - +| Value of 'name' | Property | +|---------------------------------------------------|-------------------------------------------------------------------------------------------| +| "APPBASE" | | +| "APP_CONFIG_FILE" | | +| "APP_LAUNCH_URL" | (no property)

"APP_LAUNCH_URL" represents the URL originally requested by the user, before any redirection. It is available only when the application has been launched with a browser. Not all browsers provide this value.| +| "CODE_DOWNLOAD_DISABLED" | | +| "DEV_PATH" | (no property) | +| "DISALLOW_APP" | | +| "DISALLOW_APP_BASE_PROBING" | | +| "DISALLOW_APP_REDIRECTS" | | +| "LICENSE_FILE", or an application-specific string | | +| "LOADER_OPTIMIZATION" | | +| "LOCATION_URI" | (no property) | +| "REGEX_DEFAULT_MATCH_TIMEOUT" |

"REGEX_DEFAULT_MATCH_TIMEOUT" is not a system entry, and its value can be set by calling the method. | +| "SHADOW_COPY_DIRS" | | ## Examples The following example creates a new application domain, sets a system-provided value for the domain, and adds a new value pair for the domain. The example then demonstrates how to use the method to retrieve the data from these value pairs and display them to the console. @@ -3099,11 +3061,10 @@ The friendly name of the default application domain is the file name of the proc method before creating an application domain. + This method tests whether the specified compatibility switch has been set for the current application domain. Compatibility switches typically restore a behavior (such as the way strings are sorted) that was changed between versions of .NET. ]]> - @@ -3222,12 +3183,12 @@ The friendly name of the default application domain is the file name of the proc An object's finalization method is called in one of the following situations: during garbage collection, when the common language runtime is shutting down, or when the application domain that contains the object is unloaded. The method returns `true` only in the last case; it does not return `true` if finalization results from routine garbage collection or from CLR shutdown. > [!NOTE] -> To determine whether finalization is due to CLR shutdown, use the property. It returns `true` if finalization is due to an application domain being unloaded or to the CLR shutting down. +> To determine whether finalization is due to CLR shutdown, use the property. It returns `true` if finalization is due to an application domain being unloaded or to the CLR shutting down. While executing in your finalization method during domain unloading, you might want to access another object that is referenced by a static field and has a finalization method. However, you cannot reliably do so because the accessed object might already have been finalized. > [!NOTE] -> An exception to this rule is the class, which contains static fields that reference stream objects, but is implemented specially so you can always write to the system console, even during domain unloading or system shutdown. +> An exception to this rule is the class, which contains static fields that reference stream objects, but is implemented specially so you can always write to the system console, even during domain unloading or system shutdown. Use this method in an object's finalization method to determine whether the application domain that contains the object is unloading. If that is the case, you cannot reliably access any object that has a finalization method and is referenced by a static field. @@ -3480,7 +3441,7 @@ The friendly name of the default application domain is the file name of the proc The assembly is loaded into both domains because does not derive from , and therefore the return value of the method cannot be marshaled. Instead, the common language runtime tries to load the assembly into the calling application domain. The assemblies that are loaded into the two application domains might be different if the path settings for the two application domains are different. > [!NOTE] -> If both the property and the property are set, the first attempt to load the assembly uses the display name (including version, culture, and so on, as returned by the property). If the file is not found, the property is used to search for the assembly. If the assembly is found using , the display name is matched against the assembly. If the match fails, a is thrown. +> If both the property and the property are set, the first attempt to load the assembly uses the display name (including version, culture, and so on, as returned by the property). If the file is not found, the property is used to search for the assembly. If the assembly is found using , the display name is matched against the assembly. If the match fails, a is thrown. ]]> @@ -4081,7 +4042,7 @@ This event is raised in each application domain that registers an event handler. In the reflection-only context, dependencies are not resolved automatically. They must be preloaded or returned by the handler for this event. This event is raised when an assembly has a dependency that is not already loaded into the reflection-only context. The missing dependency is specified by the property. The for this event must return an assembly that satisfies the dependency. The assembly that is returned must be loaded into the reflection-only context. > [!IMPORTANT] -> This event is raised only for missing dependencies of the assembly that you are loading into the reflection-only context (for example, by using the method). It is not raised if the assembly that you are loading cannot be found. +> This event is raised only for missing dependencies of the assembly that you are loading into the reflection-only context (for example, by using the method). It is not raised if the assembly that you are loading cannot be found. The property returns the assembly that requested the assembly load that could not be resolved. Knowing the identity of the requesting assembly might be useful in identifying the correct version of the dependency, if more than one version is available. For more information, see . @@ -4213,12 +4174,9 @@ The property is not under , it is ignored. - This property returns the value set using . - ]]> The operation is attempted on an unloaded application domain. - @@ -4276,7 +4234,7 @@ The for this event can attempt to locate the assembly containing the resource and return it. > [!IMPORTANT] -> This event is not raised if resolution fails because no file can be found for a valid linked resource. It is raised if a manifest resource stream cannot be found, but it is not raised if an individual resource key cannot be found. +> This event is not raised if resolution fails because no file can be found for a valid linked resource. It is raised if a manifest resource stream cannot be found, but it is not raised if an individual resource key cannot be found. The property contains the assembly that requested the resource. For more information, see . @@ -4351,8 +4309,6 @@ The Establishes the specified directory path as the location where assemblies are shadow copied. To be added. The operation is attempted on an unloaded application domain. - - Shadow Copying Assemblies @@ -4508,7 +4464,6 @@ The Establishes the specified directory path as the base directory for subdirectories where dynamically generated files are stored and accessed. To be added. The operation is attempted on an unloaded application domain. - @@ -4850,20 +4805,11 @@ The System.Boolean - Gets an indication whether the application domain is configured to shadow copy files. + Gets an value that indicates whether the application domain is configured to shadow copy files. if the application domain is configured to shadow copy files; otherwise, . - - and [Shadow Copying Assemblies](/dotnet/framework/app-domains/shadow-copy-assemblies). - - ]]> - + To be added. The operation is attempted on an unloaded application domain. - - Shadow Copying Assemblies diff --git a/xml/System/ContextBoundObject.xml b/xml/System/ContextBoundObject.xml index cbd1d95da8e..de1e6eed3a7 100644 --- a/xml/System/ContextBoundObject.xml +++ b/xml/System/ContextBoundObject.xml @@ -68,7 +68,6 @@ The current version of the common language runtime does not support generic types or nongeneric types that have generic methods. Attempting to create an instance of such a type causes a . - diff --git a/xml/System/ContextStaticAttribute.xml b/xml/System/ContextStaticAttribute.xml index bd8a4d36651..fd6dc7ec59b 100644 --- a/xml/System/ContextStaticAttribute.xml +++ b/xml/System/ContextStaticAttribute.xml @@ -78,7 +78,6 @@ ]]> - Extending Metadata Using Attributes diff --git a/xml/System/LocalDataStoreSlot.xml b/xml/System/LocalDataStoreSlot.xml index 1db24f5591c..f942b1254f5 100644 --- a/xml/System/LocalDataStoreSlot.xml +++ b/xml/System/LocalDataStoreSlot.xml @@ -63,12 +63,11 @@ The data slots are unique per thread or context; their values are not shared between the thread or context objects. Data slots can be allocated by a name or by an index number. - For more information about storing local data, see or . The class is used with methods such as , , , and ; it does not have any methods of its own that you need to use. + For more information about storing local data, see . The class is used with methods such as and . It doesn't have any methods of its own that you need to use. ]]> - diff --git a/xml/System/MissingMemberException.xml b/xml/System/MissingMemberException.xml index e0ebceea248..ebe97330573 100644 --- a/xml/System/MissingMemberException.xml +++ b/xml/System/MissingMemberException.xml @@ -641,12 +641,11 @@ ## Remarks contains a value that represents the signature of the missing member. - is used to format the signature. For additional information, see , , and . + is used to format the signature. For more information, see and . ]]> - diff --git a/xml/System/Type.xml b/xml/System/Type.xml index c6859f93001..8dd3eda559d 100644 --- a/xml/System/Type.xml +++ b/xml/System/Type.xml @@ -10831,7 +10831,6 @@ The following table summarizes the interactions between `assemblyResolver`, `typ is . - @@ -10919,7 +10918,6 @@ The following table summarizes the interactions between `assemblyResolver`, `typ is . The specified ProgID is not registered. - @@ -11002,7 +11000,6 @@ The following table summarizes the interactions between `assemblyResolver`, `typ is . - @@ -11093,7 +11090,6 @@ The following table summarizes the interactions between `assemblyResolver`, `typ is . The specified progID is not registered. -