Skip to content
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

Closed
bording opened this issue Nov 1, 2018 · 7 comments
Closed

"runtimes" folder isn't a valid TFM #64

bording opened this issue Nov 1, 2018 · 7 comments
Milestone

Comments

@bording
Copy link
Collaborator

bording commented Nov 1, 2018

I'm not sure if this causes any actual problem or not, but the current folder structure of the package might not be ideal:

image

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.

@bording bording changed the title "Runtimes" folder isn't a valid TFM "runtimes" folder isn't a valid TFM Nov 1, 2018
@adamralph adamralph added this to the 1.0.0 milestone Nov 1, 2018
@adamralph adamralph self-assigned this Nov 2, 2018
@adamralph
Copy link
Owner

Released in alpha 10.

@bording
Copy link
Collaborator Author

bording commented Nov 2, 2018

@adamralph I was looking at alpha 10 in NuGet Package Explorer and noticed the following:

image

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 MinVer folder would be a better idea, just to avoid any potential complications.

@adamralph
Copy link
Owner

adamralph commented Nov 2, 2018

Ah, yes, that is less than ideal. Perhaps a custom folder is indeed best. One more thought though: what if we acknowledge that the CLI is a .NET Core 2.1 app and put it in a tools TFM folder? NPE seems to like it:

@adamralph adamralph reopened this Nov 2, 2018
@bording
Copy link
Collaborator Author

bording commented Nov 2, 2018

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?

@adamralph
Copy link
Owner

Perhaps it's not the best idea. The best documentation I've found so far says:

Folder Description Action upon package install
tools Powershell scripts and programs accessible from the Package Manager Console The tools folder is added to the PATH environment variable for the Package Manager Console only (Specifically, not to the PATH as set for MSBuild when building the project).

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 dotnet MinVer.Cli.dll in the Package Manager Console, but it doesn't work because PATH can't be used in that way.

Let's go with your suggestion of a top level MinVer folder then.

@adamralph
Copy link
Owner

Looks good:

@adamralph
Copy link
Owner

adamralph commented Nov 3, 2018

Released in alpha 11.

@adamralph adamralph removed their assignment Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants