APIComparer
APIComparer copied to clipboard
Compares NuGetPackages/Assemblies and displays changes in the public api.
Into %home%\LogFiles that is used for all other logs by Azure
Eg https://github.com/ParticularLabs/APIComparer/issues/82 To make sure transient failures won't cause the comparison to fail permanently Current workaround is to run `(Get-ChildItem *.html | Select-String -Pattern "failed with the following" | Select-Object...
In the ApprovalTests NuGet package, this change removed a virtual from a public type's public property in the 3.0.14 release: https://github.com/approvals/ApprovalTests.Net/commit/6d75f8767b9b052541813906965b5d2090780add#diff-5c97d4e883fa80b2a2a6abb36842bbeaL32 However it's not listed in the report: http://apicomparer.particular.net/compare/ApprovalTests/3.0.13...3.0.14#.NETFramework,Version=v4.5
http://apicomparer.particular.net/compare/openrasta-core/2.5.2001...2.6.0-preview.1 blows up with ``` System.ArgumentException: '2.6.0-preview.1' is not a valid version string. Parameter name: version at NuGet.SemanticVersion.Parse(String version) ```
Since renaming is a breaking change Eg. https://github.com/Particular/NServiceBus/pull/4581#pullrequestreview-29367345
By moving it from `/home/wwwroot` to `/home`
This is just a suggestion. Was looking how .NET Core created their API changes and it was very interesting way of leveraging .md with GitHub. https://github.com/dotnet/core/blob/master/release-notes/1.1/1.0-1.1-api-diff/1.0-1.1-api-diff_System.Composition.Convention.md
API comparer results could be broken due to nuget not available but results cached. Example `NServiceBus.Azure.Transports.WindowsAzureServiceBus comparison between 6.4.0 and 7.0.0 has failed with the following error: Unable to find...