Remove BinaryFormatter snippets and articles (dotnet#33122)

.openpublishing.redirection.framework.json

@@ -1685,6 +1685,10 @@
             "source_path_from_root": "/docs/framework/wcf/feature-details/context-exchange-correlation.md",
             "redirect_url": "/previous-versions/dotnet/netframework-4.0/ee358724(v=vs.100)"
         },
+        {
+            "source_path_from_root": "/docs/framework/wcf/feature-details/controlling-serialization-and-deserialization-with-serializationbinder.md",
+            "redirect_url": "/dotnet/framework/wcf/feature-details/data-transfer-and-serialization"
+        },
         {
             "source_path_from_root": "/docs/framework/wcf/feature-details/how-to-create-a-workflow-service-that-calls-another-workflow-service.md",
             "redirect_url": "/previous-versions/dotnet/netframework-4.0/ff729672(v=vs.100)"
@@ -1798,6 +1802,10 @@
             "source_path_from_root": "/docs/framework/wcf/samples/transacted-batching.md",
             "redirect_url": "/previous-versions/dotnet/netframework-4.0/aa395219(v%3dvs.100)"
         },
+        {
+            "source_path_from_root": "/docs/framework/wcf/samples/usage-of-serialization-binder.md",
+            "redirect_url": "/dotnet/framework/wcf/samples/"
+        },
         {
             "source_path_from_root": "/docs/framework/wcf/samples/web-extensibility.md",
             "redirect_url": "/previous-versions/dotnet/netframework-4.0/ee818234(v%3dvs.100)"

.openpublishing.redirection.standard.json

@@ -507,6 +507,10 @@
             "source_path_from_root": "/docs/standard/guidance-architecture.md",
             "redirect_url": "/dotnet/architecture/index"
         },
+        {
+            "source_path_from_root": "/docs/standard/serialization/how-to-determine-if-netstandard-object-is-serializable.md",
+            "redirect_url": "/dotnet/standard/serialization/binaryformatter-security-guide"
+        },
         {
             "source_path_from_root": "/docs/standard/index.yml",
             "redirect_url": "/dotnet/fundamentals/"

.openpublishing.redirection.visual-basic.json

@@ -1259,6 +1259,10 @@
             "source_path_from_root": "/docs/visual-basic/programming-guide/concepts/threading/walkthrough-multithreading-with-the-backgroundworker-component.md",
             "redirect_url": "/dotnet/api/system.componentmodel.backgroundworker"
         },
+        {
+            "source_path_from_root": "/docs/visual-basic/programming-guide/concepts/serialization/walkthrough-persisting-an-object-in-visual-studio.md",
+            "redirect_url": "/dotnet/visual-basic/programming-guide/concepts/serialization/"
+        },
         {
             "source_path_from_root": "/docs/visual-basic/programming-guide/language-features/xml/how-to-enable-xml-intellisense.md",
             "redirect_url": "/previous-versions/visualstudio/visual-studio-2013/bb531402(v=vs.120)"

docs/framework/wcf/feature-details/importing-schema-to-generate-classes.md

@@ -75,7 +75,7 @@ To generate classes from schemas that are usable with Windows Communication Foun
 
  This corresponds to the **/serializable** switch on the `Svcutil.exe` tool.  
 
- Sometimes it is important for the types generated from the schema to be usable with .NET Framework runtime serialization engines (for example, the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter?displayProperty=nameWithType> and the <xref:System.Runtime.Serialization.Formatters.Soap.SoapFormatter> classes). This is useful when using types for .NET Framework remoting. To enable this, you must apply the <xref:System.SerializableAttribute> attribute to the generated types in addition to the regular <xref:System.Runtime.Serialization.DataContractAttribute> attribute. The attribute is generated automatically if the `GenerateSerializable` import option is set to `true`.  
+ Sometimes it is important for the types generated from the schema to be usable with .NET Framework runtime serialization engines. This is useful when using types for .NET Framework remoting. To enable this, you must apply the <xref:System.SerializableAttribute> attribute to the generated types in addition to the regular <xref:System.Runtime.Serialization.DataContractAttribute> attribute. The attribute is generated automatically if the `GenerateSerializable` import option is set to `true`.  
 
  The following example shows the `Vehicle` class generated with the `GenerateSerializable` import option set to `true`.  
 

docs/framework/wcf/feature-details/toc.yml

@@ -1,3 +1,4 @@
+items:
 - name: WCF Feature Details
   href: index.md
   items:
@@ -159,8 +160,6 @@
           href: importing-schema-to-generate-classes.md
         - name: Exporting Schemas from Classes
           href: exporting-schemas-from-classes.md
-        - name: Controlling Serialization and Deserialization with SerializationBinder
-          href: controlling-serialization-and-deserialization-with-serializationbinder.md
       - name: Using a Data Contract Resolver
         href: using-a-data-contract-resolver.md
     - name: Using the XmlSerializer Class

docs/framework/wcf/feature-details/version-tolerant-serialization-callbacks.md

@@ -21,12 +21,12 @@ The data contract programming model fully supports the version-tolerant serializ
 
  There are four callback attributes. Each attribute can be applied to a method that the serialization/deserialization engine calls at various times. The table below explains when to use each attribute.  
 
-|Attribute|When the corresponding method is called|  
-|---------------|---------------------------------------------|  
-|<xref:System.Runtime.Serialization.OnSerializingAttribute>|Called before serializing the type.|  
-|<xref:System.Runtime.Serialization.OnSerializedAttribute>|Called after serializing the type.|  
-|<xref:System.Runtime.Serialization.OnDeserializingAttribute>|Called before deserializing the type.|  
-|<xref:System.Runtime.Serialization.OnDeserializedAttribute>|Called after deserializing the type.|  
+| Attribute                                                    | When the corresponding method is called |
+| ------------------------------------------------------------ | --------------------------------------- |
+| <xref:System.Runtime.Serialization.OnSerializingAttribute>   | Called before serializing the type.     |
+| <xref:System.Runtime.Serialization.OnSerializedAttribute>    | Called after serializing the type.      |
+| <xref:System.Runtime.Serialization.OnDeserializingAttribute> | Called before deserializing the type.   |
+| <xref:System.Runtime.Serialization.OnDeserializedAttribute>  | Called after deserializing the type.    |
 
  The methods must accept a <xref:System.Runtime.Serialization.StreamingContext> parameter.  
 

docs/framework/wcf/samples/data-contracts.md

@@ -24,6 +24,3 @@ Demonstrates how to pass objects by references between server and client.
 
  [POCO Support](poco-support.md)
 Demonstrates the serialization support for unmarked types; that is, types to which serialization attributes have not been applied, sometimes referred to as Plain Old CLR Object (POCO) types.
-
- [Usage of Serialization Binder](usage-of-serialization-binder.md)
-This sample shows how to use the <xref:System.Runtime.Serialization.SerializationBinder> to change the version of a generic type when it is serialized.

docs/framework/wcf/samples/toc.yml

@@ -1,3 +1,4 @@
+items:
 - name: Windows Communication Foundation Samples
   href: index.md
   items:
@@ -175,8 +176,6 @@
           href: object-references.md
         - name: POCO Support
           href: poco-support.md
-        - name: Usage of Serialization Binder
-          href: usage-of-serialization-binder.md
       - name: Message Contracts
         href: message-contracts.md
         items:

docs/framework/windows-workflow-foundation/performance.md

@@ -42,7 +42,7 @@ ms.assetid: 67d2b3e8-3777-49f8-9084-abbb33b5a766
 
 ### Control Flow
 
- Just as in any programming language, WF provides support for control flows for workflow definitions by introducing a set of control flow activities for sequencing, looping, branching and other patterns. In WF3, when the same activity needs to be re-executed, a new <xref:System.Workflow.ComponentModel.ActivityExecutionContext> is created and the activity is cloned through a heavy-weight serialization and deserialization logic based on <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>. Usually the performance for iterative control flows is much slower than executing a sequence of activities.
+ Just as in any programming language, WF provides support for control flows for workflow definitions by introducing a set of control flow activities for sequencing, looping, branching, and other patterns. In WF3, when the same activity needs to be re-executed, a new <xref:System.Workflow.ComponentModel.ActivityExecutionContext> is created and the activity is cloned through a heavy-weight serialization and deserialization logic based on <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>. Usually the performance for iterative control flows is much slower than executing a sequence of activities.
 
  WF4 handles this quite differently. It takes the activity template, creates a new ActivityInstance object, and adds it to the scheduler queue. This whole process only involves explicit object creation and is very lightweight.
 

docs/fundamentals/code-analysis/quality-rules/ca2305.md

@@ -34,7 +34,7 @@ This rule finds <xref:System.Web.UI.LosFormatter?displayProperty=nameWithType> d
 
 ## How to fix violations
 
-- Use a secure serializer instead, and **don't allow an attacker to specify an arbitrary type to deserialize**. For more information see the [Preferred alternatives](../../../standard/serialization/binaryformatter-security-guide.md#preferred-alternatives).
+- Use a secure serializer instead, and **don't allow an attacker to specify an arbitrary type to deserialize**. For more information see [Preferred alternatives](../../../standard/serialization/binaryformatter-security-guide.md#preferred-alternatives).
 - Make the serialized data tamper-proof. After serialization, cryptographically sign the serialized data. Before deserialization, validate the cryptographic signature. Protect the cryptographic key from being disclosed and design for key rotations.
 
 ## When to suppress warnings

docs/fundamentals/code-analysis/quality-rules/ca2321.md

@@ -10,15 +10,14 @@ dev_langs:
  - VB
 f1_keywords:
   - "CA2321"
-  - "DoNotCallBinaryFormatterDeserializeWithoutFirstSettingBinaryFormatterBinder"
 ---
 # CA2321: Do not deserialize with JavaScriptSerializer using a SimpleTypeResolver
 
-| | Value |
-|-|-|
-| **Rule ID** |CA2321|
-| **Category** |[Security](security-warnings.md)|
-| **Fix is breaking or non-breaking** |Non-breaking|
+|                                     | Value                            |
+| ----------------------------------- | -------------------------------- |
+| **Rule ID**                         | CA2321                           |
+| **Category**                        | [Security](security-warnings.md) |
+| **Fix is breaking or non-breaking** | Non-breaking                     |
 
 ## Cause
 

docs/orleans/host/configuration-guide/serialization.md

@@ -282,8 +282,8 @@ The rules are:
 
 Orleans supports transmission of arbitrary types at runtime and therefore the in-built code generator cannot determine the entire set of types that will be transmitted ahead of time. Additionally, certain types cannot have serializers generated for them because they are inaccessible (for example, `private`) or have inaccessible fields (for example, `readonly`). Therefore, there is a need for just-in-time serialization of types that were unexpected or could not have serializers generated ahead of time. The serializer responsible for these types is called the *fallback serializer*. Orleans ships with two fallback serializers:
 
-* <xref:Orleans.Serialization.BinaryFormatterSerializer?displayProperty=fullName> which uses .NET's <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>; and
-* <xref:Orleans.Serialization.ILBasedSerializer?displayProperty=fullName> which emits [CIL](../../../standard/glossary.md#il) instructions at runtime to create serializers that leverage Orleans' serialization framework to serialize each field. This means that if an inaccessible type `MyPrivateType` contains a field `MyType` which has a custom serializer, that custom serializer will be used to serialize it.
+* <xref:Orleans.Serialization.BinaryFormatterSerializer?displayProperty=fullName>, which uses .NET's <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>; and
+* <xref:Orleans.Serialization.ILBasedSerializer?displayProperty=fullName>, which emits [CIL](../../../standard/glossary.md#il) instructions at runtime to create serializers that leverage Orleans' serialization framework to serialize each field. This means that if an inaccessible type `MyPrivateType` contains a field `MyType` which has a custom serializer, that custom serializer will be used to serialize it.
 
 The fallback serializer can be configured using the <xref:Orleans.Configuration.SerializationProviderOptions.FallbackSerializationProvider> property on both <xref:Orleans.Runtime.Configuration.ClientConfiguration> on the client and <xref:Orleans.Runtime.Configuration.GlobalConfiguration> on the silos.
 

docs/standard/base-types/how-to-round-trip-date-and-time-values.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: How to: Round-trip Date and Time Values"
 title: "How to: Round-trip Date and Time Values"
+description: "Learn how to round-trip date and time values"
 ms.date: 11/15/2022
 dev_langs:
   - "csharp"
@@ -12,7 +12,7 @@ helpviewer_keywords:
   - "formatting strings [.NET], round-trip values"
 ms.assetid: b609b277-edc6-4c74-b03e-ea73324ecbdb
 ---
-# How to: Round-trip Date and Time Values
+# How to: Round-trip Date and time values
 
 In many applications, a date and time value is intended to unambiguously identify a single point in time. This article shows how to save and restore a <xref:System.DateTime> value, a <xref:System.DateTimeOffset> value, and a date and time value with time zone information so that the restored value identifies the same time as the saved value.
 

docs/standard/language-independence.md

@@ -363,7 +363,7 @@ Constructors in CLS-compliant classes and structures must follow these rules:
   [!code-csharp[Conceptual.CLSCompliant#11](../../samples/snippets/csharp/VS_Snippets_CLR/conceptual.clscompliant/cs/ctor1.cs#11)]
   [!code-vb[Conceptual.CLSCompliant#11](../../samples/snippets/visualbasic/VS_Snippets_CLR/conceptual.clscompliant/vb/ctor1.vb#11)]
 
-* An object constructor cannot be called except to create an object. In addition, an object cannot be initialized twice. For example, this means that <xref:System.Object.MemberwiseClone%2A?displayProperty=nameWithType> and deserialization methods such as <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize%2A?displayProperty=nameWithType> must not call constructors.
+* An object constructor cannot be called except to create an object. In addition, an object cannot be initialized twice. For example, this means that <xref:System.Object.MemberwiseClone%2A?displayProperty=nameWithType> and deserialization methods must not call constructors.
 
 ### Properties
 

docs/standard/serialization/binaryformatter-event-source.md

@@ -14,7 +14,7 @@ This functionality is not a substitute for a <xref:System.Runtime.Serialization.
 
 ## Description of events
 
-The `BinaryFormatter` event source has the well-known name `System.Runtime.Serialization.Formatters.Binary.BinaryFormatterEventSource`. Listeners may subscribe to 6 events.
+The `BinaryFormatter` event source has the well-known name `System.Runtime.Serialization.Formatters.Binary.BinaryFormatterEventSource`. Listeners can subscribe to six events.
 
 ### SerializationStart event (id = `10`)