question-mark
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.

Extension libraries reference dependencies not found in NuGet feeds

See original GitHub issue

Describe the bug

First of all: Thanks for your great work. Have been using dotnet interactive a lot since the VSCode integration was released and it is a joy to work with ❤❤❤

I just found a little thing. Referencing the packages meant to build extensions as documented in the main Readme (eg. Microsoft.DotNet.Interactive, Microsoft.DotNet.Interactive.Formatting, etc) leads to failing project restores.

Dependencies like System.CommandLine can be fixed when replicating the NuGet.config used in the dotnet interactive repo. Dependencies like FSAutocomplete.Core cannot be fixed as they do not exist in any feeds but only as project references.

I created a repository with two configurations the main branch has a working version of the plugin using your NuGet.config. The broken-references branch uses the global standard. If you want to test this you first have to clean your nuget cache because otherwise it seems as if it would work nicely (which it doesn’t).

I’m working on another extension where the problem is a bit more severe. This Deedle formatter extension is currently blocked from upgrading the packages because I can’t find a workaround for dependencies like FSAutocomplete.Core.

I’m totally fine with using the custom NuGet.config. I just think it should be reflected in the documentation. People using packages from nuget.org are kind of used to having it as the only repo - even for prerelease packages.

Please complete the following:

Which version of .NET Interactive are you using? There are a few ways to find this out:

Version: 1.0.151601+c44fed791093db19261c49b39d7d901e7983a3af Build date: 2020-10-16T22:22:16.0000000Z This doesn’t really connect to my issue though. My pinned .NET Core SDK version is 3.1.403

  • OS
    • Windows 10 (working on WSL2 - Ubuntu 20.04)
    • macOS
    • Linux (Please specify distro)
    • iOS
    • Android
  • Browser
    • Chrome
    • Edge
    • Firefox
    • Safari
    • Does not apply
  • Frontend
    • Jupyter Notebook
    • Jupyter Lab
    • nteract
    • Visual Studio Code
    • Other (please specify)

Screenshots

image

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
jonsequiturcommented, Oct 24, 2020

The goal is that all of the dependencies are on public NuGet going forward as we improve the extension story and docs. We’re trimming down the dependencies list and publishing an updated System.CommandLine soon.

Thanks for being an early adopter!

0reactions
WalternativEcommented, Jan 20, 2021

@Alkasai it’s not part of this repo (or Deedle for that matter because it’s currently one of my pet projects). You can find the repo here https://github.com/WalternativE/Deedle.DotNet.Interactive.Extension - there is also a short description on how to get it because it’s currently hosted on MyGet. If you have problems with it let me know (best would be in the repo). Hope this answers your question.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Nuget package installed but references not resolved
The problem was caused by a bug in Visual Studio where the references are not resolved correctly.
Read more >
Troubleshooting NuGet Package Restore in Visual Studio
This error occurs when you attempt to build a project that contains references to one or more NuGet packages, but those packages are...
Read more >
NuGet Package Dependency Resolution
This error occurs when one or more of the packages referenced in your project do not indicate that they support the project's target...
Read more >
Unable to resolve dependencies of NuGet packages
Solution · Clear the NuGet cache files. You do this in the following way: In the toolbar of Visual Studio, navigate to Tools...
Read more >
Referencing a Local Private NuGet Package in your Solution
I recently needed to add a local reference to my project and I couldn't quite figure out the best way to do it...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found