user reports the following. bug verified by dino.
----
Just started using VS 2013 Update 2 RC (with build-in TypeScript support) and NTVS 1.0 Beta.
It seems that these two interact in non-optimal way:
1. When a TypeScript file is saved, the build-in TypeScript support in VS does some super-fast compilation of just that file (this seems to take only 50-100ms)
2. When a TypeScript file is saved AND application is running/debugging in Node, the NTVS runs full project TypeScript compilation using tcs.exe (this takes several seconds even with empty project, and would likely increase to 10+ seconds with real project).
So, the #2 seems unnecessary for (all/most) edits, slows things down about two orders of magnitude, and the feature should be removed?
----
Just started using VS 2013 Update 2 RC (with build-in TypeScript support) and NTVS 1.0 Beta.
It seems that these two interact in non-optimal way:
1. When a TypeScript file is saved, the build-in TypeScript support in VS does some super-fast compilation of just that file (this seems to take only 50-100ms)
2. When a TypeScript file is saved AND application is running/debugging in Node, the NTVS runs full project TypeScript compilation using tcs.exe (this takes several seconds even with empty project, and would likely increase to 10+ seconds with real project).
So, the #2 seems unnecessary for (all/most) edits, slows things down about two orders of magnitude, and the feature should be removed?