[Suggestion] Link “https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference” should be clickable in migration-failed dialog

[v-longmin]

Details about Problem

VS Version: D16.2stg 29027.113
OS Version: 17763.RS5_Release.180914-1434.
Install VS: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=2806963&view=results
Install NuGet: \\ddfiles\Drops\NuGet\Drops\CI\NuGet.Client\Dev\5.2.0.6067\artifacts\VS15\NuGet.Tools.vsix

Detailed repro steps

1. Launch Visual Studio 2019.
2. Create a new C++ Console App project and open PM UI in Solution Explorer window.
3. Install a package (e.g. Netonsoft.json) with “packages.config” format into the project.
4. Right-click the “Reference” node and select the “Migrate packages.config to PackageReference…”.
5. Observe the warning.

Expected

“https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference” should be a link in migration-failed dialog.

Actual

Link “https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference” does not clickable in migration-failed dialog as below screenshot.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for icebox cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will add a Triage:NeedsTriageDiscussion label and lead to a triaging process.
This process is part of the experimental Stale icebox issues cleanup we are currently trialing. Please share any feedback you might have in the linked issue.

[ghost]

This issue will now be closed since it had been marked Icebox cleanup candidate, but received no further activity in the past 14 days.

[ghost]

This issue will now be closed since it had been marked Icebox cleanup candidate, but received no further activity in the past 14 days.

[v-luzh]

It still reproes om Main\33912.166 + NuGet Client Dev\6.8.0.22, so we reopen it to track the issue.

[jebriede]

Team triage: The error is being displayed in a message box that does not support hyperlinks and we'd need to create a custom dialog with a hyperlink support to change the behavior. Users can copy the dialog with Ctrl+C and copy the URL to visit it. Converting the error dialog to a custom dialog and supporting hyperlinks is lower priority than some other features we are working on for now.