Add Deprecation Links in Details page in PM UI

[dominoFire]

Add two new deprecation links in details Page in PM UI when a package is deprecated.

• More Info Link
• Alternate package Link

[skofman1]

Hi @dominoFire , looked at the cool demo of the feature (this is so useful!), and I have a minor suggestion.

For packages where the version of the 'Alternative package' isn't specified, right now we show 'Azure.Storage.Blobs >= 0.0.0'. How about:

1. Just the package name with no version
2. Showing 'Azure.Storage.Blobs any version'

What do you think? Again, it's minor but the current UX is a bit confusing.

//cc @aortiz-msft

[aortiz-msft]

@chgill-MSFT ^

[dominoFire]

@skofman1 @aortiz-msft @chgill-MSFT Thanks for the follow-up. We have a current discussion in the following issue:

#8795

I think we should match the experience in nuget.org

[chrisraygill]

@dominoFire IMO we should just open the package details window to the default version given their search preferences.

If they have Include prerelease enabled, then show the latest stable/prerelease version. If they have Include prerelease disabled, then show the latest stable version.

This is already how browse works in the PMUI today in normal search scenarios. NuGet.org works a little differently, but I think somewhat incidentally. On NuGet.org the alternate package deprecation link goes to nuget.org/packages/<packageID>/ with no version specified which goes to the latest stable version. On NuGet.org, there's nowhere to specify a preference for prerelease or stable versions on the package details page - only in search.

TL;DR

Let's do what's most natural to the PMUI already which isn't exactly what NuGet.org does.

In the case of afine >= 0.0.0 today, instead:

Don't show any version - open the linked package to the latest stable or latest including prerelease depending on if "Include prerelease" is enabled.