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.

dotnet tool install requires full SDK

See original GitHub issue

Steps to reproduce

install dotnet core runtime https://www.microsoft.com/net/download/thank-you/dotnet-runtime-2.1.3-windows-hosting-bundle-installer
run dotnet tool install -g sometool

Expected behavior

tool will be installed

Actual behavior

It is asking to install the sdk

Environment data

dotnet --info output:

Host (useful for support):
  Version: 2.1.3
  Commit:  124038c13e

.NET Core SDKs installed:
  No SDKs were found.

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

I have a couple of CLI tools that I would like to use in production (mainly for deployment) and I am unable to install the SDK. Is there any way to get this to work with just the runtime (with powershell or something)?

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

jzabroskicommented, Jan 24, 2022

@livarcocc Interesting. What is your recommendation for projects like Entity Framework and FluentMigrator that basically recommend running these in production? Ha.

CC @ajcvickers https://docs.microsoft.com/en-us/ef/core/cli/dotnet#aspnet-core-environment

1reaction

wli3commented, Aug 23, 2018

Thank you for the issue!

dotnet tools are not intent to be used in production. It is for development. dotnet tools is aim to solve the delivery of the development tools. For production delivery, the requirement is different.
if you want to run your app in production, you could dotnet publish, copy the whole folder, and then use dotnet __.dll in production.