Microsoft releases TypeScript 1.0 RC; Visual Studio 2013 will support it

Microsoft is now offering programmers a chance to check out a near-final version of the company's TypeScript programming language. The release candidate version of TypeScript 1.0 is now available to download, along with news that it will be supported by Visual Studio 2013.

TypeScript was first announced by Microsoft in October 2012 and was made to extend the features of JavaScript. In a blog post today, S. Somasegar, the company's corporate vice president of the Developer Division, announced that since then TypeScript "has been a hit with developers both inside and outside Microsoft." He revealed that it has been used to help program many of the company's products and services, including parts of Bing, Xbox Music and Video and more.

Somasegar said that Visual Studio 2013 will include support for TypeScript starting with the Update 2 release. An early version was released a few weeks ago and today Microsoft made available Visual Studio 2013 Update 2 CTP2 for download, along with the release candidate version of Team Foundation Server 2013.

The blog post goes over some of the new features and improvements that will be a part of VS2013 Update 2, such as a full-featured JSON editor, a way to auto-create a Windows Azure Web Site and more.

Source: Microsoft | Image via Microsoft

Report a problem with article
Previous Story

Microsoft granted U.S. patent for Xbox One case design

Next Story

HTC promises new Windows Phones are on the way - but when?

8 Comments

Commenting is disabled on this article.

Maybe it's just me, but I hate the idea of having the final version of some software (VS Update 2 in this case) ship with so-called RC components. It's one thing to require security updates over time, but unfinished products, IMO, should never be included in any final version of something. If I wanted TypeScript, I'd much prefer to be able to download *it* separately, and have *it* ship with the proper VS plugins--even if *that* is an RC.

Nitpicking, maybe, but I like to be able to lock down my dev environments. Otherwise, such moving targets make things difficult to maintain over time.

what TypeScript does is to reinterpret javascript in a "more standard way of code". For example : in Typescript : "class SomeClass {" is just "var SomeClass = (function () {"

So, for somebody that is seasoned with javascript, TypeScript is just an annoying middleware.

There is no reason whatsoever why we must have separate languages for server and client side. I don't think that we need another language. Just limit C# to safe methods and allow it to run on client side. JavaScript must die just like VBScript.

EJocys said,
Just limit C# to safe methods and allow it to run on client side. JavaScript must die just like VBScript.
It is going to be awhile before another language picks up steam universally in browsers. A stripped down, "safe" C# would be as bad as VBScript (perhaps with a better syntax) as a result, if not worse because people would be confused by the incongruity between versions of the language.

There is no reason that client side languages need to be so loosely typed, but C# has too much political pressure behind it to be a realistic candidate. In fact, that's what makes TypeScript so interesting because you get C#-like features that simply get compiled into JavaScript for clients. Frankly, I think that that approach is the way to go: allow a strongly typed language to be compiled into JavaScript, and C# (now that it has lambda support) would or even F# would be great for that.

That's nice to hear!

I think either this or Dart are desperately needed to componentize large code bases with Javascript, depending on taste and needs. Type safety can also help a LOT in maintaining code.

Nice stop gap solutions in wait for ECMAScript 6 to be adopted as "the next Javascript".

Edited by Northgrove, Feb 26 2014, 12:03pm :

Excellent news.

We've been using it at work for the past 12 months on a couple of internal projects- so good, and with more third party libraries being supported all the time it can only get better

Hopefully the full 1.0 release is coming shortly.