diff --git a/xml/System.ComponentModel.Design.Serialization/CodeDomComponentSerializationService.xml b/xml/System.ComponentModel.Design.Serialization/CodeDomComponentSerializationService.xml index 56b7e757a52..1ab274f9537 100644 --- a/xml/System.ComponentModel.Design.Serialization/CodeDomComponentSerializationService.xml +++ b/xml/System.ComponentModel.Design.Serialization/CodeDomComponentSerializationService.xml @@ -54,7 +54,6 @@ - Dynamic Source Code Generation and Compilation @@ -129,7 +128,6 @@ To be added. - Dynamic Source Code Generation and Compilation @@ -173,7 +171,6 @@ - Dynamic Source Code Generation and Compilation @@ -226,7 +223,6 @@ is not a supported type of serialization store. Use a store returned by . - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/CodeDomDesignerLoader.xml b/xml/System.ComponentModel.Design.Serialization/CodeDomDesignerLoader.xml index e5166779159..ae30f7fe092 100644 --- a/xml/System.ComponentModel.Design.Serialization/CodeDomDesignerLoader.xml +++ b/xml/System.ComponentModel.Design.Serialization/CodeDomDesignerLoader.xml @@ -62,7 +62,6 @@ - Dynamic Source Code Generation and Compilation @@ -238,7 +237,6 @@ - Dynamic Source Code Generation and Compilation @@ -500,7 +498,6 @@ ]]> - Dynamic Source Code Generation and Compilation @@ -600,7 +597,6 @@ The language did not provide a code parser for this file; this file type may not support a designer. The class can be designed, but it is not the first class in the file, or the designer could not be shown for this file because none of the classes within it can be designed. - Dynamic Source Code Generation and Compilation @@ -878,7 +874,6 @@ ]]> - Dynamic Source Code Generation and Compilation @@ -923,7 +918,6 @@ ]]> - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/CodeDomLocalizationProvider.xml b/xml/System.ComponentModel.Design.Serialization/CodeDomLocalizationProvider.xml index 05ec6515fde..47298648336 100644 --- a/xml/System.ComponentModel.Design.Serialization/CodeDomLocalizationProvider.xml +++ b/xml/System.ComponentModel.Design.Serialization/CodeDomLocalizationProvider.xml @@ -60,7 +60,7 @@ ]]> - Dynamic Source Code Generation and Compilation + @@ -115,7 +115,6 @@ ]]> - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/CodeDomSerializer.xml b/xml/System.ComponentModel.Design.Serialization/CodeDomSerializer.xml index 07f2fb9ac01..85f255a65d5 100644 --- a/xml/System.ComponentModel.Design.Serialization/CodeDomSerializer.xml +++ b/xml/System.ComponentModel.Design.Serialization/CodeDomSerializer.xml @@ -87,7 +87,6 @@ When you inherit from , you must override the following members: and . - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/CodeDomSerializerBase.xml b/xml/System.ComponentModel.Design.Serialization/CodeDomSerializerBase.xml index 69010bd3c9a..6362af07f13 100644 --- a/xml/System.ComponentModel.Design.Serialization/CodeDomSerializerBase.xml +++ b/xml/System.ComponentModel.Design.Serialization/CodeDomSerializerBase.xml @@ -122,17 +122,14 @@ continues to interpret expressions until they are completely resolved to an object, or until it can no longer simplify the expression. In this case, will return a that contains the most simplified expression. The following expressions are not supported: -- - -- - -- +- +- +- ]]> - Dynamic Source Code Generation and Compilation @@ -204,7 +201,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -265,7 +261,6 @@ ]]> - Dynamic Source Code Generation and Compilation @@ -315,7 +310,6 @@ - Dynamic Source Code Generation and Compilation @@ -507,7 +501,6 @@ is . - Dynamic Source Code Generation and Compilation @@ -712,7 +705,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -769,7 +761,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -865,7 +856,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -925,7 +915,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -979,7 +968,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -1041,7 +1029,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -1104,7 +1091,6 @@ - Dynamic Source Code Generation and Compilation @@ -1173,7 +1159,6 @@ - Dynamic Source Code Generation and Compilation @@ -1238,7 +1223,6 @@ - Dynamic Source Code Generation and Compilation @@ -1307,7 +1291,6 @@ - Dynamic Source Code Generation and Compilation @@ -1364,7 +1347,6 @@ - Dynamic Source Code Generation and Compilation @@ -1429,7 +1411,6 @@ - Dynamic Source Code Generation and Compilation @@ -1490,7 +1471,6 @@ - Dynamic Source Code Generation and Compilation @@ -1570,7 +1550,6 @@ - Dynamic Source Code Generation and Compilation @@ -1634,11 +1613,11 @@ The method will look on the for the following objects: -- - a collection of statements to add a resource manager to, if one needs to be declared. +- - a collection of statements to add a resource manager to, if one needs to be declared. -- - the root expression, which is needed to create a resource manager. +- - the root expression, which is needed to create a resource manager. -- - used to fabricate a name for the resource and to decide what type of resource manager call to make. +- - used to fabricate a name for the resource and to decide what type of resource manager call to make. ]]> @@ -1646,7 +1625,6 @@ is . - Dynamic Source Code Generation and Compilation @@ -1708,7 +1686,6 @@ is . - Dynamic Source Code Generation and Compilation @@ -1769,7 +1746,6 @@ , , or is . - Dynamic Source Code Generation and Compilation @@ -1822,7 +1798,6 @@ - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/CollectionCodeDomSerializer.xml b/xml/System.ComponentModel.Design.Serialization/CollectionCodeDomSerializer.xml index ff899b5c5ac..8851520464f 100644 --- a/xml/System.ComponentModel.Design.Serialization/CollectionCodeDomSerializer.xml +++ b/xml/System.ComponentModel.Design.Serialization/CollectionCodeDomSerializer.xml @@ -51,7 +51,6 @@ ]]> - Dynamic Source Code Generation and Compilation @@ -129,7 +128,6 @@ is . - Dynamic Source Code Generation and Compilation @@ -196,7 +194,6 @@ or is . - Dynamic Source Code Generation and Compilation @@ -266,7 +263,6 @@ , , , or is . - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel.Design.Serialization/TypeCodeDomSerializer.xml b/xml/System.ComponentModel.Design.Serialization/TypeCodeDomSerializer.xml index 27dff6e7ffd..8f1bf2b6cca 100644 --- a/xml/System.ComponentModel.Design.Serialization/TypeCodeDomSerializer.xml +++ b/xml/System.ComponentModel.Design.Serialization/TypeCodeDomSerializer.xml @@ -58,7 +58,6 @@ - Dynamic Source Code Generation and Compilation @@ -153,7 +152,6 @@ - Dynamic Source Code Generation and Compilation @@ -208,7 +206,6 @@ - Dynamic Source Code Generation and Compilation @@ -261,7 +258,6 @@ - Dynamic Source Code Generation and Compilation @@ -344,7 +340,6 @@ - Dynamic Source Code Generation and Compilation diff --git a/xml/System.ComponentModel/EventDescriptor.xml b/xml/System.ComponentModel/EventDescriptor.xml index 0cf501ac437..cf91e3ce162 100644 --- a/xml/System.ComponentModel/EventDescriptor.xml +++ b/xml/System.ComponentModel/EventDescriptor.xml @@ -71,9 +71,7 @@ - unbinds the delegate from the component so that the delegate no longer receives events from the component. - For more information about events, see [Handling and Raising Events](/dotnet/standard/events/). For more information about reflection, see the topics in [Reflection](/dotnet/framework/reflection-and-codedom/reflection). - - + For more information about events, see [Handling and Raising Events](/dotnet/standard/events/). For more information about reflection, see [Reflection](/dotnet/framework/reflection-and-codedom/reflection). ## Examples The following code example is built upon the example in the class. It prints the information (category, description, and display name) of each event on a button in a text box. It requires that `button1` and `textbox1` have been instantiated on a form. @@ -303,7 +301,7 @@ A that contains the event data. Represents the method that will handle the event of the class. - delegate, you identify a method to handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event-handler delegates, see [Handling and Raising Events](/dotnet/standard/events/). - - - -## Examples - For an example of using this delegate, see [Handling DataView Events](/dotnet/framework/data/adonet/dataset-datatable-dataview/handling-dataview-events). - + delegate, you identify a method to handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, unless you remove the delegate. For more information about event-handler delegates, see [Handling and Raising Events](/dotnet/standard/events/). + +## Examples + For an example of using this delegate, see [Handling DataView Events](/dotnet/framework/data/adonet/dataset-datatable-dataview/handling-dataview-events). + ]]> diff --git a/xml/System.ComponentModel/ListChangedType.xml b/xml/System.ComponentModel/ListChangedType.xml index 94c8ad9435f..78cb07f9281 100644 --- a/xml/System.ComponentModel/ListChangedType.xml +++ b/xml/System.ComponentModel/ListChangedType.xml @@ -50,8 +50,6 @@ ## Remarks Used by the property of the class to indicate the way an object changes. - - ## Examples For an example of using this class, see [Handling DataView Events](/dotnet/framework/data/adonet/dataset-datatable-dataview/handling-dataview-events). diff --git a/xml/System.ComponentModel/PropertyDescriptor.xml b/xml/System.ComponentModel/PropertyDescriptor.xml index 1e15b35ee21..199db86b008 100644 --- a/xml/System.ComponentModel/PropertyDescriptor.xml +++ b/xml/System.ComponentModel/PropertyDescriptor.xml @@ -61,33 +61,22 @@ provides the following properties and methods: -- contains the for this property. - -- indicates whether this property should be localized. - -- returns an editor of the specified type. - - also provides the following `abstract` properties and methods: - -- contains the type of component this property is bound to. - -- indicates whether this property is read-only. - -- gets the type of the property. - -- indicates whether resetting the component changes the value of the component. - -- returns the current value of the property on a component. - -- resets the value for this property of the component. - -- sets the value of the component to a different value. - -- indicates whether the value of this property needs to be persisted. - - Typically, the `abstract` members are implemented through reflection. For more information about reflection, see the topics in [Reflection](/dotnet/framework/reflection-and-codedom/reflection). - - +- contains the for this property. +- indicates whether this property should be localized. +- returns an editor of the specified type. + + also provides the following `abstract` properties and methods: + +- contains the type of component this property is bound to. +- indicates whether this property is read-only. +- gets the type of the property. +- indicates whether resetting the component changes the value of the component. +- returns the current value of the property on a component. +- resets the value for this property of the component. +- sets the value of the component to a different value. +- indicates whether the value of this property needs to be persisted. + + Typically, the `abstract` members are implemented through reflection. For more information, see [Reflection](/dotnet/framework/reflection-and-codedom/reflection). ## Examples The following code example is built upon the example in the class. It prints the information (category, description, display name) of the text of a button in a text box. It assumes that `button1` and `textbox1` have been instantiated on a form. diff --git a/xml/System.ComponentModel/TypeConverter.xml b/xml/System.ComponentModel/TypeConverter.xml index 2b27c8f2b11..53f58163af1 100644 --- a/xml/System.ComponentModel/TypeConverter.xml +++ b/xml/System.ComponentModel/TypeConverter.xml @@ -60,14 +60,12 @@ The most common type of converter is one that converts to and from a text representation. The type converter for a class is bound to the class with a . Unless this attribute is overridden, all classes that inherit from this class use the same type converter as the base class. > [!NOTE] -> For general type system purposes, do not access a type converter directly. Instead, access the appropriate converter by using . For more information, see the code examples provided. +> For general type system purposes, do not access a type converter directly. Instead, access the appropriate converter by using . For more information, see the code examples provided. > > However, when using XAML, a XAML processor searches for the directly, instead of going through . For cases where you do want a instance from code, or where you create a shared instance in WPF resources, it is acceptable to construct it directly without referencing or other reflection and type system support. Classes derived from are often referenced as part of how a XAML processor converts an attribute or initialization text value from markup (which is inherently a string) and generates an object for a run-time representation. Custom type authors that intend to support a type conversion behavior for XAML typically implement a class that supports their own unique `ConvertFrom` behavior from a string. This behavior enables type conversion from the string provided as a XAML attribute value and provides a XAML processor with the support needed to create an object from the string, so that the object can be produced in a parsed object graph. Custom types or members of custom types are indicated by applying to the definitions, with the attribute referencing the custom implementation. For more information, see [Type Converters for XAML Overview](/dotnet/framework/xaml-services/type-converters-for-xaml-overview). - - ## Examples The following code example shows how to create an instance of a type converter and bind it to a class. The class implementing the converter, `MyClassConverter`, must inherit from the class. diff --git a/xml/System.Data/Constraint.xml b/xml/System.Data/Constraint.xml index 19bad7a9781..99abbcec05b 100644 --- a/xml/System.Data/Constraint.xml +++ b/xml/System.Data/Constraint.xml @@ -67,8 +67,6 @@ A base constructor is not used. Primary or unique key constraints are created by using the constructor, and foreign key constraints are created by using the constructor. - - ## Examples The following example examines the collection of constraints for a and determines whether each constraint is a or a . The properties of the constraint are then displayed. diff --git a/xml/System.Net.Security/AuthenticationLevel.xml b/xml/System.Net.Security/AuthenticationLevel.xml index e159e0f45d8..98839deb18f 100644 --- a/xml/System.Net.Security/AuthenticationLevel.xml +++ b/xml/System.Net.Security/AuthenticationLevel.xml @@ -51,9 +51,7 @@ The values of this enumeration are used to set the property. > [!NOTE] -> The MutualAuthRequired and MutualAuthRequested values are relevant for Kerberos authentication. Kerberos authentication can be supported directly, or can be used if the Negotiate security protocol is used to select the actual security protocol. For more information about authentication protocols, see [Internet Authentication](/dotnet/framework/network-programming/internet-authentication). - - +> The MutualAuthRequired and MutualAuthRequested values are relevant for Kerberos authentication. Kerberos authentication can be supported directly, or can be used if the Negotiate security protocol is used to select the actual security protocol. For more information about authentication protocols, see [Internet Authentication](/dotnet/framework/network-programming/internet-authentication). ## Examples The following code example demonstrates setting the authentication flags for a request. diff --git a/xml/System.Net.Security/NegotiateStream.xml b/xml/System.Net.Security/NegotiateStream.xml index 8606efcd320..05d0d24b532 100644 --- a/xml/System.Net.Security/NegotiateStream.xml +++ b/xml/System.Net.Security/NegotiateStream.xml @@ -88,7 +88,6 @@ The following code example demonstrates the server side of a client-server conne ]]> - Changes to NTLM authentication for HTTPWebRequest in Version 3.5 SP1 diff --git a/xml/System.Net/AuthenticationManager.xml b/xml/System.Net/AuthenticationManager.xml index f95df311e33..4e698900a9e 100644 --- a/xml/System.Net/AuthenticationManager.xml +++ b/xml/System.Net/AuthenticationManager.xml @@ -71,7 +71,6 @@ ]]> - Changes to NTLM authentication for HTTPWebRequest in Version 3.5 SP1 @@ -258,8 +257,6 @@ Version 3.5 SP1 now defaults to specifying the host name used in the request URL in the SPN in the NTLM (NT LAN Manager) authentication exchange when the property is not set. The host name used in the request URL may be different from the Host header specified in the in the client request. The host name used in the request URL may be different from the actual host name of the server, the machine name of the server, the computer's IP address, or the loopback address. In these cases, Windows will fail the authentication request. To address the issue, you may need to notify Windows that the host name used in the request URL in the client request ("contoso", for example) is actually an alternate name for the local computer. - - ## Examples The following code example demonstrates displaying the contents of the . @@ -267,7 +264,6 @@ ]]> - Changes to NTLM authentication for HTTPWebRequest in Version 3.5 SP1 diff --git a/xml/System.Net/HttpListener.xml b/xml/System.Net/HttpListener.xml index d14e57c6a46..201f537f392 100644 --- a/xml/System.Net/HttpListener.xml +++ b/xml/System.Net/HttpListener.xml @@ -109,7 +109,6 @@ Starting in .NET 11, the Windows `HTTP.sys` implementation of - Changes to NTLM authentication for HTTPWebRequest in Version 3.5 SP1 HttpCfg.exe diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml index 1ab2e5d20ce..0014cf0c1a0 100644 --- a/xml/System.Reflection.Emit/DynamicMethod.xml +++ b/xml/System.Reflection.Emit/DynamicMethod.xml @@ -57,7 +57,7 @@ You can use the class to generate an A dynamic method can be anonymously hosted, or it can be logically associated with a module or with a type. -- If the dynamic method is anonymously hosted, it is located in a system-provided assembly, and therefore is isolated from other code. By default, it does not have access to any non-public data. An anonymously hosted dynamic method can have restricted ability to skip the JIT compiler's visibility checks, if it has been granted with the flag. The trust level of the assembly whose non-public members are accessed by the dynamic method must be equal to, or a subset of, the trust level of the call stack that emitted the dynamic method. For more information about anonymously hosted dynamic methods, see [Walkthrough: Emitting Code in Partial Trust Scenarios](/dotnet/framework/reflection-and-codedom/walkthrough-emitting-code-in-partial-trust-scenarios). +- If the dynamic method is anonymously hosted, it is located in a system-provided assembly, and therefore is isolated from other code. By default, it does not have access to any non-public data. An anonymously hosted dynamic method can have restricted ability to skip the JIT compiler's visibility checks, if it has been granted with the flag. The trust level of the assembly whose non-public members are accessed by the dynamic method must be equal to, or a subset of, the trust level of the call stack that emitted the dynamic method. - If the dynamic method is associated with a module that you specify, the dynamic method is effectively global to that module. It can access all types in the module and all `internal` (`Friend` in Visual Basic) members of the types. You can associate a dynamic method with any module, regardless of whether you created the module, provided that a demand for with the flag can be satisfied by the call stack that includes your code. If the flag is included in the grant, the dynamic method can skip the JIT compiler's visibility checks and access the private data of all types declared in the module or in any other module in any assembly. @@ -91,8 +91,8 @@ Although dynamic methods are `static` methods (`Shared` methods in Visual Basic) The following list summarizes the conditions under which dynamic methods can contain unverifiable code. (For example, a dynamic method is unverifiable if its property is set to `false`.) - A dynamic method that's associated with a security-critical assembly is also security-critical, and can skip verification. For example, an assembly without security attributes that is run as a desktop application is treated as security-critical by the runtime. If you associate a dynamic method with the assembly, the dynamic method can contain unverifiable code. -- If a dynamic method that contains unverifiable code is associated with an assembly that has level 1 transparency, the just-in-time (JIT) compiler injects a security demand. The demand succeeds only if the dynamic method is executed by fully trusted code. See [Security-Transparent Code, Level 1](/dotnet/framework/misc/security-transparent-code-level-1). -- If a dynamic method that contains unverifiable code is associated with an assembly that has level 2 transparency (such as mscorlib.dll), it throws an exception (injected by the JIT compiler) instead of making a security demand. See [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2). +- If a dynamic method that contains unverifiable code is associated with an assembly that has level 1 transparency, the just-in-time (JIT) compiler injects a security demand. The demand succeeds only if the dynamic method is executed by fully trusted code. +- If a dynamic method that contains unverifiable code is associated with an assembly that has level 2 transparency (such as mscorlib.dll), it throws an exception (injected by the JIT compiler) instead of making a security demand. - An anonymously hosted dynamic method that contains unverifiable code always throws an exception. It can never skip verification, even if it is created and executed by fully trusted code. The exception that's thrown for unverifiable code varies depending on the way the dynamic method is invoked. If you invoke a dynamic method by using a delegate returned from the method, a is thrown. If you invoke the dynamic method by using the method, a is thrown with an inner . diff --git a/xml/System.Reflection/Assembly.xml b/xml/System.Reflection/Assembly.xml index b2bf13bd787..ccc84146bba 100644 --- a/xml/System.Reflection/Assembly.xml +++ b/xml/System.Reflection/Assembly.xml @@ -87,11 +87,10 @@ To get an array of objects representing the assemblies that are currently loaded, use the method. - To load assemblies dynamically, the class provides the following static methods. + To load assemblies dynamically, the class provides the following static methods: -- The recommended way to load assemblies is to use the method, which identifies the assembly to be loaded by its display name (for example, "System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"). The search for the assembly follows the rules described in [How the Runtime Locates Assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies). - The and methods enable you to load an assembly for reflection, but not for execution. For example, an assembly that targets a 64-bit platform can be examined by code that is running on a 32-bit platform. -- The and methods are provided for rare scenarios in which an assembly must be identified by path. +- The and methods load assemblies by their path. To get an object for the currently executing assembly, use the method. @@ -4559,7 +4558,6 @@ For bundled assemblies, the value returned is an empty string. ]]> The current assembly is a dynamic assembly, represented by an object. - Shadow Copying Assemblies diff --git a/xml/System.Reflection/Module.xml b/xml/System.Reflection/Module.xml index c2b56fbd5b3..22ce8269670 100644 --- a/xml/System.Reflection/Module.xml +++ b/xml/System.Reflection/Module.xml @@ -83,7 +83,7 @@ - Working with .resx Files Programmatically + Working with .resx files Programmatically diff --git a/xml/System.Runtime.ConstrainedExecution/Cer.xml b/xml/System.Runtime.ConstrainedExecution/Cer.xml index 4d1ecf4f94d..8f11353b84c 100644 --- a/xml/System.Runtime.ConstrainedExecution/Cer.xml +++ b/xml/System.Runtime.ConstrainedExecution/Cer.xml @@ -50,8 +50,6 @@ Specifies a method's behavior when called within a constrained execution region. To be added. - - Reliability Best Practices diff --git a/xml/System.Runtime.ConstrainedExecution/Consistency.xml b/xml/System.Runtime.ConstrainedExecution/Consistency.xml index f6e70abbd5b..6f8e0de7cf0 100644 --- a/xml/System.Runtime.ConstrainedExecution/Consistency.xml +++ b/xml/System.Runtime.ConstrainedExecution/Consistency.xml @@ -50,7 +50,6 @@ Specifies a reliability contract. To be added. - Reliability Best Practices diff --git a/xml/System.Runtime.ConstrainedExecution/CriticalFinalizerObject.xml b/xml/System.Runtime.ConstrainedExecution/CriticalFinalizerObject.xml index bcb930aa879..5be086c1c88 100644 --- a/xml/System.Runtime.ConstrainedExecution/CriticalFinalizerObject.xml +++ b/xml/System.Runtime.ConstrainedExecution/CriticalFinalizerObject.xml @@ -45,10 +45,6 @@ Ensures that all finalization code in derived classes is marked as critical. To be added. - - - - Reliability Best Practices diff --git a/xml/System.Runtime.ConstrainedExecution/PrePrepareMethodAttribute.xml b/xml/System.Runtime.ConstrainedExecution/PrePrepareMethodAttribute.xml index 20a532fea3a..45395792e81 100644 --- a/xml/System.Runtime.ConstrainedExecution/PrePrepareMethodAttribute.xml +++ b/xml/System.Runtime.ConstrainedExecution/PrePrepareMethodAttribute.xml @@ -55,8 +55,6 @@ Instructs the native image generation service to prepare a method for inclusion in a constrained execution region (CER). To be added. - - Reliability Best Practices diff --git a/xml/System.Runtime.ConstrainedExecution/ReliabilityContractAttribute.xml b/xml/System.Runtime.ConstrainedExecution/ReliabilityContractAttribute.xml index 8c6ce30aef5..2e6afcc8c76 100644 --- a/xml/System.Runtime.ConstrainedExecution/ReliabilityContractAttribute.xml +++ b/xml/System.Runtime.ConstrainedExecution/ReliabilityContractAttribute.xml @@ -55,7 +55,6 @@ Defines a contract for reliability between the author of some code, and the developers who have a dependency on that code. To be added. - Reliability Best Practices diff --git a/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml b/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml index 5ae767408ed..cb53bc8c901 100644 --- a/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml +++ b/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml @@ -694,7 +694,7 @@ property affects types to which a attribute has been applied and that also implement the interface. In this case when is `true`, data added in future versions of the contract is ignored on read and write. For more information, see [Forward-Compatible Data Contracts](/dotnet/framework/wcf/feature-details/forward-compatible-data-contracts). + The property affects types to which a attribute has been applied and that also implement the interface. In this case when is `true`, data added in future versions of the contract is ignored on read and write. ]]> @@ -933,7 +933,7 @@ ## Remarks This property can be set using a constructor. For a list, see . - The property specifies the maximum number of objects that the serializer serializes or deserializes in a single or method call. The method always reads one root object, but this object may have other objects in its data members. Those objects may have other objects. The default is . Note that when serializing or deserializing arrays, every array entry counts as a separate object. Also, note that some objects may have a large memory representation, so this quota alone may not be sufficient to prevent Denial of Service attacks. For more information, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). If you need to increase this quota beyond its default value, it is important to do so both on the sending (serializing) and receiving (deserializing) sides. It applies both when reading and writing data. + The property specifies the maximum number of objects that the serializer serializes or deserializes in a single or method call. The method always reads one root object, but this object may have other objects in its data members. Those objects may have other objects. The default is . Note that when serializing or deserializing arrays, every array entry counts as a separate object. Also, note that some objects may have a large memory representation, so this quota alone may not be sufficient to prevent Denial of Service attacks. If you need to increase this quota beyond its default value, it is important to do so both on the sending (serializing) and receiving (deserializing) sides. It applies both when reading and writing data. ]]> diff --git a/xml/System.Runtime.Serialization.Json/JsonReaderWriterFactory.xml b/xml/System.Runtime.Serialization.Json/JsonReaderWriterFactory.xml index 4307f4e4a1c..2fc5a0e35aa 100644 --- a/xml/System.Runtime.Serialization.Json/JsonReaderWriterFactory.xml +++ b/xml/System.Runtime.Serialization.Json/JsonReaderWriterFactory.xml @@ -56,7 +56,7 @@ class can be used to create the necessary XML readers and writers. Note that not every XML Infoset element can be mapped to JSON. For more information about mapping, see [How to: Serialize and Deserialize JSON Data](/dotnet/framework/wcf/feature-details/how-to-serialize-and-deserialize-json-data). + Windows Communication Foundation (WCF) processes JSON messages using a mapping between JSON data and the XML Infoset. Normally, this mapping is hidden from view. However, in some advanced scenarios it may be necessary to manually convert between JSON and XML. In this case, the class can be used to create the necessary XML readers and writers. Note that not every XML Infoset element can be mapped to JSON. ]]> @@ -74,7 +74,7 @@ to prevent Denial of Service (DoS) attacks when reading untrusted data. For more information about using to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). + Each of the overloads uses a to prevent Denial of Service (DoS) attacks when reading untrusted data. ]]> @@ -132,8 +132,6 @@ ## Remarks This overload does not accept an parameter. The character encoding (UTF-8, Unicode or Big-Endian Unicode) is auto-detected when the data is read. - For more information about using to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). - ]]> @@ -190,8 +188,6 @@ ## Remarks This overload does not take an parameter. The character encoding (UTF-8, Unicode or Big-Endian Unicode) is auto-detected when the data is read. - For more information about using to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). - ]]> @@ -252,8 +248,6 @@ ## Remarks This overload does not take an parameter. The character encoding (UTF-8, Unicode or Big-Endian Unicode) is auto-detected when the data is read. - For more information about using to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). - ]]> @@ -323,14 +317,7 @@ The delegate to call when the reader is closed. Creates an that can map streams encoded with JavaScript Object Notation (JSON), of a specified size and offset, to an XML Infoset. An that can read JavaScript Object Notation (JSON). - - to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). - - ]]> - + To be added. @@ -402,14 +389,7 @@ The delegate to call when the reader is closed. The default value is . Creates an that can map buffers encoded with JavaScript Object Notation (JSON), with a specified size and offset and character encoding, to an XML Infoset. An that can read JavaScript Object Notation (JSON). - - to prevent Denial of Service attacks when reading untrusted data, see [Security Considerations for Data](/dotnet/framework/wcf/feature-details/security-considerations-for-data). - - ]]> - + To be added. diff --git a/xml/System.Runtime.Serialization/CollectionDataContractAttribute.xml b/xml/System.Runtime.Serialization/CollectionDataContractAttribute.xml index d2e052c290b..8c751b3b711 100644 --- a/xml/System.Runtime.Serialization/CollectionDataContractAttribute.xml +++ b/xml/System.Runtime.Serialization/CollectionDataContractAttribute.xml @@ -64,10 +64,6 @@ The is also intended to be used with dictionary types to handle keyed collections. Dictionary types are classes that implement either the or the interface, for example, the . Use the and properties to set custom names when using the class. - For more information about using the , see [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). - - - ## Examples The following example applies the to a class that inherits from the class. The code sets the and properties to custom values. diff --git a/xml/System.Runtime.Serialization/ContractNamespaceAttribute.xml b/xml/System.Runtime.Serialization/ContractNamespaceAttribute.xml index db719c4ff26..b89e2730713 100644 --- a/xml/System.Runtime.Serialization/ContractNamespaceAttribute.xml +++ b/xml/System.Runtime.Serialization/ContractNamespaceAttribute.xml @@ -60,7 +60,7 @@ attribute to an assembly that contains types to which the has been applied. The enables you to set a namespace that is different than the one generated when the type is serialized. For more information about how names are generated, see [Data Contract Names](/dotnet/framework/wcf/feature-details/data-contract-names). + Apply the attribute to an assembly that contains types to which the has been applied. The enables you to set a namespace that is different than the one generated when the type is serialized. If you are using a type to conform to an existing data contract, you must match the namespace of the existing contract by using the (or the property of the class). @@ -77,8 +77,6 @@ ]]> - Using Data Contracts - Data Contract Names diff --git a/xml/System.Runtime.Serialization/DataContractAttribute.xml b/xml/System.Runtime.Serialization/DataContractAttribute.xml index 89ea35df2fc..aff73b3e19a 100644 --- a/xml/System.Runtime.Serialization/DataContractAttribute.xml +++ b/xml/System.Runtime.Serialization/DataContractAttribute.xml @@ -59,15 +59,13 @@ attribute to types (classes, structures, or enumerations) that are used in serialization and deserialization operations by the . If you send or receive messages by using the Windows Communication Foundation (WCF) infrastructure, you should also apply the to any classes that hold and manipulate data sent in messages. For more information about data contracts, see [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). +Apply the attribute to types (classes, structures, or enumerations) that are used in serialization and deserialization operations by the . If you send or receive messages by using the Windows Communication Foundation (WCF) infrastructure, you should also apply the to any classes that hold and manipulate data sent in messages. You must also apply the to any field, property, or event that holds values you want to serialize. By applying the , you explicitly enable the to serialize and deserialize the data. > [!CAUTION] > You can apply the to private fields. Be aware that the data returned by the field (even if it is private) is serialized and deserialized, and thus can be viewed or intercepted by a malicious user or process. -For more information about data contracts, see the topics listed in [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). - ## Data contracts A *data contract* is an abstract description of a set of fields with a name and data type for each field. The data contract exists outside of any single implementation to allow services on different platforms to interoperate. As long as the data passed between the services conforms to the same contract, all the services can process the data. This processing is also known as a *loosely coupled system*. A data contract is also similar to an interface in that the contract specifies how data must be delivered so that it can be processed by an application. For example, the data contract may call for a data type named "Person" that has two text fields, named "FirstName" and "LastName". To create a data contract, apply the to the class and apply the to any fields or properties that must be serialized. When serialized, the data conforms to the data contract that is implicitly built into the type. @@ -94,8 +92,6 @@ A data contract has two basic requirements: a stable name and a list of members. A data contract can also accommodate later versions of itself. That is, when a later version of the contract includes extra data, that data is stored and returned to a sender untouched. To do this, implement the interface. -For more information about versioning, see [Data Contract Versioning](/dotnet/framework/wcf/feature-details/data-contract-versioning). - ]]> @@ -112,7 +108,6 @@ The following example serializes and deserializes a class named `Person` to whic - Using Data Contracts @@ -374,7 +369,7 @@ The following example serializes and deserializes a class named `Person` to whic property is used to give a name to a data contract, which is the name of the type in XML schema. For more information, see [Data Contract Names](/dotnet/framework/wcf/feature-details/data-contract-names). + The property is used to give a name to a data contract, which is the name of the type in XML schema. By default, the name of a data contract is the name of the type that the is applied to. However, there may be reasons to change this default name. One reason is to allow an existing type to process data that must conform to an existing data contract. For example, there exists a type named `Person` but the data contract, embodied in an XML schema, requires that the name be `Customer`. The contract can be satisfied by setting the property value to `Customer`. diff --git a/xml/System.Runtime.Serialization/DataContractResolver.xml b/xml/System.Runtime.Serialization/DataContractResolver.xml index e6773e0cad4..e31b6e29b69 100644 --- a/xml/System.Runtime.Serialization/DataContractResolver.xml +++ b/xml/System.Runtime.Serialization/DataContractResolver.xml @@ -55,15 +55,13 @@ [!WARNING] -> Only use if you are completely sure of what information is being serialized. Malicious types can cause unexpected behavior. - - +> Only use if you are completely sure of what information is being serialized. Malicious types can cause unexpected behavior. ## Examples - The following example shows how to derive a class from . For a working sample, see [DataContractResolver](/dotnet/framework/wcf/samples/datacontractresolver). + The following example shows how to derive a class from . :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/datacontractresolver/cs/datacontractresolver.cs" id="Snippet2"::: diff --git a/xml/System.Runtime.Serialization/DataContractSerializer.xml b/xml/System.Runtime.Serialization/DataContractSerializer.xml index 05f0567db96..b3c41310cce 100644 --- a/xml/System.Runtime.Serialization/DataContractSerializer.xml +++ b/xml/System.Runtime.Serialization/DataContractSerializer.xml @@ -61,10 +61,6 @@ For a list of types that can be serialized, see [Types Supported by the Data Con To use the , first create an instance of a class and an object appropriate to writing or reading the format; for example, an instance of the . Then call the method to persist the data. To retrieve data, create an object appropriate to reading the data format (such as an for an XML document) and call the method. -For more information about using the , see [Serialization and Deserialization](/dotnet/framework/wcf/feature-details/serialization-and-deserialization). - -You can set the type of a data contract serializer using the [<dataContractSerializer>](/dotnet/framework/configure-apps/file-schema/wcf/datacontractserializer-element) element in a client application configuration file. - ## Prepare classes for serialization or deserialization The is used in combination with the and classes. To prepare a class for serialization, apply the to the class. For each member of the class that returns data that you want to serialize, apply the . You can serialize fields and properties, regardless of accessibility: private, protected, internal, protected internal, or public. @@ -83,11 +79,11 @@ If you are creating a class that has fields or properties that must be populated When serializing or deserializing an object, it is required that the type is "known" to the . Begin by creating an instance of a class that implements (such as ) and adding the known types to the collection. Then create an instance of the using one of the overloads that takes the (for example, ). > [!NOTE] -> Unlike other primitive types, the structure is not a known type by default, so it must be manually added to the list of known types (see [Data Contract Known Types](/dotnet/framework/wcf/feature-details/data-contract-known-types)). +> Unlike other primitive types, the structure is not a known type by default, so it must be manually added to the list of known types. ## Forward compatibility -The understands data contracts that have been designed to be compatible with future versions of the contract. Such types implement the interface. The interface features the property that returns an object. For more information, see [Forward-Compatible Data Contracts](/dotnet/framework/wcf/feature-details/forward-compatible-data-contracts). +The understands data contracts that have been designed to be compatible with future versions of the contract. Such types implement the interface. The interface features the property that returns an object. ]]> @@ -96,8 +92,6 @@ The understands data - Using Data Contracts - Serialization and Deserialization @@ -624,7 +618,7 @@ The understands data property is used when the class to which a has been applied also implements the interface. In this case, the data added in a future version of the contract is ignored on read and write. For more information, see [Forward-Compatible Data Contracts](/dotnet/framework/wcf/feature-details/forward-compatible-data-contracts). + The property is used when the class to which a has been applied also implements the interface. In this case, the data added in a future version of the contract is ignored on read and write. ]]> @@ -632,7 +626,6 @@ The understands data - Forward Compatible Data Contracts diff --git a/xml/System.Runtime.Serialization/DataMemberAttribute.xml b/xml/System.Runtime.Serialization/DataMemberAttribute.xml index 49d2022dacc..8c65947a821 100644 --- a/xml/System.Runtime.Serialization/DataMemberAttribute.xml +++ b/xml/System.Runtime.Serialization/DataMemberAttribute.xml @@ -72,8 +72,6 @@ > [!NOTE] > Properties to which the attribute has been applied must have both `get` and `set` fields. They cannot be `get`-only or `set`-only. To serialize a property that should remain `get`-only by design (for example, a property that returns a collection), consider applying the to the backing field instead. - For more information about data contracts and data members, see [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). For more information about member names, see [Data Member Default Values](/dotnet/framework/wcf/feature-details/data-member-default-values). - ## Examples The following example shows a type to which the and attributes have been applied. The property on the is set to "ID". @@ -85,10 +83,6 @@ - Using Data Contracts - Best Practices: Data Contract Versioning - Data Member Default Values - Data Member Order @@ -274,13 +268,11 @@ the member is not present. - Data Contract Versioning - Best Practices: Data Contract Versioning @@ -333,9 +325,6 @@ ]]> - Using Data Contracts - Data Contract Names - Data Contract Versioning @@ -381,11 +370,9 @@ - Data Member Order diff --git a/xml/System.Runtime.Serialization/ExportOptions.xml b/xml/System.Runtime.Serialization/ExportOptions.xml index a6593e37759..133764bc756 100644 --- a/xml/System.Runtime.Serialization/ExportOptions.xml +++ b/xml/System.Runtime.Serialization/ExportOptions.xml @@ -56,13 +56,7 @@ ## Remarks The is used to generate XSD schemas from a type or assembly. You can also use the to generate .NET code from a schema document. - For more information about importing and exporting schemas, see [Schema Import and Export](/dotnet/framework/wcf/feature-details/schema-import-and-export) and [Exporting Schemas from Classes](/dotnet/framework/wcf/feature-details/exporting-schemas-from-classes). - - The property is used by the to include types that can be read in an object graph. For more information about the data contract and known types, see [Data Contract Known Types](/dotnet/framework/wcf/feature-details/data-contract-known-types). - - For more information about data contracts, see [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). - - + The property is used by the to include types that can be read in an object graph. ## Examples The following example creates an instance of the class and adds a type (`Possessions`) to the collection returned by the property. @@ -77,11 +71,6 @@ - Schema Import and Export - Importing Schema To Generate Classes - Exporting Schemas From Classes - Data Contract Known Types - Using Data Contracts @@ -205,10 +194,6 @@ ## Remarks The property is used by the to include types that can be read in an object graph (set using the property). - For more information about the data contract and known types, see [Data Contract Known Types](/dotnet/framework/wcf/feature-details/data-contract-known-types). - - - ## Examples The following example creates an instance of the class and adds a type to the collection returned by the property. @@ -218,7 +203,6 @@ ]]> - Data Contract Known Types diff --git a/xml/System.Runtime.Serialization/ExtensionDataObject.xml b/xml/System.Runtime.Serialization/ExtensionDataObject.xml index bbae92ae7fa..322234d096f 100644 --- a/xml/System.Runtime.Serialization/ExtensionDataObject.xml +++ b/xml/System.Runtime.Serialization/ExtensionDataObject.xml @@ -64,7 +64,6 @@ - Using Data Contracts diff --git a/xml/System.Runtime.Serialization/IExtensibleDataObject.xml b/xml/System.Runtime.Serialization/IExtensibleDataObject.xml index 65265159ea0..9fb6cf9e510 100644 --- a/xml/System.Runtime.Serialization/IExtensibleDataObject.xml +++ b/xml/System.Runtime.Serialization/IExtensibleDataObject.xml @@ -59,8 +59,6 @@ The interface provides 5. Apply the attribute to the class. Set the and properties to appropriate values if necessary. -For more information about versioning of types, see [Data Contract Versioning](/dotnet/framework/wcf/feature-details/data-contract-versioning). For information about creating forward-compatible data contracts, see [Forward-Compatible Data Contracts](/dotnet/framework/wcf/feature-details/forward-compatible-data-contracts). For more information about data contracts, see [Using Data Contracts](/dotnet/framework/wcf/feature-details/using-data-contracts). - ]]> @@ -72,8 +70,6 @@ The following code shows an instance of a type (`PersonVersion2`) that is the se ]]> - Data Contract Versioning - Using Data Contracts diff --git a/xml/System.Runtime.Serialization/IgnoreDataMemberAttribute.xml b/xml/System.Runtime.Serialization/IgnoreDataMemberAttribute.xml index 3419a8f0694..cad8ccd34fc 100644 --- a/xml/System.Runtime.Serialization/IgnoreDataMemberAttribute.xml +++ b/xml/System.Runtime.Serialization/IgnoreDataMemberAttribute.xml @@ -53,17 +53,15 @@ When applied to the member of a type, specifies that the member is not part of a data contract and is not serialized. - attribute to opt-out of the default behavior. By default, the `DataContractSerializer` serializes all publicly visible types. All public read/write properties and fields of the type are serialized. You can change the default behavior by applying the and attributes to the types and members - + attribute to opt-out of the default behavior. By default, the `DataContractSerializer` serializes all publicly visible types. All public read/write properties and fields of the type are serialized. You can change the default behavior by applying the and attributes to the types and members + ]]> - Serializable Types - Types Supported by the Data Contract Serializer diff --git a/xml/System.Runtime.Serialization/ImportOptions.xml b/xml/System.Runtime.Serialization/ImportOptions.xml index aa22d42f366..94753969892 100644 --- a/xml/System.Runtime.Serialization/ImportOptions.xml +++ b/xml/System.Runtime.Serialization/ImportOptions.xml @@ -41,8 +41,6 @@ - Schema Import and Export - Importing Schema To Generate Classes diff --git a/xml/System.Runtime.Serialization/InvalidDataContractException.xml b/xml/System.Runtime.Serialization/InvalidDataContractException.xml index 4d9b84d2871..66bfb6a07a1 100644 --- a/xml/System.Runtime.Serialization/InvalidDataContractException.xml +++ b/xml/System.Runtime.Serialization/InvalidDataContractException.xml @@ -83,7 +83,6 @@ ]]> - Using Data Contracts diff --git a/xml/System.Runtime.Serialization/KnownTypeAttribute.xml b/xml/System.Runtime.Serialization/KnownTypeAttribute.xml index 45f3405222a..e8080d18e6b 100644 --- a/xml/System.Runtime.Serialization/KnownTypeAttribute.xml +++ b/xml/System.Runtime.Serialization/KnownTypeAttribute.xml @@ -80,7 +80,6 @@ - Data Contract Known Types diff --git a/xml/System.Runtime.Serialization/XPathQueryGenerator.xml b/xml/System.Runtime.Serialization/XPathQueryGenerator.xml index 8b05696e0fa..884e24a45c3 100644 --- a/xml/System.Runtime.Serialization/XPathQueryGenerator.xml +++ b/xml/System.Runtime.Serialization/XPathQueryGenerator.xml @@ -53,22 +53,19 @@ and as appropriate to the type and its fields or properties. +1. Create the data contract type by applying the and as appropriate to the type and its fields or properties. -2. Use the method of the class to generate the MemberInfo array. +2. Use the method of the class to generate the MemberInfo array. -3. Pass the type and the array to the method. +3. Pass the type and the array to the method. -4. If needed, use the returned by the `namespaces` parameter to examine the XML namespaces referenced by the namespaces prefixes in the XPath query. +4. If needed, use the returned by the `namespaces` parameter to examine the XML namespaces referenced by the namespaces prefixes in the XPath query. > [!NOTE] -> The namespace prefix "xg" (for "XPath Generator") is used as the default in the XPath. This cannot be changed. Instead, refer to the NameTable collection to see what namespace the prefix is associated with. - - +> The namespace prefix "xg" (for "XPath Generator") is used as the default in the XPath. This cannot be changed. Instead, refer to the NameTable collection to see what namespace the prefix is associated with. ## Examples The following example creates XPath queries from two classes to which the and attributes have been applied. @@ -151,11 +148,6 @@ and attributes have been applied. diff --git a/xml/System.Runtime.Serialization/XmlObjectSerializer.xml b/xml/System.Runtime.Serialization/XmlObjectSerializer.xml index ee6af2e0096..51f91cceaeb 100644 --- a/xml/System.Runtime.Serialization/XmlObjectSerializer.xml +++ b/xml/System.Runtime.Serialization/XmlObjectSerializer.xml @@ -72,8 +72,6 @@ When you inherit from , you must override the following members: , , . Additionally, the and methods must be implemented for reading and deserializing. - Using Data Contracts - Data Contract Serializer diff --git a/xml/System.Runtime.Serialization/XsdDataContractExporter.xml b/xml/System.Runtime.Serialization/XsdDataContractExporter.xml index 55b69929a99..9499c68613d 100644 --- a/xml/System.Runtime.Serialization/XsdDataContractExporter.xml +++ b/xml/System.Runtime.Serialization/XsdDataContractExporter.xml @@ -90,8 +90,6 @@ The following example creates an instance of the - Types Supported by the Data Contract Serializer - Serialization and Deserialization diff --git a/xml/System.Runtime.Serialization/XsdDataContractImporter.xml b/xml/System.Runtime.Serialization/XsdDataContractImporter.xml index 62929c86d81..bf92f476082 100644 --- a/xml/System.Runtime.Serialization/XsdDataContractImporter.xml +++ b/xml/System.Runtime.Serialization/XsdDataContractImporter.xml @@ -40,14 +40,12 @@ Web service, or to create data contract types from XML schemas. will transform a set of XML schemas and create the .NET Framework types that represent the data contract in a selected programming language. To create the code, use the classes in the namespace. - + Conversely, use the class when you have created a Web service that incorporates data represented by CLR types and when you need to export XML schemas for each data type to be consumed by other Web services.That is, transforms a set of CLR types into a set of XML schemas. - Using Data Contracts - Types Supported by the Data Contract Serializer @@ -537,7 +535,6 @@ ]]> - Data Contract Known Types diff --git a/xml/System.Security.Authentication.ExtendedProtection/ChannelBinding.xml b/xml/System.Security.Authentication.ExtendedProtection/ChannelBinding.xml index bb5818450b5..858903385e3 100644 --- a/xml/System.Security.Authentication.ExtendedProtection/ChannelBinding.xml +++ b/xml/System.Security.Authentication.ExtendedProtection/ChannelBinding.xml @@ -60,7 +60,6 @@ ]]> - Integrated Windows Authentication with Extended Protection diff --git a/xml/System.Security.Permissions/ReflectionPermission.xml b/xml/System.Security.Permissions/ReflectionPermission.xml index 6967a8a092b..a5b41133965 100644 --- a/xml/System.Security.Permissions/ReflectionPermission.xml +++ b/xml/System.Security.Permissions/ReflectionPermission.xml @@ -53,10 +53,6 @@ ]]> - - - Security Considerations for Reflection - Security Issues in Reflection Emit diff --git a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml index 8f900a448c6..fadf4d201f6 100644 --- a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml +++ b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml @@ -53,11 +53,6 @@ ]]> - - - Extending Metadata Using Attributes - Security Issues in Reflection Emit - Security Considerations for Reflection @@ -288,8 +283,6 @@ if restricted invocation of non-public members is allowed; otherwise, . To be added. - Security Issues in Reflection Emit - Security Considerations for Reflection diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml index 3d1903319bc..35aa1e87989 100644 --- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml +++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml @@ -54,8 +54,6 @@ - Security Considerations for Reflection - Security Issues in Reflection Emit diff --git a/xml/System.Security/CodeAccessPermission.xml b/xml/System.Security/CodeAccessPermission.xml index b765b83d389..40f4767badd 100644 --- a/xml/System.Security/CodeAccessPermission.xml +++ b/xml/System.Security/CodeAccessPermission.xml @@ -135,7 +135,7 @@ -or- There is already an active for the current frame. - Using the Assert Method + You cannot override this method. diff --git a/xml/System.Security/IStackWalk.xml b/xml/System.Security/IStackWalk.xml index 3129a7302d8..b5c772c41e5 100644 --- a/xml/System.Security/IStackWalk.xml +++ b/xml/System.Security/IStackWalk.xml @@ -128,7 +128,6 @@ Asserts that the calling code can access the resource identified by the current permission object, even if callers higher in the stack have not been granted permission to access the resource. To be added. The calling code does not have . - Using the Assert Method diff --git a/xml/System.Security/PermissionSet.xml b/xml/System.Security/PermissionSet.xml index af75842e928..93c54d2ee0e 100644 --- a/xml/System.Security/PermissionSet.xml +++ b/xml/System.Security/PermissionSet.xml @@ -375,7 +375,6 @@ -or- There is already an active for the current frame. - Using the Assert Method diff --git a/xml/System/Activator.xml b/xml/System/Activator.xml index cbf3e46a758..abc6fe456c4 100644 --- a/xml/System/Activator.xml +++ b/xml/System/Activator.xml @@ -171,9 +171,6 @@ ## Remarks The constructor to be invoked must be accessible. -> [!NOTE] -> This method can be used to access nonpublic types if the caller has been granted with the flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).) - ## Examples The following code example demonstrates how to call the method. Instances of several different types are created and their default values are displayed. diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml index 68a480c983a..d58b9b72ea5 100644 --- a/xml/System/AppDomain.xml +++ b/xml/System/AppDomain.xml @@ -530,7 +530,6 @@ The To be added. The operation is attempted on an unloaded application domain. - Shadow Copying Assemblies @@ -2675,25 +2674,6 @@ 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). - - 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. - - When the last `Worker` object handles the exception, the event is raised only in the last application domain. The other application domains never get a chance to handle the exception, so the event is not raised. - - When the last `Worker` object does not handle the exception, 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. - - :::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"::: - :::code language="vb" source="~/snippets/visualbasic/System/AppDomain/FirstChanceException/example.vb" id="Snippet1"::: - ]]> @@ -4352,7 +4332,6 @@ The To be added. The operation is attempted on an unloaded application domain. - Shadow Copying Assemblies @@ -4635,7 +4614,6 @@ The Turns on shadow copying. To be added. The operation is attempted on an unloaded application domain. - Shadow Copying Assemblies @@ -4700,7 +4678,6 @@ The Establishes the specified directory path as the location of assemblies to be shadow copied. To be added. The operation is attempted on an unloaded application domain. - Shadow Copying Assemblies @@ -4853,17 +4830,9 @@ The Gets an indication 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/IAsyncResult.xml b/xml/System/IAsyncResult.xml index 33cd5a1769a..75a8b08edd3 100644 --- a/xml/System/IAsyncResult.xml +++ b/xml/System/IAsyncResult.xml @@ -280,7 +280,7 @@ ]]> - Most implementers of the interface will not use this property and should return . A task that is created with the method will not complete if this property is not implemented correctly. See Application Compatibility in 4.5. + Most implementers of the interface will not use this property and should return . A task that's created with the method will not complete if this property is not implemented correctly. Use this property to determine if the asynchronous operation completed synchronously. For example, this property can return for an asynchronous I/O operation if the I/O request was small. diff --git a/xml/System/Lazy`1.xml b/xml/System/Lazy`1.xml index a01365a2ca7..9ec30b32c73 100644 --- a/xml/System/Lazy`1.xml +++ b/xml/System/Lazy`1.xml @@ -81,7 +81,7 @@ - Will the lazily initialized object be accessed from more than one thread? If so, the object might create it on any thread. You can use one of the simple constructors whose default behavior is to create a thread-safe object, so that only one instance of the lazily instantiated object is created no matter how many threads try to access it. To create a object that is not thread safe, you must use a constructor that enables you to specify no thread safety. > [!CAUTION] - > Making the object thread safe does not protect the lazily initialized object. If multiple threads can access the lazily initialized object, you must make its properties and methods safe for multithreaded access. + > Making the object thread safe does not protect the lazily initialized object. If multiple threads can access the lazily initialized object, you must make its properties and methods safe for multithreaded access. - Does lazy initialization require a lot of code, or does the lazily initialized object have a parameterless constructor that does everything you need and doesn't throw exceptions? If you need to write initialization code or if exceptions need to be handled, use one of the constructors that takes a factory method. Write your initialization code in the factory method. @@ -99,7 +99,7 @@ **Alternative to locking** In certain situations, you might want to avoid the overhead of the object's default locking behavior. In rare situations, there might be a potential for deadlocks. In such cases, you can use the or constructor, and specify . This enables the object to create a copy of the lazily initialized object on each of several threads if the threads call the property simultaneously. The object ensures that all threads use the same instance of the lazily initialized object and discards the instances that are not used. Thus, the cost of reducing the locking overhead is that your program might sometimes create and discard extra copies of an expensive object. In most cases, this is unlikely. The examples for the and constructors demonstrate this behavior. > [!IMPORTANT] -> When you specify , exceptions are never cached, even if you specify a factory method. +> When you specify , exceptions are never cached, even if you specify a factory method. **Equivalent constructors** In addition to enabling the use of , the and constructors can duplicate the functionality of the other constructors. The following table shows the parameter values that produce equivalent behavior. @@ -111,15 +111,13 @@ **Other capabilities** For information about the use of with thread-static fields, or as the backing store for properties, see [Lazy Initialization](/dotnet/framework/performance/lazy-initialization). - - ## Examples The following example demonstrates the use of the class to provide lazy initialization with access from multiple threads. > [!NOTE] -> The example uses the constructor. It also demonstrates the use of the constructor (specifying `true` for `isThreadSafe`) and the constructor (specifying for `mode`). To switch to a different constructor, just change which constructors are commented out. +> The example uses the constructor. It also demonstrates the use of the constructor (specifying `true` for `isThreadSafe`) and the constructor (specifying for `mode`). To switch to a different constructor, just change which constructors are commented out. > -> For an example that demonstrates exception caching using the same constructors, see the constructor. +> For an example that demonstrates exception caching using the same constructors, see the constructor. The example defines a `LargeObject` class that will be initialized lazily by one of several threads. The four key sections of code illustrate the creation of the initializer, the factory method, the actual initialization, and the constructor of the `LargeObject` class, which displays a message when the object is created. At the beginning of the `Main` method, the example creates the thread-safe lazy initializer for `LargeObject`: @@ -152,7 +150,7 @@ :::code language="vb" source="~/snippets/visualbasic/System/LazyT/Overview/example.vb" id="Snippetlargector"::: > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/Overview/example.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/Overview/example.fs" id="Snippetall"::: @@ -241,7 +239,7 @@ The class provides locking, so that only one thread is allowed to create the `LargeObject` instance. The example demonstrates that the other threads all get the same instance. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example.cs" id="Snippetall"::: :::code language="vb" source="~/snippets/visualbasic/System/LazyT/.ctor/example.vb" id="Snippetall"::: @@ -304,12 +302,12 @@ The following example demonstrates the use of this constructor to create a lazy initializer that is not thread safe, for scenarios where all access to the lazily initialized object occurs on the same thread. It also demonstrates the use of the constructor (specifying for `mode`. To switch to a different constructor, just change which constructor is commented out. > [!NOTE] -> For code that demonstrates how to use this constructor in multithreaded scenarios (specifying `true` for `isThreadSafe`), see the example for the constructor. +> For code that demonstrates how to use this constructor in multithreaded scenarios (specifying `true` for `isThreadSafe`), see the example for the constructor. The example defines a `LargeObject` class that will be initialized lazily. In the `Main` method, the example creates a instance and then pauses. When you press the **Enter** key, the example accesses the property of the instance, which causes initialization to occur. The constructor of the `LargeObject` class displays a console message. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example1.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/.ctor/example1.fs" id="Snippetall"::: @@ -394,7 +392,7 @@ When the example is run, the first thread that tries to create an instance of `LargeObject` fails, and the exception is caught. You might expect that the next thread would successfully create an instance, but the object has cached the exception. Because of this, all three threads throw the exception. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example2.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/.ctor/example2.fs" id="Snippetall"::: @@ -459,7 +457,7 @@ The following example demonstrates the use of this constructor to create a lazy initializer that enables multiple threads to race to create an object lazily. Multiple threads might succeed in creating instances, but all threads use the instance that was created first. > [!NOTE] -> For an example that demonstrates how to use this constructor in single-threaded scenarios (specifying for `mode`), see the constructor. For an example that demonstrates how to use this constructor to provide locking instead of race conditions in multithreaded scenarios (specifying for `mode`), see the constructor. +> For an example that demonstrates how to use this constructor in single-threaded scenarios (specifying for `mode`), see the constructor. For an example that demonstrates how to use this constructor to provide locking instead of race conditions in multithreaded scenarios (specifying for `mode`), see the constructor. The example defines a `LargeObject` class that will be initialized lazily by any of several threads. The three key sections of code illustrate the creation of the initializer, the actual initialization, and the constructor and finalizer of the `LargeObject` class. At the beginning of the `Main` method, the example creates the object that performs lazy initialization of the `LargeObject`: @@ -482,7 +480,7 @@ However, the object ensures that only one instance is used by all threads. The output from the example shows that all three threads use the same instance, and also shows that the other two instances can be reclaimed by garbage collection. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example5.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/.ctor/example5.fs" id="Snippetall"::: @@ -592,7 +590,7 @@ An instance created with this constructor is usable by multiple threads concurre The following example demonstrates the use of this constructor to provide lazy initialization with exception caching, in a scenario with a single thread. It also demonstrates the use of the constructor (specifying for `mode`). To switch to that constructor, just change which constructor is commented out. > [!NOTE] -> For code that demonstrates how to use this constructor in multithreaded scenarios (specifying `true` for `isThreadSafe`), see the example for the constructor. +> For code that demonstrates how to use this constructor in multithreaded scenarios (specifying `true` for `isThreadSafe`), see the example for the constructor. The example defines a `LargeObject` class that will be initialized lazily by one of several threads. The three key sections of code illustrate the creation of the initializer, the actual initialization, and the constructor of the `LargeObject` class, which demonstrates exception caching. At the beginning of the `Main` method, the example creates the thread-safe lazy initializer for `LargeObject`: @@ -615,7 +613,7 @@ An instance created with this constructor is usable by multiple threads concurre When the example is run, the first attempt to create an instance of `LargeObject` fails, and the exception is caught. You might expect that the next attempt would succeed, but the object has cached the exception. Because of this, all three attempts throw the exception. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example3.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/.ctor/example3.fs" id="Snippetall"::: @@ -682,7 +680,7 @@ An instance created with this constructor is usable by multiple threads concurre The following example demonstrates the use of this constructor to create a lazy initializer that enables multiple threads to race to create an object lazily. Multiple threads might succeed in creating instances, but all threads use the instance that was created first. In addition, the example demonstrates that exceptions are never cached when you specify , even if initialization is performed by a function instead of by the parameterless constructor of the lazily created type. > [!NOTE] -> For an example that demonstrates how to use this constructor in single-threaded scenarios (specifying for `mode`), see the constructor. For an example that demonstrates how to use this constructor to provide locking instead of race conditions in multithreaded scenarios (specifying for `mode`), see the constructor. +> For an example that demonstrates how to use this constructor in single-threaded scenarios (specifying for `mode`), see the constructor. For an example that demonstrates how to use this constructor to provide locking instead of race conditions in multithreaded scenarios (specifying for `mode`), see the constructor. The example defines a `LargeObject` class that will be initialized lazily by any of several threads. The four key sections of code illustrate the creation of the initializer, the actual initialization, the initialization function, and the constructor and finalizer of the `LargeObject` class. At the beginning of the `Main` method, the example creates the object that performs lazy initialization of the `LargeObject`: @@ -707,7 +705,7 @@ An instance created with this constructor is usable by multiple threads concurre With any other setting, an unhandled exception in the initialization function would be cached. However, suppresses exception caching. The output from the example demonstrates that a subsequent attempt to initialize the object succeeds. > [!NOTE] -> The exception message usually appears after messages indicating that other threads have successfully initialized the object. This is because of the delay introduced by throwing and catching the exception. +> The exception message usually appears after messages indicating that other threads have successfully initialized the object. This is because of the delay introduced by throwing and catching the exception. Because the constructor for the instance specified , all three threads are allowed to create `LargeObject` instances. The example demonstrates this by displaying console messages in the constructor and in the finalizer of the `LargeObject` class: @@ -718,7 +716,7 @@ An instance created with this constructor is usable by multiple threads concurre The object ensures that only one instance is used by all threads (except the thread where the initialization function throws an exception). The output from the example shows this. > [!NOTE] -> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. +> For simplicity, this example uses a global instance of , and all the methods are `static` (`Shared` in Visual Basic). These are not requirements for the use of lazy initialization. :::code language="csharp" source="~/snippets/csharp/System/LazyT/.ctor/example4.cs" id="Snippetall"::: :::code language="fsharp" source="~/snippets/fsharp/System/LazyT/.ctor/example4.fs" id="Snippetall"::: diff --git a/xml/System/Uri.xml b/xml/System/Uri.xml index c7f7e87617c..00f38e702ce 100644 --- a/xml/System/Uri.xml +++ b/xml/System/Uri.xml @@ -226,8 +226,7 @@ The following code snippet shows example values of the various properties on the - Changes to the System.Uri namespace in Version 2.0 - International Resource Identifier Support in System.UriSystem.Uri + International Resource Identifier Support in System.Uri