tsconfig breaks TSC in VS 2015

[glatzert]

Placing a tsconfig.json file inside of an ASP.NET vNext Project (beta6) will break tsc.
It will not produce any output.or overwrite files or whatever else.
Removing the tsconfig.json fixes the automatic compilation.

[mhegazy]

@paulvanbrenk can you take a look/provide a workaround here?

[paulvanbrenk]

only the following setup is supported at this time

/projectroot
    /wwwroot
    /scripts
        - tsconfig.json
        - ts files

For compile on save to work you need to enable Compile on save for files that are not part of a project, in tools/options/text editor/typescript/project

hope this helps

[mhegazy]

also to note, this is something we are still working on. TypeScript 1.5 release went out before ASP.Net release, so there are some missing support that we need to update in the next release. sorry for the hassle.

[glatzert]

Well okay - the currently supported setup works - but orignially we wanted to go by one file per Module, which is not accomplishable without multiple tsconfig files, but with a buildstep - so we will use that as a Workaround.
Thanks

[paulvanbrenk]

Can you describe how you would like to setup your project to do 'one file per module', so we can take that into account when we improve the tsconfig experience in the near future.

[glatzert]

Well we'd like to use something like this:

 /projectroot
    /scripts
        /module1
            - sourceFile1.ts
            - sourceFile2.ts
            - sourceFile3.ts
            - tsconfig.json
        /module2
            - sourceFile4.ts
            - sourceFile5.ts
            - tsconfig.json
        /module3
            - sourceFile6.ts
            - sourceFile7.ts
            - tsconfig.json

Which should be build into this:

 /projectroot
    /wwwroot/js
        -Module1.js/map.js/min.js
        -Module2.js/map.js/min.js
        -Module3.js/map.js/min.js

Currently we can only make one js file per ts file or one js file with all the code. (The latter `out: "../wwwroot/js/Output.js"´ seems not to work either.)

[paulvanbrenk]

@glatzert thanks, this is good feedback.

You should be able to enable this scenario right now using a grunt task, however I don't think there is any good information available right now (I couldn't find any just now). And I have to make sure that works with compile on save. I'll add some information to the ASP.NET + TypeScript wiki this week.