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.

Need a way to turn BundledDotnetTools off for source-build

See original GitHub issue

Try to source-build up through the CLI.

There are a bunch of BundledDotnetTools that aren’t source-buildable (pretty much all of them).

We need to be able to turn these off during source-build. We could possibly use the same build variables we are currently using to not package the rest of ASP.NET in the SDK during source-build.

/cc @dseefeld @omajid @livarcocc @wli3

Issue Analytics

State:
Created 6 years ago
Comments:29 (23 by maintainers)

Top GitHub Comments

2reactions

leecowcommented, Mar 19, 2018

I can’t stress enough that any functionality which we consider to be in-box behavior needs to be included in source-build where ‘source-build’ means building from source with the bare minimum of bootstrap binaries needed to build and nothing required from the interwebs during the process.

1reaction

livarcocccommented, Apr 3, 2018

Our plan is to have a variable to turn off including bundled tools into the CLI. This change went in in the PR @omajid mentioned above.

Other than that, we will add special error messages when you try to dotnet <bundled_tool> and we don’t find the tool indicating the user to run dotnet install -g (which will only happen in source build tools).

Issue dotnet/cli#8861 is tracking adding that error message.

Given that this issue was tracking the OFF switch for the bundle tools and that went in, I am going to go ahead and close it.