[BUG] Microsoft.Rest.ClientRuntime Dependency Loop

[TheOnlyWei]

Describe the bug
Please provide the description of issue you're seeing.

Installing the following package:
https://www.nuget.org/packages/Microsoft.Rest.ClientRuntime/

NOTE: the command is wrong, the parameter -Version should be -RequiredVersion.

After entering the command, I get a dependency loop error:

PS C:\Users\Administrator\Desktop\dotnet\hybrid-compute-dotnet-manage-vm> Install-Package Microsoft.Rest.ClientRuntime -RequiredVersion 2.3.22

The package(s) come(s) from a package source that is not marked as trusted.
Are you sure you want to install software from 'nuget.org'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): A
Install-Package : Dependency loop detected for package 'Microsoft.Rest.ClientRuntime'.
At line:1 char:1
+ Install-Package Microsoft.Rest.ClientRuntime -RequiredVersion 2.3.22
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : Deadlock detected: (Microsoft.Rest.ClientRuntime:String) [Install-Package], Exception
    + FullyQualifiedErrorId : DependencyLoopDetected,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Expected behavior
What is the expected behavior?

Should not have an error.

Actual behavior (include Exception or Stack Trace)
What is the actual behavior?

There was an error.

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. Install-Package Microsoft.Rest.ClientRuntime -RequiredVersion 2.3.22

Environment:

• Name and version of the Library package used: Microsoft.Rest.ClientRuntime 2.3.22
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): Windows Server 2019 Datacenter
• IDE and version : [e.g. Visual Studio 16.3] Visual Studio Code

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[YalinLi0312]

@jsquire It looks is Microsoft.Rest.ClientRuntime, why it is a question for management package?

[jsquire]

@YalinLi0312: That's a mistake on may part. Apologies for the confusion.

[ghost]

Hi @TheOnlyWei. There hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by removing the no-recent-activity label. Otherwise, we'll close this out in 7 days.

[ghost]

Hi @TheOnlyWei. There was a mistake and this issue was unintentionally flagged as a stale pull request. The label has been removed and the issue will remain active; no action is needed on your part. Apologies for the inconvenience.

[AlexGhiondea]

@TheOnlyWei there is a newer version of the package -- are you still seeing this?

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[TheOnlyWei]

@AlexGhiondea Yes, I get the same error in 2.3.23 (the latest version I found).

Install-Package: Dependency loop detected for package 'Microsoft.Rest.ClientRuntime'.

[pakrym]

There are two versions of Install-Package commands. One exists inside Package Manager Console in VisualStudio and works just fine:

The other is from PackageManagement Powershell module and is intended for general-purpose powershell packages, not .NET packages. You are ending up using this version. It's unable to handle .NET-specific package authoring.

When using VSCOde I recommend using dotnet package add to install the package.

dotnet add package Microsoft.Rest.ClientRuntime --version 2.3.22

[ghost]

Hi @TheOnlyWei. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @TheOnlyWei, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.