Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Connect-wpf sample app not running because cannot find Microsoft.DotNet.Arcade.Sdk #2582

Open
2 tasks done
c1sc0 opened this issue Dec 29, 2022 · 3 comments · May be fixed by #3724
Open
2 tasks done

Connect-wpf sample app not running because cannot find Microsoft.DotNet.Arcade.Sdk #2582

c1sc0 opened this issue Dec 29, 2022 · 3 comments · May be fixed by #3724
Labels
Area-Documentation Improvements or additions to documentation bug Something isn't working Impact-Low

Comments

@c1sc0
Copy link

c1sc0 commented Dec 29, 2022

Describe the bug

I tried to run the provided sample app in VS Code, but it failed with an Omnisharp error:
Unable to find package Microsoft.DotNet.Arcade.Sdk with version (= 8.0.0-beta.22554.2)

Please complete the following:

.NET Interactive
© 2020 Microsoft Corporation
Version: 1.0.360602+9bf026dabac44a6256a65168fa93dcb7e2edcca4
Library version: 1.0.0-beta.22606.2+9bf026dabac44a6256a65168fa93dcb7e2edcca4
Build date: 2022-12-29T12:27:44.9947868Z

  • OS
    • Windows 11
  • Frontend
    • Visual Studio Code

Possible solution is to add the arcade's public nuget source to the nuget.config:

<add key="dotnet-eng" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json" />
@jonsequitur jonsequitur added bug Something isn't working Area-Documentation Improvements or additions to documentation labels Dec 29, 2022
@brettfo
Copy link
Member

brettfo commented Jan 3, 2023

This is certainly something we'd like to take a better look at, but in the meantime you should be able to copy that sample's directory somewhere outside of the repo and have it behave like normal. The Arcade SDK is simply an internal thing that all dotnet repos use to build that doesn't directly impact this scenario.

@michael-hawker
Copy link
Contributor

I also ran into this and copied out the folder, which let is compile and run, but then the notebook call to connect to the named pipe fails in VS Code:

Image

@jonsequitur
Copy link
Contributor

@michael-hawker This is unrelated to the original issue. The repo has been updated to use the new magic command API (#3567) so it will only run in VS Code Insiders until we publish the new API to VS Code stable.

@michael-hawker michael-hawker linked a pull request Oct 18, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Documentation Improvements or additions to documentation bug Something isn't working Impact-Low
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] Update Connect WPF Sample? michael-hawker/dotnet-interactive
4 participants
@jonsequitur @brettfo @c1sc0 @michael-hawker