Request: add TypeScript support for UWP projects in Visual Studio

[carlpaten-ivadolabs]

It's not at all obvious right now how to:

1. Write a UWP app in TypeScript;
2. Debug that app.

A prepared template would be lovely for this.

---

Workaround for the debugging issues in VS 2015.2 and 2015.3 (s/o @minestarks):

I assume you're running in an English locale here, otherwise I don't think the workaround is applicable.

Close VS.
In an administrator command prompt:

cd %ProgramFiles(x86)%\msbuild\microsoft\visualstudio\v14.0\typescript
mkdir en
copy *.xaml en
copy TypeScript.Tasks.dll en\TypeScript.Tasks.resources.dll

Now open your UWP project again, the TS files should be visible and building when you build your project.

[mhegazy]

UWP projects are not currently supported for TS. we are working on enabling them, including type definitions, templates, and debugging.

[carlpaten-ivadolabs]

UWP projects are not currently supported for TS.

Could you clarify that somewhere in the documentation?

we are working on enabling them, including type definitions, templates, and debugging.

Exciting news!

[grork]

Do we have a time frame? I'm less bothered by full template support, but people have existing projects that were broken by Update 2/1.8.

[saschanaz]

TS works anyway on UWP when every compiled js file is added to project, while we have to build twice to run. Debug should just work, at least my projects do.

[lahloumehdi]

The bad thing is that TypeScript it worked perfectly with uwp/visual studio 2015 Update 1 and Typescript 1.7.6.

There was something broken after the update 2 of VS or the update of typescript (1.8>)

I have a very big UWP project that use TypeScript and I'm not able to upgrade VS or TypeScript because of to this issue ...

[saschanaz]

@lahloumehdi Does your problem also happen on VS2015 Update 3?

[lahloumehdi]

@saschanaz Unfortunately no.

[carlpaten-ivadolabs]

@lahloumehdi so the issue is fixed in VS2015 Update 3? Great news!

By the way, last time I checked this was broken in VS15 Preview 2. Any idea if it was fixed at some point?