Skip to content

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

Closed
moozzyk opened this issue Apr 27, 2016 · 16 comments
Closed

Discussion for: Packages containing tools are being renamed #1411

moozzyk opened this issue Apr 27, 2016 · 16 comments

Comments

@moozzyk
Copy link
Contributor

moozzyk commented Apr 27, 2016

Discussion for aspnet/Announcements#172

@Bartmax
Copy link

Bartmax commented Apr 27, 2016

What exactly razor tools does? and when/why I could need it?

@muratg muratg added this to the Discussions milestone Apr 27, 2016
@natemcmaster
Copy link
Contributor

https://github.com/aspnet/RazorTooling is part of what provides the IntelliSense for Razor files (*.cshtml) in Visual Studio.

@Bartmax
Copy link

Bartmax commented Apr 27, 2016

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 project.json

@304NotModified
Copy link

304NotModified commented Apr 27, 2016

About the announcement: A table would be more readable than an list (at least on mobile)

@MaximRouiller
Copy link

otnet-razor-tooling? 😜

@mikes-gh
Copy link
Contributor

@natemcmaster @Bartmax
I think dotnet-razor-tooling is for Razor intellisense for TagHelpers to be precise.

@NTaylorMullen

FYI: dotnet-razor-tooling is only for TagHelper IntelliSense.

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.

@moozzyk
Copy link
Contributor Author

moozzyk commented Apr 28, 2016

The table contains status of the rename. dotnet-razor-tooling and dotnet-aspnet-codegenerator renames are still in progress.

@MaximRouiller
Copy link

@moozzyk I was more highlighting the typo. 😃

@moozzyk
Copy link
Contributor Author

moozzyk commented Apr 28, 2016

@MaximRouiller - I commented on @mikes-gh response and fixed the typo you pointed out to.

@mikes-gh
Copy link
Contributor

mikes-gh commented Apr 28, 2016

@moozzyk sorry saw that now hidden on iPad layout. I guess tables aren't responsive on github

@dodyg
Copy link

dodyg commented Apr 29, 2016

I got this error

tools must specify a version range

for this

"tools": {
  "Microsoft.EntityFrameworkCore.Tools": {
    "version": "1.0.0-*",
    "imports": "portable-net451+win8"
  }
},
"dependencies": {
  "Microsoft.EntityFrameworkCore.Tools": {
    "version": "1.0.0-*",
    "type": "build"
  }
}

@MaximRouiller
Copy link

@moozzyk
Copy link
Contributor Author

moozzyk commented Apr 29, 2016

@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?

@dodyg
Copy link

dodyg commented Apr 29, 2016

Year it was during dotnet restore. The problem goes away now. I don't really know what happened.

I am using

.NET Command Line Tools (1.0.0-rc2-002498)

Product Information:
 Version:     1.0.0-rc2-002498
 Commit Sha:  55e561bfb3

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64

@moozzyk
Copy link
Contributor Author

moozzyk commented Apr 29, 2016

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 version. It wouldn't get away on its own though. If you see this again show your project.json file and I will try to repro.

@aspnet-hello
Copy link

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.

@aspnet-hello aspnet-hello removed this from the Discussions milestone Dec 31, 2017
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants