-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add a dotnet install runtime command #7686
Comments
Please Anyone clear my doubt. |
@MuthiyalLakshmi I hope the link helps. @livarcocc @blackdwarf we need to better manage this experience in 2.0. Nothing's really preventing us from providing a link... or offering to download & install the framework. |
Yes. We have talked about it a couple of times. How do you want to track that improvement? |
sry its not working having the same problem showing again and again
…On 06-Feb-2017 11:17 pm, "Livar" ***@***.***> wrote:
Yes. We have talked about it a couple of times. How do you want to track
that improvement?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/dotnet/cli/issues/5594#issuecomment-277757847>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AYZN1gB8pv8vc1N13L4We7y3GTVfwboKks5rZ1zBgaJpZM4L33a3>
.
|
@MuthiyalLakshmi on the link that @piotrpMSFT shared you should be able to find an installer for the 1.1.0 runtime. Install that and try to rerun. It should clear up the error message. @livarcocc the issue should be in the core-setup repo, right? This message is from the host? We should still leave this one around for tracking. |
@blackdwarf Yes, the message is in the host, however, maybe the CLI could augment this experience somehow, like, offering to install the missing shared framework. |
@livarcocc this is a part of the overall plans for 2.0; if we have a CLI gesture for the user to install a runtime from the CLI command, then yes, that piece should be lit up here as well. We need a design and UX. Imagine what I will be doing. :) |
We have been talking about a |
#14962 Closing as a duplicate of this item. Route all feedback there |
The text was updated successfully, but these errors were encountered: