Visual Studio 2013 RC

Visual Studio 2013 RC

  • Comments 16

As part of the Visual Studio 2013 RC, we have included TypeScript 0.9.1.1, the most recent TypeScript release.  This will help us reach out to a broader audience of early adopters for feedback on TypeScript’s features, and help us shape TypeScript going forward.  If you haven’t had a chance to try out TypeScript, yet, please grab Visual Studio 2013 RC, and let us know what you think.

Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
  • not sure this is a good TypeScript release.  All of the reference path's seem to be bad now.

    i.e.

    /// <reference path="../Scripts/App/tsDefs/jquery.d.ts" />

    Error 1 Incorrect reference: file \"C:\Users\ME\AppData\Local\Temp\Scripts\App\tsDefs\jquery.d.ts\" does not exist C:\Users\ME\AppData\Local\Temp\TFSTemp\vctmp9068_895922.ts 1 1 vctmp9068_895922.ts

  • @Barrie, the reference paths are based off of the current file path for the source file.  It's possible this file has been opened but not yet saved.  If you save this file to a location for your project, where your jquery.d.ts is relative to, do you still see this error?

  • I see what you're saying, but this wasn't a new source file.  It's been in my project for some time.  I had simply changed a few lines of code.  I then opened and compiled the file in VS2012 and it worked as expected.  They should both be using the same version of TS so I'm not sure what's going on.

  • i'm surprised that this bug wasn't visible to you guys until I re-reported it:

    typescript.codeplex.com/.../1550

    from my perspective, this should be a showstopper as it effectively breaks typescript IDE integration once it occurs.  (and it occurs *all* the time in active use)

  • just making sure we're all on the same page...

    Problem: I'm saving an existing TS file in a TFS controlled project and receiving some bad reference errors.

    The diagnosis so far has been:

    1.  I'm not saving the file.

    2.  The file is not in my project.

    3.  It's working as expected.

    Now, since we're all developers here, I can appreciate your diagnoses as being perfectly reasonable from your perspective.  In fact, I believe it's not TS that is the problem but something wonky in VS2013 RC.  I've been using VS2012 and VS2013 Preview interchangeably up to today without experiencing this issue.  Immediately after I upgraded to today's posting of VS2013 RC, the first compile I made resulted in this error.  I might have reported the error in the VS2013 forumns, but they likely would have redirected me here.  Perhaps it's a spurious error that I'll not experience again.  So, perhaps it's best to let this issue rest until more devs install the new RC and watch if

    it's a common experience.

    Either way,

    thanks for the suggestions.  ;-)

  • As long as we cannot use TS to develop Windows Store apps, its useless to me. Until then I will keep developing using CoffeeScript.

  • @philk:  I don't think you understand what Typescript is.  it compiles directly to Javascript, as does CoffeScript.  So whatever you could do in coffescript you can do in typescript.    

    Typescript provides build-time type safety to javascript.  That's it.  (and that is a very compelling reason to use it!)  

  • I lost TypeScript debugging in VS when I upgraded to VS 2013 RC. Am I the only one?

  • TS debugging seems fine here, both in VS2012 and VS2013 RC

  • @Barrie

    That is curious.  And before, were you also using the TypeScript 0.9.1.1 release?  That's what is in the RC.  If you're still having the issue, can you log a report on the issue tracker (typescript.codeplex.com/.../Create), if you haven't already.

    @philk

    There is a Windows 8 sample you could use until we support the Windows Store app development more completely.  You can find it at the bottom of the Samples page here: www.typescriptlang.org/Samples

  • @philk check out a tutorial I whipped up for using TS to build a Win8.1 app: www.youtube.com/watch

  • @Jonathan Turner

    I have not re-experienced the problem.  In fact, after reading some of the resolutions to issues on where to place various lines in the project file, I am fully functional with debugging TS files, deploying JS files that aren't in the project and generally everything.  As long as those project lines are in the magic order, everything works as advertised.  So, I'm happy.  Congrats on making a great product.  I look forward to the release.

  • I have visual studio 2012 installed and Visual studio 2013.

    I create a website, I want to create a typescript file (add new file). I don;t see typescript.

    The only time I have seen Typescript working was with Web Essentials. I cannot get this think working.

    Please fix it, this is the release candidate not a beta version.

    Really put some effort into it, listen to developers and just fix it, even beta's should do something.

  • Visual Studio 2012 Update 3 + TypeScript 0.9.1.1 bug here.

    TypeScript is not compiling, not updating the corresponding js file...

  • I like TypeScript and hope that Typescript features end up in Ecmascript. Especially type annotations and declare (to tame the global object).

    But it would be incredibly useful if Typescript could align with ES6/7  proposals before version 1.0. Especially for modules. Bit of a pain but in the long run will pay off.

Page 1 of 2 (16 items) 12