It is unclear to me how tsconfig.json is used in Visual Studio 2015

It is unclear to me how tsconfig.json is used in Visual Studio 2015. And what happens when the TypeScript panel in the Project Properties conflicts? Does switching to use tsconfig.json kill features like Save-On-Compile?

[mhegazy]

Sorry for the confusion.. we are working on cleaning this up. An easy way to think of this, is a project file (.csprox, .jsproj, .vbproj or .njsproj) and a tsconfig.json are mutually exclusive. if you have a project file the tsconfig is ignored. if you want to use a tsconfig file, do not use a project.

In the future, i would see us adding an option in the project property pages to allow you to use tsconfig or not, and if so, the project property pages will all be grayed out..

[paulvanbrenk]

tsconfig.json is only supported in Asp.net 5 and Cordova projects currently. Since neither has a Project Properties for TypeScript they won't conflict, and tsconfig.json will take precedence.

To enable Compiler on Save, you need to enable Compile on Save for files that are not part of a project, in the Tools/Options/Text Editor/TypeScript.

We plan to have more comprehensive support in 1.6.

[paulvanbrenk]

Closing this as we're using #4161 to track this.

[ltlombardi]

Jan 2018, this is still a issue. Every single official documentation and blog talks about tsconfig.json file, and nothing about how to configure the same in the project.
For example:
https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/

[mhegazy]

@ltlombardi i am not sure i understand your issue. this issue has been closed over 3 years ago. Please file a new issue, and include enough context for use to investigate

[ltlombardi]

@mhegazy thank you. ;-) I'll do that