Files
docs-desktop/.github/ISSUE_TEMPLATE/dotnet-breaking-change.md
T

2.3 KiB

name, about
name about
.NET Core breaking change Report a change in .NET Core that breaks something that worked in a previous version (intended mostly for product-team use)

[Change title]

[Brief description of the change]

Version introduced

[Version in which the breaking change first occurred (for example, 3.0 for .NET Core 3.0)]

Old behavior

New behavior

Reason for change

[ Suggested steps if user is affected go here:

  • Possible workarounds
  • Example of code changes to handle change ]

Category

[Choose a category from one of the following:

  • ASP.NET Core
  • C#
  • Core .NET libraries
  • Cryptography
  • Data
  • Debugger
  • Deployment
  • Globalization
  • Interop
  • JIT
  • LINQ
  • Managed Extensibility Framework (MEF)
  • MSBuild
  • Networking
  • Printing
  • Security
  • Serialization
  • Visual Basic
  • Windows Forms
  • Windows Presentation Foundation (WPF)
  • XML, XSLT ]

Affected APIs

[ If no APIs are affected, this should read: "Not detectable via API analysis"

If affected APIs are identifiable, include a link for each. The link takes the form:

[friendly description of API](link to API on docs.microsoft.com)

For example, `String.IndexOf(String)

For methods, if all overloads are affected, link to the general overloaded method page. For example:

https://docs.microsoft.com/dotnet/api/system.string.indexof

Otherwise, link to the individual method overload. For example:

https://docs.microsoft.com/dotnet/api/system.string.indexof#System_String_IndexOf_System_String_

]


Issue metadata

  • Issue type: breaking-change