Extension bundled with nuget package no longer loading correctly
See original GitHub issueDescribe the bug
A library I work on bundles with it an extension.dib
, following the guidance in this document: https://github.com/dotnet/interactive/tree/5df931c08ec22bb0d01c8082e2339b80a17f4a30/samples/extensions/RandomNumber
We reference the bundled extension here: https://github.com/hypar-io/Elements/blob/ea629a7ec2d873cbf680298a6af69a00fd59ccbf/Elements/src/Elements.csproj#L60
Until recently, I would install the library in a notebook using #r “nuget: Hypar.Elements, *-*“
and it would both install the package and import the extension. The using
s from the .dib
were automatically imported, I had access to the variables/methods defined, and custom Formatter
s would be registered for me to use right away.
Recently, this stopped working in interactive notebooks in VS Code. I still receive the message Loading extension script from /Users/andrewheumann/.nuget/packages/hypar.elements/1.4.0-alpha.2/interactive-extensions/dotnet/extension.dib
, and I can verify that that file exists. However, none of the using
s are imported, and none of the variables / methods / Formatter
s are available. This video shows how this used to work.
Let me know if I’ve missed something about how this is supposed to work, or if this is the wrong place to report this issue.
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about
magic command. ):
Version: 1.0.355307+4cc71ae4e275fd80852b9c2faa317bc3a0033d2c
Library version: 1.0.0-beta.22553.7+4cc71ae4e275fd80852b9c2faa317bc3a0033d2c
Build date: 2022-11-04T02:20:42.0000000Z
- OS
- Windows 11
- Windows 10
- macOS
- Linux (Please specify distro)
- iOS
- Android
- Browser
- Chrome
- Edge
- Firefox
- Safari
- Frontend
- Jupyter Notebook
- Jupyter Lab
- nteract
- Visual Studio Code
- Visual Studio Code Insiders
- Visual Studio
- Other (please specify)
Screenshots
Issue Analytics
- State:
- Created 10 months ago
- Comments:8 (3 by maintainers)
Top GitHub Comments
This has been fixed. The fix is in Insiders and should be rolling out in Stable in the next couple of days.
AMAZING!!! thank you so much @jonsequitur