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
DotNetCliToolReference restore does not seem to be implicit #5315
Comments
Hi @Aethon. Let's first confirm the right behavior and see if this is a doc issue or a product issue. @KathleenDollard @livarcocc can you guys help with this question? |
@rrelyea to comment. |
@rrelyea can you please help? |
There are no issues that I'm aware of in this space. I verified that quickly by running:
In logs I see
This indicates that the tools did get restored. Maybe the customer is facing some other problems? |
@Aethon can you provide more information on your problem? |
It was 2.0.x. I will try 2.1 and report that it works or gone a replication
path. Thanks!
…On Wed, Jun 27, 2018, 9:48 AM Kathleen Dollard ***@***.***> wrote:
@nkolev92 <https://github.com/nkolev92> did you test in a 2.0 version?
@Aethon <https://github.com/Aethon> could you install .NET Core 2.1 and
try this again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5315 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAnF0a6umFRUQ7ly4p9htn2ncaKGHC6Oks5uA5stgaJpZM4T7tox>
.
|
@Aethon, did it work? Thanks! |
Closing this issue due to the lack of response. |
At 2.0.4 and 2.0.7, DotNetCliToolReferences do not restore automatically. I have to run
dotnet restore
to get those to resolve. I cannot find documentation supporting this and have not found any issues raised. Is this expected behavior or should I file a bug? And which repo should the issue be reported in?Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: