Using LKG Develop Branch

Topics: Code Checkins, General
Apr 6, 2013 at 3:33 AM
I know there is documentation on how to use internal builds (i.e. develop branch's LKG). But, the next release includes a considerable amount of changes. I tried using the develop branch's LKG a week or so ago and followed the instructions to swap out the TypeScriptServices.js and I also swapped out the lib.d.ts since there is now generics support. But the VS TS editor was not working at all, specifically intellisense. Does the latest develop branch contain to many changes to play around with the latest LKG due in VS? Are we able to swap out with the latest compiler etc. If so how do I do so or do we have to wait for an official release?

Keep in mind that I just download the source code for the develop branch's LGK and copied and replaced the TypeScriptService.js and lib.d.ts in the installed directory. Do I need to follow the other method in the instructions to download from GitHub and compile myself, etc.?

Please help
Apr 6, 2013 at 7:38 AM
I doubt you can do it. I recently upgraded my own editor (Cats) from 0.8.x to the 0.9.x branch and noticed:

1) The language services api has undergone some changes that are not backwards compatible (they are however changes for the better I think).

2) Some of the methods are broken (they typically don't return all required info)

3) Some of the methods even have dummy implementations like "return [];" instead of returning the actual data

The standalone compiler (tsc) in the develop branch is in a better shape. It at least compiles most code that contain generics and you can even run it afterwards. So I guess that is right now the easiest way to experiment with generics.
Apr 8, 2013 at 3:33 PM
@djarekg - exactly what jbaroncom says. The 0.9.0 work in 'develop' is still in heavy flux, and the language service API is changing as part of that. We're using a completely different approach to the language service now, and now that we've moved to it, things should start settling down. We're looking into ways to make it easier to try it out the latest 'develop', like making an alpha version of the TypeScript Visual Studio plugin available. We'll hopefully have more info on that in a couple weeks.