Is there a MSBuild parameter that tells VS which `tsconfig.json` to use?
See original GitHub issueI have 2 tsconfig.json files:
- tsconfig.full.json
- tsconfig.quick.json
I want to be able to point the VS2015 to either one of them accorting to the configuration parameters in *.targets
files. How can I do it?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:20 (11 by maintainers)
Top Results From Across the Web
Documentation - Compiler Options in MSBuild - TypeScript
Which compiler options are available in MSBuild projects. ... can configure TypeScript in two ways. Either via a tsconfig.json or via the project...
Read more >MSBuild Configuration - ticehurst.com
The tsconfig.json can either explicitly enumerate the input files (in the "includes" property) or it can exclude files that should not be compiled...
Read more >MSbuild typescript exclude folder - Stack Overflow
I have told VS to exclude the clientapps folder, and yet it the CompileTypeScriptWithTSConfig target still sees it and trys to compile it...
Read more >[WFR] Building a project does not honor the tsconfig.json ...
WIth the build action set to "none", the project properties page still recognizes there is a tsconfig.json and does not permit editing of...
Read more >MSBuild — .NET Core - Medium
We suggest you use tsconfig.json for your project when possible. To incorporate one into an existing project, including a new item to your...
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
Did anything ever happen with this? It’s 4 years later and VS2019 still can’t switch tsconfig files for different build scenarios.
For anyone else who ends up here I did find a (fairly nasty) workaround: https://stackoverflow.com/a/64705238 - basically @paulvanbrenk’s suggestion with added path overrides.
You can enable this by manually editing the project file, and adding
Configuration=Debug
to the itemgroup you want to include for debug. (Typing from memory, but there’s probably a PropertyGroup which works this way in your project.)