-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Discussion for: Packages containing tools are being renamed #1411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What exactly razor tools does? and when/why I could need it? |
https://github.com/aspnet/RazorTooling is part of what provides the IntelliSense for Razor files (*.cshtml) in Visual Studio. |
is this a visual studio only thing? shouldn't be part of visual studio instead of some tool package? Even if it's not only for VS, I don't see how an IDE feature has a place on |
About the announcement: A table would be more readable than an list (at least on mobile) |
|
@natemcmaster @Bartmax
It would be good to clarify that on readme.md for razor tooling Its also a bit behind on this rename and currently broken on ci build. |
The table contains status of the rename. |
@moozzyk I was more highlighting the typo. 😃 |
@MaximRouiller - I commented on @mikes-gh response and fixed the typo you pointed out to. |
@moozzyk sorry saw that now hidden on iPad layout. I guess tables aren't responsive on github |
I got this error
for this
|
@dodyg - haven't seen this. Can you provide more context? When/Where does this error happen? Is it during restore? Also what version of dotnet are you using? |
Year it was during I am using
|
This https://github.com/NuGet/NuGet.Client/blob/d74b04c1bdd3a6bb14b0ba6edd319e9c839c6eae/test/NuGet.Core.Tests/NuGet.ProjectModel.Test/PackageSpecReaderTests.cs#L203-L212 tells me that you in your project.json the tool did not have |
This issue is being closed because it has not been updated in 3 months. We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate. |
Discussion for aspnet/Announcements#172
The text was updated successfully, but these errors were encountered: