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.

Tool dependecies versioning issues

See original GitHub issue

When you build a tool that uses NetCore.App version that you don’t have installed the tool does not work at all. Example: I compiled the tool against NetCore.App 23911 and 23923 ( “Microsoft.NETCore.App”: { “type”: “platform”, “version”: “1.0.0-rc2-23911” } } ) and it did not work because: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\1.0.0-rc2-23924

When I compiled against 23924 the tool worked.

Since projects using tools don’t control what versions of dependency a tool is using it defeats the purpose of a shared framework since in the end you will need a version of a framework that corresponds to the dependency of the tool.

Also the message is quite confusing as well:

Could not load host policy library []

Issue Analytics

State:
Created 7 years ago
Comments:35 (25 by maintainers)

Top GitHub Comments

3reactions

muratgcommented, Apr 4, 2016

@blackdwarf We’ll be rolling newer versions between RC2 and RTM. Don’t we want to keep RC2 users be able to update the CLI so that they can use newer bits?

I feel like the current design is too restrictive. Ideally risk of breaking due to roll-forward is more acceptable than forcing folks to use exact versions.

0reactions

gkhanna79commented, Apr 7, 2016

This got fixed with https://github.com/dotnet/cli/pull/2316. Closing the issue.