When building ...\src\Microsoft.DotNet.Interactive.Js\dist is not found
See original GitHub issuePulled the repo, executed ensure-symlinks, opened the sln file with visual studio 2019.
When building dotnet-interactive with visual studio 2019 it fails with
1>CSC : error CS1566: Error reading resource 'Microsoft.DotNet.Interactive.App.resources.dotnet-interactive.js' -- 'Could not find a part of the path 'A:\develop\Training\interactive\src\Microsoft.DotNet.Interactive.Js\dist\dotnet-interactive.js'.'
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Missing folder and files · Issue #2128 · dotnet/interactive
Missing folder and files #2128 ... The latest master has missing ... When building ...\src\Microsoft.DotNet.Interactive.Js\dist is not found ...
Read more >"dotnet restore --interactive" doesn't work with Azure Artifacts
When I tried dotnet restore --configfile .\.nuget\NuGet.Config --interactive it did prompt me. I could login in and everything worked! I'm not ...
Read more >.NET Interactive is here! | .NET Notebooks Preview 2 ...
Today we are excited to announce Preview 2 of the .NET Notebook experience. Preview 2 includes C#, F#, and PowerShell support.
Read more >Exploring .NET interactive notebooks with VS Code
In this post I explore .NET Interaction Notebooks for VS Code, discuss the options, and show how to get started.
Read more >Microsoft.dotnet-interactive 1.0.440301
Version Downloads Last updated
1.0.440301 22,297 17 days ago
1.0.431302 69,510 2 months ago
1.0.430802 8,036 2 months ago
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
DEVELOPER-GUIDE.md
has been updatedFrom my side, it is fine to close it.
I don’t think making the build work without symlink support is something the dev team can prioritize. Is there any additional work to be done here or can we close this?