Andreas Öhlund

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...

Support for semver2 style versions

2

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`

Create a basic landing page

2

With textboxes for nuget, leftversion, rightversion

Nuget versions should be case insensitive

4

Eg: http://apicomparer.particular.net/compare/NServiceBus/5.2.16...6.0.0-RC0003 fails since the package is called rc0003

http://apicomparer.particular.net/compare/NServiceBus/5.2.16...6.0.0-RC2 could potentially expand to http://apicomparer.particular.net/compare/NServiceBus/5.2.16...6.0.0-rc0002

Example from the exe: ``` ## The following types are no longer available ### NServiceBus.AzureDataBusDefaults Default can be found in our documentation. ## Types with removed members ### NServiceBus.AzureDataBusDefaults ####...

Better highlight removed and new targets

3

The tabbed view that @SeanFeldman added does work but it would be nice if we can improve the visiblity of new and/or removed targets. Example where the rabbit client dropped...