Skip to content

Specify TypeScript version in solution rather than IDE. #7078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
simonvane opened this issue Feb 14, 2016 · 2 comments
Closed

Specify TypeScript version in solution rather than IDE. #7078

simonvane opened this issue Feb 14, 2016 · 2 comments
Labels
Question An issue which isn't directly actionable in code

Comments

@simonvane
Copy link

I would like to be able to upgrade to Visual Studio 2015 Update 1. The problem is that this will also update the TypeScript compiler to version 1.7. My code does not compile in version 1.7 for some reason so I cannot do this yet.

I think the TypeScript version should be a project option rather than tied to the IDE, that way I can upgrade Visual Studio 2015 to update 1 without having to fix any code and without having to upgrade the build server and get the whole team of devs to upgrade.

Is this possible?

Thank you.

@meritozh
Copy link

try to use npm to install a local special version, and use glup.js to compile TypeScript for you project.

or maybe you can try to replace the tsc.exe...

here are links can help you:
#1110
Use specific TypeScript compiler version in Visual Studio

@mhegazy
Copy link
Contributor

mhegazy commented Feb 16, 2016

you can set the TypeScriptToolsVersion in your project to 1.6 (or which ever version that works for you) and your project will always build against this version of the compiler. The IDE plugin in is not tied to the compiler version, so upgrading the IDE is possible without upgrading the compiler.
Note that since the IDE plugin version is different, you might get different errors from that at build time.

See https://github.com/Microsoft/TypeScript/wiki/Setting-Compiler-Options-in-MSBuild-projects#toolsversion for more information about toolsVersion

@mhegazy mhegazy added the Question An issue which isn't directly actionable in code label Feb 16, 2016
@mhegazy mhegazy closed this as completed Feb 16, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

3 participants