You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.
When using the Bower Package Manager UI in VS2015, there isn't any real reaction when you click the "install" or "uninstall" buttons. The output window starts doing something but depending on how VS windowing is arranged this may not be obvious.
It would be great to at least have a cursor change or some obvious indicator that the button was successfully pressed. Similar to the way nuget package manager greys out while working on a request once it is received.
The text was updated successfully, but these errors were encountered:
If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.
By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.
Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!
When using the Bower Package Manager UI in VS2015, there isn't any real reaction when you click the "install" or "uninstall" buttons. The output window starts doing something but depending on how VS windowing is arranged this may not be obvious.
It would be great to at least have a cursor change or some obvious indicator that the button was successfully pressed. Similar to the way nuget package manager greys out while working on a request once it is received.
The text was updated successfully, but these errors were encountered: