You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .NET SDK itself now has means to check for source or binary breaking changes in the public API against an earlier version of an assembly or package. In addition to the MSbuild tasks there is even the Microsoft.DotNet.ApiCompat.Tool global tool.
It seems to me, that there is no more active development of Microsoft.CodeAnalysis.PublicApiAnalyzers.
So I wondered if those features of the .NET SDK is to be the replacement for Microsoft.CodeAnalysis.PublicApiAnalyzers.
The text was updated successfully, but these errors were encountered:
bitbonk
changed the title
Is the API compatibility verification built into .NET SDK the replacement for Microsoft.CodeAnalysis.PublicApiAnalyzers?
Is the built-in API compatibility verification of the .NET SDK the replacement for Microsoft.CodeAnalysis.PublicApiAnalyzers?
Dec 15, 2024
The .NET SDK itself now has means to check for source or binary breaking changes in the public API against an earlier version of an assembly or package. In addition to the MSbuild tasks there is even the Microsoft.DotNet.ApiCompat.Tool global tool.
It seems to me, that there is no more active development of
Microsoft.CodeAnalysis.PublicApiAnalyzers
.So I wondered if those features of the .NET SDK is to be the replacement for
Microsoft.CodeAnalysis.PublicApiAnalyzers
.The text was updated successfully, but these errors were encountered: