-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
"runtimes" folder isn't a valid TFM #64
Comments
Released in alpha 10. |
@adamralph I was looking at alpha 10 in NuGet Package Explorer and noticed the following: It turns out that as part of the .NET Core Global Tool work, the tools folder also expects subfolders to be TFMs! Again, not sure if this would actually be a real problem (and possibly only if the PackageType metadata indicates it is a tool package), but I'm still wondering if a top-level |
That does seem like it might work, but I wonder if it's a good idea to put things in that folder structure when it's not actually a global tool? |
Perhaps it's not the best idea. The best documentation I've found so far says:
That implies that all the files in that folder should be suitable to appear in the Package Manager Console's PATH, and I don't think that's the case with this package. It would actually be quite nice to be able to run Let's go with your suggestion of a top level MinVer folder then. |
Released in alpha 11. |
I'm not sure if this causes any actual problem or not, but the current folder structure of the package might not be ideal:
NuGet expects folders underneath the
build
folder to be valid TFMs.It might be worth moving all of the MinVer.Cli bits into a new
MinVer
root folder in the package, and then update the path in MinVer.targets to be aware of the change.The text was updated successfully, but these errors were encountered: