Update breaking change doc formatting

microsoft · richlander · Apr 17, 2017 · Apr 15, 2017 · Apr 17, 2017 · Apr 17, 2017
commit 1f89ff65d0b5e175c10ab31fe9192177591c3c76
diff --git a/...with-netdatacontractserializer-cannot-be-deserialized-by-_net-4_5_1-or-4_5_2.md b/...with-netdatacontractserializer-cannot-be-deserialized-by-_net-4_5_1-or-4_5_2.md
@@ -1,4 +1,4 @@
-## 133: A ConcurrentDictionary serialized in .NET 4.5 with NetDataContractSerializer cannot be deserialized by .NET 4.5.1 or 4.5.2
+## A ConcurrentDictionary serialized in .NET 4.5 with NetDataContractSerializer cannot be deserialized by .NET 4.5.1 or 4.5.2
 
 ### Scope
 Minor
@@ -43,3 +43,4 @@ Core
     Should be fairly easy to detect ConcurrentDictionary objects being serialized/deserialized by a NetDataContractSerializer.
 -->
 
+<!-- breaking change id: 133 -->
diff --git a/...dler-of-the-datagrid's-unloadingrow-event-can-cause-a-nullreferenceexception.md b/...dler-of-the-datagrid's-unloadingrow-event-can-cause-a-nullreferenceexception.md
@@ -1,4 +1,4 @@
-## 107: Accessing a WPF DataGrid's selected items from a handler of the DataGrid's UnloadingRow event can cause a NullReferenceException
+## Accessing a WPF DataGrid's selected items from a handler of the DataGrid's UnloadingRow event can cause a NullReferenceException
 
 ### Scope
 Minor
@@ -27,3 +27,5 @@ This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgr
 
 ### Category
 Windows Presentation Foundation (WPF)
+
+<!-- breaking change id: 107 -->
diff --git a/...anges/ado_net-now-attempts-to-automatically-reconnect-broken-sql-connections.md b/...anges/ado_net-now-attempts-to-automatically-reconnect-broken-sql-connections.md
@@ -1,4 +1,4 @@
-## 119: ADO.NET now attempts to automatically reconnect broken SQL connections
+## ADO.NET now attempts to automatically reconnect broken SQL connections
 
 ### Scope
 Edge
@@ -42,4 +42,4 @@ Data
     Single-diagnostic compilation action analyzer
 -->
 
-
+<!-- breaking change id: 119 -->
diff --git a/...ing-changes/aescryptoserviceprovider-decryptor-provides-a-reusable-transform.md b/...ing-changes/aescryptoserviceprovider-decryptor-provides-a-reusable-transform.md
@@ -1,4 +1,4 @@
-## 165: AesCrytpServiceProvider decryptor provides a reusable transform
+## AesCrytpServiceProvider decryptor provides a reusable transform
 
 ### Scope
 Minor
@@ -46,4 +46,4 @@ Core
     205301
 -->
 
-
+<!-- breaking change id: 165 -->
diff --git a/...etup_dynamicbase-is-no-longer-randomized-by-userandomizedstringhashalgorithm.md b/...etup_dynamicbase-is-no-longer-randomized-by-userandomizedstringhashalgorithm.md
@@ -1,4 +1,4 @@
-## 115: AppDomainSetup.DynamicBase is no longer randomized by UseRandomizedStringHashAlgorithm
+## AppDomainSetup.DynamicBase is no longer randomized by UseRandomizedStringHashAlgorithm
 
 ### Scope
 Edge
@@ -29,3 +29,4 @@ Core
     Should be easy to look for DynamicBase use while UseRandomizedStringHashAlgorithm is set
 -->
 
+<!-- breaking change id: 115 -->
diff --git a/...ger-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md b/...ger-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md
@@ -1,4 +1,4 @@
-## 144: Application.FilterMessage no longer throws for re-entrant implementations of IMessageFilter.PreFilterMessage
+## Application.FilterMessage no longer throws for re-entrant implementations of IMessageFilter.PreFilterMessage
 
 ### Scope
 Edge
@@ -37,4 +37,4 @@ Windows Forms
     more useful, even though it would be easier to be 'precise' if we analyzed the interface implementer.
 -->
 
-
+<!-- breaking change id: 144 -->
diff --git a/...ickonce-that-use-a-sha-256-code-signing-certificate-may-fail-on-windows-2003.md b/...ickonce-that-use-a-sha-256-code-signing-certificate-may-fail-on-windows-2003.md
@@ -1,4 +1,4 @@
-## 63: Apps published with ClickOnce that use a SHA-256 code-signing certificate may fail on Windows 2003
+## Apps published with ClickOnce that use a SHA-256 code-signing certificate may fail on Windows 2003
 
 ### Scope
 Edge
@@ -40,3 +40,5 @@ ClickOnce
     ### Notes
     Only affects WinServer 2003; there is a KB to address it.  Could flag it if we detect click-once being used (especially if it has a SHA-1 code-signing cert)
 -->
+
+<!-- breaking change id: 63 -->
diff --git a/...ges/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md b/...ges/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md
@@ -1,4 +1,4 @@
-## 125: ASP.NET MVC now escapes spaces in strings passed in via route parameters
+## ASP.NET MVC now escapes spaces in strings passed in via route parameters
 
 ### Scope
 Minor
@@ -31,3 +31,4 @@ ASP.NET
     Single-diagnostic compilation action analyzer
 -->
 
+<!-- breaking change id: 125 -->
diff --git a/.../assemblies-compiled-with-regex_compiletoassembly-breaks-between-4_0-and-4_5.md b/.../assemblies-compiled-with-regex_compiletoassembly-breaks-between-4_0-and-4_5.md
@@ -1,4 +1,4 @@
-## 74: Assemblies compiled with Regex.CompileToAssembly breaks between 4.0 and 4.5
+## Assemblies compiled with Regex.CompileToAssembly breaks between 4.0 and 4.5
 
 ### Scope
 Minor
@@ -30,3 +30,5 @@ To work around this problem, you can do either of the following:
 Core
 
 [More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
+
+<!-- breaking change id: 74 -->
diff --git a/...breaking-changes/binaryformatter-can-fail-to-find-type-from-loadfrom-context.md b/...breaking-changes/binaryformatter-can-fail-to-find-type-from-loadfrom-context.md
@@ -1,4 +1,4 @@
-## 147: BinaryFormatter can fail to find type from LoadFrom context
+## BinaryFormatter can fail to find type from LoadFrom context
 
 ### Scope
 Edge
@@ -45,3 +45,5 @@ public class TypeFinderBinder : SerializationBinder
 
 ### Category
 Serialization
+
+<!-- breaking change id: 147 -->
diff --git a/...elector-property-(such-as-'selecteditem')-to-a-static-property-does-not-work.md b/...elector-property-(such-as-'selecteditem')-to-a-static-property-does-not-work.md
@@ -1,4 +1,4 @@
-## 99: Binding a WPF selector property (such as 'SelectedItem') to a static property does not work
+## Binding a WPF selector property (such as 'SelectedItem') to a static property does not work
 
 ### Scope
 Minor
@@ -34,4 +34,4 @@ Windows Presentation Foundation (WPF)
     We could look for FrameworkElement.SetBinding calls, but this is such a corner case of that (selected properties and static properties) that it would probably be too noisy. A xaml analyzer is probably our best bet, and that's not even going to be perfect
 -->
 
-
+<!-- breaking change id: 99 -->
diff --git a/...on/breaking-changes/blockingcollection_trytakefromany-does-not-throw-anymore.md b/...on/breaking-changes/blockingcollection_trytakefromany-does-not-throw-anymore.md
@@ -1,4 +1,4 @@
-## 18: BlockingCollection&lt;T&gt;.TryTakeFromAny does not throw anymore
+## BlockingCollection&lt;T&gt;.TryTakeFromAny does not throw anymore
 
 ### Scope
 Minor
@@ -30,3 +30,5 @@ If TryTakeFromAny returning -1 or TakeFromAny throwing were used for control-flo
 Core
 
 [More information](https://msdn.microsoft.com/en-us/library/hh367887#core)
+
+<!-- breaking change id: 18 -->
diff --git a/...-fail-with-error-msb4062-if-using-the-entitydeploysplit-or-entityclean-tasks.md b/...-fail-with-error-msb4062-if-using-the-entitydeploysplit-or-entityclean-tasks.md
@@ -1,4 +1,4 @@
-## 109: Building an Entity Framework edmx with Visual Studio 2013 can fail with error MSB4062 if using the EntityDeploySplit or EntityClean tasks
+## Building an Entity Framework edmx with Visual Studio 2013 can fail with error MSB4062 if using the EntityDeploySplit or EntityClean tasks
 
 ### Scope
 Major
@@ -29,3 +29,4 @@ Entity Framework
 
 [More information](http://stackoverflow.com/questions/20400054/entitydeploysplit-error-microsoft-data-entity-build-tasks-dll-missing/24249247#24249247)
 
+<!-- breaking change id: 109 -->
diff --git a/...omattributes-on-an-indexer-property-no-longer-throws-ambiguousmatchexception.md b/...omattributes-on-an-indexer-property-no-longer-throws-ambiguousmatchexception.md
@@ -1,4 +1,4 @@
-## 112: Calling Attribute.GetCustomAttributes on an indexer property no longer throws AmbiguousMatchException if the ambiguity can be resolved by index's type
+## Calling Attribute.GetCustomAttributes on an indexer property no longer throws AmbiguousMatchException if the ambiguity can be resolved by index's type
 
 ### Scope
 Edge
@@ -37,4 +37,6 @@ Be aware that GetCustomAttribute(s) will work more frequently now. If an app was
 * `M:System.Reflection.CustomAttributeExtensions.GetCustomAttributes``1(System.Reflection.MemberInfo,System.Boolean)`
 
 ### Category
-Core
+Core
+
+<!-- breaking change id: 112 -->
diff --git a/...s/calling-createdefaultauthorizationcontext-with-a-null-argument-has-changed.md b/...s/calling-createdefaultauthorizationcontext-with-a-null-argument-has-changed.md
@@ -1,4 +1,4 @@
-## 138: Calling CreateDefaultAuthorizationContext with a null argument has changed
+## Calling CreateDefaultAuthorizationContext with a null argument has changed
 
 ### Scope
 Minor
@@ -28,3 +28,5 @@ In rare cases, WCF apps that use custom authentication may see behavioral differ
 Windows Communication Foundation (WCF)
 
 [More information](https://msdn.microsoft.com/en-us/library/dn833123%28v=vs.110%29.aspx#WCF)
+
+<!-- breaking change id: 138 -->
diff --git a/...hanges/calling-datagrid_commitedit-from-a-celleditending-handler-drops-focus.md b/...hanges/calling-datagrid_commitedit-from-a-celleditending-handler-drops-focus.md
@@ -1,4 +1,4 @@
-## 124: Calling DataGrid.CommitEdit from a CellEditEnding handler drops focus
+## Calling DataGrid.CommitEdit from a CellEditEnding handler drops focus
 
 ### Scope
 Edge
@@ -26,4 +26,6 @@ This bug has been fixed in the .NET Framework 4.5.2, so it can be avoided by upg
 * `M:System.Windows.Controls.DataGrid.CommitEdit(System.Windows.Controls.DataGridEditingUnit,System.Boolean)`
 
 ### Category
-Windows Presentation Foundation (WPF)
+Windows Presentation Foundation (WPF)
+
+<!-- breaking change id: 124 -->
diff --git a/...agrid-with-items-selected-can-cause-duplicate-items-to-appear-in-the-element.md b/...agrid-with-items-selected-can-cause-duplicate-items-to-appear-in-the-element.md
@@ -1,4 +1,4 @@
-## 104: Calling Items.Refresh on a WPF ListBox, ListView, or DataGrid with items selected can cause duplicate items to appear in the element
+## Calling Items.Refresh on a WPF ListBox, ListView, or DataGrid with items selected can cause duplicate items to appear in the element
 
 ### Scope
 Minor
@@ -29,3 +29,4 @@ Windows Presentation Foundation (WPF)
 
 [More information](http://connect.microsoft.com/VisualStudio/feedback/details/873075/on-net-4-5-the-selected-items-in-a-wpf-listbox-listview-control-are-incorrect-when-items-refresh-is-called-from-code-behind)
 
+<!-- breaking change id: 104 -->
diff --git a/Documentation/breaking-changes/calls-to-claimsidentity-constructors.md b/Documentation/breaking-changes/calls-to-claimsidentity-constructors.md
@@ -1,4 +1,4 @@
-## 164: Calls to ClaimsIdentity constructors
+## Calls to ClaimsIdentity constructors
 
 ### Scope
 Edge
@@ -40,3 +40,5 @@ Core
     ### Original Bug
     227024
 -->
+
+<!-- breaking change id: 164 -->
diff --git a/...-changes/change-in-behavior-for-task_waitall-methods-with-time-out-arguments.md b/...-changes/change-in-behavior-for-task_waitall-methods-with-time-out-arguments.md
@@ -1,4 +1,4 @@
-## 26: Change in behavior for Task.WaitAll methods with time-out arguments
+## Change in behavior for Task.WaitAll methods with time-out arguments
 
 ### Scope
 Minor
@@ -29,3 +29,5 @@ If an AggregateException was being caught as a means of detecting a task that wa
 Core
 
 [More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
+
+<!-- breaking change id: 26 -->
diff --git a/...n/breaking-changes/change-in-behavior-in-data-definition-language-(ddl)-apis.md b/...n/breaking-changes/change-in-behavior-in-data-definition-language-(ddl)-apis.md
@@ -1,4 +1,4 @@
-## 27: Change in behavior in Data Definition Language (DDL) APIs
+## Change in behavior in Data Definition Language (DDL) APIs
 
 ### Scope
 Minor
@@ -31,3 +31,5 @@ These changes make it easier to build tools and applications that use the DDL AP
 Entity Framework
 
 [More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#sql)
+
+<!-- breaking change id: 27 -->
diff --git a/Documentation/breaking-changes/changes-in-path-normalization.md b/Documentation/breaking-changes/changes-in-path-normalization.md
@@ -1,4 +1,4 @@
-## 163: Changes in path normalization
+## Changes in path normalization
 
 ### Scope
 Minor
@@ -61,4 +61,4 @@ Core
     195340
 -->
 
-
+<!-- breaking change id: 163 -->
diff --git a/...led-property-of-the-parent-of-a-textblock-control-affects-any-child-controls.md b/...led-property-of-the-parent-of-a-textblock-control-affects-any-child-controls.md
@@ -1,4 +1,4 @@
-## 161: Changing the IsEnabled property of the parent of a TextBlock control affects any child controls
+## Changing the IsEnabled property of the parent of a TextBlock control affects any child controls
 
 ### Scope
 Minor
@@ -31,4 +31,4 @@ Windows Presentation Foundation (WPF)
     213267
 -->
 
-
+<!-- breaking change id: 161 -->
diff --git a/Documentation/breaking-changes/clickonce-supports-sha-256-on-4_0-targeted-apps.md b/Documentation/breaking-changes/clickonce-supports-sha-256-on-4_0-targeted-apps.md
@@ -1,4 +1,4 @@
-## 79: ClickOnce supports SHA-256 on 4.0-targeted apps
+## ClickOnce supports SHA-256 on 4.0-targeted apps
 
 ### Scope
 Minor
@@ -31,3 +31,4 @@ ClickOnce
     We could possibly detect this by analyzing ClickOnce manifests and looking for SHA-256 certs.
 -->
 
+<!-- breaking change id: 79 -->
diff --git a/Documentation/breaking-changes/coerceisselectionboxhighlighted.md b/Documentation/breaking-changes/coerceisselectionboxhighlighted.md
@@ -1,4 +1,4 @@
-## 179: CoerceIsSelectionBoxHighlighted
+## CoerceIsSelectionBoxHighlighted
 
 ### Scope
 Minor
@@ -32,4 +32,4 @@ Windows Presentation Foundation (WPF)
     125219
 -->
 
-
+<!-- breaking change id: 179 -->
diff --git a/...g-changes/compiler-support-for-type-forwarding-when-multi-targeting-mscorlib.md b/...g-changes/compiler-support-for-type-forwarding-when-multi-targeting-mscorlib.md
@@ -1,4 +1,4 @@
-## 56: Compiler support for type forwarding when multi-targeting mscorlib
+## Compiler support for type forwarding when multi-targeting mscorlib
 
 ### Scope
 Edge
@@ -25,3 +25,5 @@ This change prevents compiler warnings (and compilation failure in cases where w
 Core
 
 [More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#core)
+
+<!-- breaking change id: 56 -->
diff --git a/...s/concurrentqueue_trypeek-can-return-an-erroneous-null-via-its-out-parameter.md b/...s/concurrentqueue_trypeek-can-return-an-erroneous-null-via-its-out-parameter.md
@@ -1,4 +1,4 @@
-## 95: ConcurrentQueue&lt;T&gt;.TryPeek can return an erroneous null via its out parameter
+## ConcurrentQueue&lt;T&gt;.TryPeek can return an erroneous null via its out parameter
 
 ### Scope
 Major
@@ -28,3 +28,5 @@ This issue is fixed in the .NET Framework 4.5.1. Upgrading to that Framework wil
 Core
 
 [More information](http://connect.microsoft.com/VisualStudio/feedback/details/762273/bug-in-concurrentqueue-in-net-4-5-trypeek-returns-true-but-no-real-object-returned)
+
+<!-- breaking change id: 95 -->
diff --git a/...g-changes/connection-pool-blocking-period-for-azure-sql-databases-is-removed.md b/...g-changes/connection-pool-blocking-period-for-azure-sql-databases-is-removed.md
@@ -1,4 +1,4 @@
-## 160: Connection pool blocking period for Azure SQL databases is removed
+## Connection pool blocking period for Azure SQL databases is removed
 
 ### Scope
 Minor
@@ -39,4 +39,4 @@ Data
     213479
 -->
 
-
+<!-- breaking change id: 160 -->
diff --git a/...aking-changes/contentdisposition-datetimes-returns-slightly-different-string.md b/...aking-changes/contentdisposition-datetimes-returns-slightly-different-string.md
@@ -1,4 +1,4 @@
-## 78: ContentDisposition DateTimes returns slightly different string
+## ContentDisposition DateTimes returns slightly different string
 
 ### Scope
 Minor
@@ -26,3 +26,5 @@ Do not expect that string representations of ContentDispositions from different
 Networking
 
 [More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#Networking)
+
+<!-- breaking change id: 78 -->
diff --git a/...eaking-changes/cor_prf_gc_root_handles-are-not-being-enumerated-by-profilers.md b/...eaking-changes/cor_prf_gc_root_handles-are-not-being-enumerated-by-profilers.md
@@ -1,4 +1,4 @@
-## 117: COR_PRF_GC_ROOT_HANDLEs are not being enumerated by profilers
+## COR_PRF_GC_ROOT_HANDLEs are not being enumerated by profilers
 
 ### Scope
 Minor
@@ -32,3 +32,4 @@ Core
     Native code analysis needed. Also, this could be categorized as 'profiling' but I chose to call it 'core' because there are no other profiling issues. We can add that category in the future if enough issues crop up to justify it.
 -->
 
+<!-- breaking change id: 117 -->
diff --git a/...ion/breaking-changes/cspparameters_parentwindowhandle-now-expects-hwnd-value.md b/...ion/breaking-changes/cspparameters_parentwindowhandle-now-expects-hwnd-value.md
@@ -1,4 +1,4 @@
-## 178: CspParameters.ParentWindowHandle now expects HWND value
+## CspParameters.ParentWindowHandle now expects HWND value
 
 ### Scope
 Minor
@@ -53,3 +53,5 @@ can set the AppContext switch to `false`.
 
 ### Category
 Security
+
+<!-- breaking change id: 178 -->
diff --git a/Documentation/breaking-changes/currentculture-flows-across-tasks.md b/Documentation/breaking-changes/currentculture-flows-across-tasks.md
@@ -1,4 +1,4 @@
-## 146: CurrentCulture and CurrentUICulture flow across tasks
+## CurrentCulture and CurrentUICulture flow across tasks
 
 ### Scope
 Minor
@@ -39,3 +39,5 @@ Applications targeting .NET 4.6 or later will automatically get the right behavi
 Core
 
 [More information](https://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo%28v=vs.110%29.aspx#Async)
+
+<!-- breaking change id: 146 -->
diff --git a/...eaking-changes/currentculture-not-preserved-across-wpf-dispatcher-operations.md b/...eaking-changes/currentculture-not-preserved-across-wpf-dispatcher-operations.md
@@ -1,4 +1,4 @@
-## 145: CurrentCulture is not preserved across WPF Dispatcher operations
+## CurrentCulture is not preserved across WPF Dispatcher operations
 
 ### Scope
 Minor
@@ -45,3 +45,5 @@ Windows Presentation Foundation (WPF)
     This issue is not marked as detectable via API analysis because simply looking for CurrentCulture or CurrentUICulture being set is insufficient in most cases - it must be done in a WPF app.
     Also, looking for WPF Dispatcher invocations is insufficient because many dispatcher invocations are automatic and, besides that, there is no way to know if CurrentCulture or CurrentUICulture matters for those dispatchers.
 -->
+
+<!-- breaking change id: 145 -->
diff --git a/...-changes/datagridcellspanel_bringintoview-throws-argumentoutofrangeexception.md b/...-changes/datagridcellspanel_bringintoview-throws-argumentoutofrangeexception.md
@@ -1,4 +1,4 @@
-## 151: DataGridCellsPanel.BringIndexIntoView throws ArgumentOutOfRangeException
+## DataGridCellsPanel.BringIndexIntoView throws ArgumentOutOfRangeException
 
 ### Scope
 Edge
@@ -35,3 +35,5 @@ Windows Presentation Foundation (WPF)
 <!--
 Original Bug: 272673
 -->
+
+<!-- breaking change id: 151 -->