Build on context menu not working

Open
#2,212 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, typescript
Domain
build-system, tooling

Research direction

Start at the context-menu Build path for tsconfig.json and inspect how it resolves the TypeScript compiler; compare that lookup with the missing tsc.exe path shown in the output. Reproduce the listed steps, and consider it done when Build launches the available compiler and completes the tsconfig.json build without the missing-file error.

Written by the indexing model from the issue text.

Description

Expected

Command on context menu Build builds .ts files.

Actual Behavior

Command fails to execute as tsc.exe file no longer exists.

  • NTVS Version: 1.5.10717.1 Commit Hash:c892fc71536f0cf66cc3c34359ae0b7e86fc0d6d
  • Visual Studio Version: 16.3.0 Preview 2.0
  • Node.js Version: 10.4.1
Steps to Reproduce
  1. Create a new folder on the file explorer.
  2. Open Visual Studio > File > Open > Folder
  3. Choose the newly created folder.
  4. Add a tsconfig.json file.
  5. Right click the tsconfig.json > Build.
  6. See error on output Tsc.
=== Build Started: C:\Program Files (x86)\Microsoft SDKs\TypeScript\3.6\tsc.exe -p "C:\Users\user\source\repos\OpenFolderError\tsconfig.json" ===
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Microsoft.VisualStudioTools.Project.ProcessOutput..ctor(Process process, Redirector redirector)
Error - Failed to start 'C:\Program Files (x86)\Microsoft SDKs\TypeScript\3.6\tsc.exe'

image

Dominant language
C#
Stars
1.8k
Forks
355
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/nodejstools

All issues in microsoft/nodejstools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.