Visual Studio "TypeScript Build" project properties versus tsconfig.json

[IanKemp]

If you have a C# project with TypeScript support enabled, and that project has a tsconfig.json file, navigating to to the "TypeScript Build" section of that project's properties results in a non-editable page with the message "One or more tsconfig.json files detected. Project properties are disabled.":

The implication is that VS project properties for TS, and tsconfig.json, are mutually exclusive.

• Why is this? Why can't that properties page be populated from the values in the tsconfig.json if present and there are no ancestor tsconfig files?
• Is using tsconfig.json deprecated in favour of controlling the TypeScript configuration from Visual Studio?

[mhegazy]

Why is this? Why can't that properties page be populated from the values in the tsconfig.json if present and there are no ancestor tsconfig files?

To enable that we need an editor that allows round-tripping from a json file, i.e. you edit the json file, ui changes, you edit the ui, the json file changes, including all required validations etc.. notice that the .json file is available for you to edit outside the property pages, but not the project file (.csproj) for instance.
We, the typescript team, have limited engineering resources and have to prioritize our deliverables. JS developers are usually familiar with JSON files, and with the support of schema, we believe the experience is better than what a property page can offer.

Is using tsconfig.json deprecated in favour of controlling the TypeScript configuration from Visual Studio?

Both are supported. but we recommend using a tsconfig.json moving on. we are not updating the UI in the project property pages, so using tsconfig.json will give you a better experience.

[typescript-bot]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.