Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"runtimes" folder isn't a valid TFM

See original GitHub issue

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.

Issue Analytics

State:
Created 5 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

adamralphcommented, Nov 3, 2018

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).

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.

0reactions

adamralphcommented, Nov 3, 2018

Released in alpha 11.