Installing C# Dependencies when debugging node project.
See original GitHub issueEnvironment data
dotnet --info
output:
.NET Core SDK (reflecting any global.json):
Version: 2.1.302
Commit: 9048955601
Runtime Environment:
OS Name: Windows
OS Version: 10.0.17134
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.302\
Host (useful for support):
Version: 2.1.2
Commit: 811c3ce6c0
.NET Core SDKs installed:
2.1.200 [C:\Program Files\dotnet\sdk]
2.1.302 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
VS Code version:
[Window Title]
Visual Studio Code
[Main Instruction]
Visual Studio Code
[Content]
Version: 1.27.2 (user setup)
Commit: f46c4c469d6e6d8c46f268d1553c5dc4b475840f
Date: 2018-09-12T16:17:45.060Z
Electron: 2.0.7
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
[OK] [Copy]
C# Extension version: 1.16.1
Steps to reproduce
- Open a node project.
- Configure a
type: 'node'
project inlaunch.json
. - Press F5 to begin debugging.
- –> Notice that Output window says it is installing C# dependencies.
- Disable C# extension.
- Repeat step (3).
- –> Notice that the project correctly starts debugging.
Expected behavior
When debugging a non-C# project, C# extension doesn’t install a bunch of stuff onto my system before letting me debug my project.
Actual behavior
C# extension interrupts my process and makes me install a bunch of stuff that I will not be using in current debugging session.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Setting up git npm dependency for debugging - Stack Overflow
jsx Module build failed (from /mnt/c/Users/User/projects/current/client/node_modules/babel-loader/lib/index.js): Error: Plugin/Preset files are ...
Read more >How to Get Started with Debugging Node.js Applications
The most common way to debug Node.js code is by logging to the console ... into the nodejs-debugging directory and install the dependencies:....
Read more >Debug Node.js Apps using Visual Studio Code
Setting up a project for Node.js debugging is straightforward with VS Code providing ... To terminate nodemon, press Ctrl+C in the Integrated Terminal....
Read more >Running and debugging Node.js - CLion - JetBrains
In the embedded Terminal ( Alt+F12 ) , type npm install --save-dev nodemon or yarn add nodemon --dev to install nodemon as a...
Read more >debug - npm
js core's debugging technique. Works in Node.js and web browsers. Installation. $ npm install debug. Usage. debug ...
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
I am facing the same phenomenon. I created a Node.js project from scratch. When I pressed F5, before configuring any run task, it went into:
`Installing C# dependencies… Platform: win32, x86_64
Downloading package ‘OmniSharp for Windows (.NET 4.6 / x64)’ (31021 KB)… Done! Installing package ‘OmniSharp for Windows (.NET 4.6 / x64)’
Downloading package ‘.NET Core Debugger (Windows / x64)’ (43046 KB)… Done! Installing package ‘.NET Core Debugger (Windows / x64)’
Downloading package ‘Razor Language Server (Windows / x64)’ (46894 KB)… Done! Installing package ‘Razor Language Server (Windows / x64)’
Finished`
@MicahZoltu Yup. It will do it once, and then it is done.
This issue has been fixed in 1.18 (see #2658). So I will resolve this as a duplicate