简体   繁体   English

libman package 管理器在初始化时冻结

[英]The libman package manager freezes in initialization

I used the libman package manager on Visual Studio 2022 very well, however, the libman freezes in package console manager for a long time today when I use the libman init command.我在 Visual Studio 2022 上很好地使用了 libman package 管理器,但是,今天当我使用libman init命令时,libman 在 package 控制台管理器中冻结了很长时间。

The libman --version works well. libman --version 运行良好。

PM> libman --version

2.1.161+abc97ecc7d.RR

I found the similar problem in the Visual Studio community but it didn't have any solutions or workarounds.我在Visual Studio 社区中发现了类似的问题,但没有任何解决方案或解决方法。

I clean the cache of libman by below command, however, the issue doesn't resolve.我通过以下命令清理了 libman 的缓存,但是问题没有解决。

PM> libman cache clean
Cache cleaned.

PM> libman clean
libman : libman.json was not  `found:C:\Users\user\source\repos\BlazorServerTestDynamicAccess\libman.json`

What can I do to resolve this issue?我该怎么做才能解决这个问题?

在此处输入图像描述

There are two ways to work around this:有两种方法可以解决此问题:

  1. Use a different console.使用不同的控制台。 As mentioned in the VS Developer Community issue:正如 VS 开发者社区问题中提到的:

But the Package Manager Console isn't a real command line, and doesn't provide the ability for a program to read input.但是 Package 管理器控制台不是真正的命令行,并且不提供程序读取输入的能力。

  1. Avoid any prompts for user input.避免任何用户输入提示。 For libman init , add the -y or --useDefault parameter.对于libman init ,添加-y--useDefault参数。 For libman install , make sure you have provided the provider name and destination path libman.json file (using the defaultProvider and defaultDestination properties), or as parameters (see libman install --help ).对于libman install ,请确保您提供了提供程序名称和目标路径 libman.json 文件(使用defaultProviderdefaultDestination属性),或作为参数(请参阅libman install --help )。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM