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

dotnet commands fail with just core installed #2879

Closed
jonmill opened this Issue May 4, 2016 · 9 comments

Comments

Projects
None yet
3 participants
@jonmill

jonmill commented May 4, 2016

Steps to reproduce

  1. Download the .NET Core Installer (x64 and x86)
  2. Run dotnet --help (as specified by the output of running just dotnet)

Expected behavior

A help text is displayed

Actual behavior

"Did not find a suitable dotnet SDK at ''. Install dotnet SDK from "

Environment data

dotnet --info output:

Same error as above

@brthor

This comment has been minimized.

Show comment
Hide comment
@brthor

brthor May 4, 2016

Contributor

Another issue on this: #2697

Contributor

brthor commented May 4, 2016

Another issue on this: #2697

@jonmill jonmill changed the title from dotnet --help fails with just core installed to dotnet commands fail with just core installed May 4, 2016

@jonmill

This comment has been minimized.

Show comment
Hide comment
@jonmill

jonmill May 4, 2016

dotnet info doesn't work either :(

jonmill commented May 4, 2016

dotnet info doesn't work either :(

@jonmill

This comment has been minimized.

Show comment
Hide comment
@jonmill

jonmill May 4, 2016

ie. dotnet --version or dotnet --info

jonmill commented May 4, 2016

ie. dotnet --version or dotnet --info

@brthor

This comment has been minimized.

Show comment
Hide comment
@brthor

brthor May 4, 2016

Contributor

I don't know how these things can work without an SDK installed.

What should the help text say?

Contributor

brthor commented May 4, 2016

I don't know how these things can work without an SDK installed.

What should the help text say?

@jonmill

This comment has been minimized.

Show comment
Hide comment
@jonmill

jonmill May 4, 2016

The help text should describe what the dotnet command is and how to run it (like man dotnet) would. Once the SDK is installed, that can be expanded to include the SDK help.

Version should always be available to output the version of whatever is installed; if no SDK is installed the it should show the runner version. Once the SDK is installed, show the runner and SDK version. Same with info

jonmill commented May 4, 2016

The help text should describe what the dotnet command is and how to run it (like man dotnet) would. Once the SDK is installed, that can be expanded to include the SDK help.

Version should always be available to output the version of whatever is installed; if no SDK is installed the it should show the runner version. Once the SDK is installed, show the runner and SDK version. Same with info

@brthor

This comment has been minimized.

Show comment
Hide comment
@brthor

brthor May 4, 2016

Contributor

I think having --help also output dotnet app.dll like it does if you type dotnet alone is reasonable, but for --version, it's current beauty is that you get a string you can easily pipe to other commands, or easily use in a build.

Perhaps a --host-version would satisfy the need while preserving this scenario?

Contributor

brthor commented May 4, 2016

I think having --help also output dotnet app.dll like it does if you type dotnet alone is reasonable, but for --version, it's current beauty is that you get a string you can easily pipe to other commands, or easily use in a build.

Perhaps a --host-version would satisfy the need while preserving this scenario?

@jonmill

This comment has been minimized.

Show comment
Hide comment
@jonmill

jonmill May 4, 2016

for --version, it's current beauty is that you get a string you can easily pipe to other commands, or easily use in a build.

What use cases do we see in this area? If anything, this seems like a developer-centric scenario that would not be involved if just core were installed...

jonmill commented May 4, 2016

for --version, it's current beauty is that you get a string you can easily pipe to other commands, or easily use in a build.

What use cases do we see in this area? If anything, this seems like a developer-centric scenario that would not be involved if just core were installed...

@brthor

This comment has been minimized.

Show comment
Hide comment
@brthor

brthor May 4, 2016

Contributor

What use cases do we see in this area? If anything, this seems like a developer-centric scenario that would not be involved if just core were installed...

There was some conversation here #1607 (comment)

I see the use cases as primarily being around automation when verification needs to be done, or decisions made based on the current version of the cli being used.

With just core installed, the scenarios are likely different which is why I think a different option makes sense.

Contributor

brthor commented May 4, 2016

What use cases do we see in this area? If anything, this seems like a developer-centric scenario that would not be involved if just core were installed...

There was some conversation here #1607 (comment)

I see the use cases as primarily being around automation when verification needs to be done, or decisions made based on the current version of the cli being used.

With just core installed, the scenarios are likely different which is why I think a different option makes sense.

@TheRealPiotrP

This comment has been minimized.

Show comment
Hide comment
@TheRealPiotrP

TheRealPiotrP May 4, 2016

Contributor

This is a duplicate of #2697

Contributor

TheRealPiotrP commented May 4, 2016

This is a duplicate of #2697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment