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.

Error acquiring .NET Core tooling (multiple issues)

See original GitHub issue

I have a deploy project (.deployproj file) that was created in visual studio and includes ARM templates. I get the following error when I open the project folder.

Downloading .NET Core tooling version(s) 2.2.5 ...... Error!
Failed to download .NET Core tooling 2.2.5:
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 205: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable


Error: /home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 205: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable
/home/ha/.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.7.0/assets/install scripts/dotnet-install.sh: line 147: VERSION_ID: unbound variable

vscode version information

Version: 1.38.1 Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0 Date: 2019-09-11T13:30:08.229Z Electron: 4.2.10 Chrome: 69.0.3497.128 Node.js: 10.11.0 V8: 6.9.427.31-electron.0 OS: Linux x64 5.3.1-arch1-1-ARCH

Issue Analytics

State:
Created 4 years ago
Comments:22 (11 by maintainers)

Top GitHub Comments

2reactions

StephenWeatherfordcommented, Nov 19, 2019

Thanks. BTW, you can use the new azureResourceManagerTools.languageServer.dotnetExePath setting to point to an existing dotnet.exe instead of us downloading it.

1reaction

StephenWeatherfordcommented, Nov 18, 2019

Never mind, I see in the original markdown that there is a slash, apparently markdown is interpreting the “.” as an escaped period.

Top Results From Across the Web

Troubleshoot .NET tool usage issues - Microsoft Learn

A common reason for failure is that the tool name isn't correct. This can happen because of mistyping, or because the tool has...

Error on installing .Net Core - Stack Overflow

Net Core over VS Community 2015 update 3. I am stuck with the following error. ... Error 0x80070642: Failed to acquire payload from: ......

Getting Started With Entity Framework Core - ASP.NET Core

In this example, you will use the command line tool from within Visual Studio Code. The first step is to create a folder...

Build and run an ASP.NET Core app in a container

Develop, build, and debug an ASP.NET Core app in a Docker container, using Visual Studio Code. ... Issue dotnet build command to build...

Deploying an ASP.NET core application with Elastic Beanstalk

NET Core SDK's dotnet command line tool to generate a basic .NET Core command line application, install dependencies, compile code, and run applications ......