Home Original page

GitHub - Mistrall/TypeScript.NET: .NET Library Ported to TypeScript (Typed JavaScript)

###A JavaScript Friendly .NET Library Ported to TypeScript

The intention of this project to to allow for the evolution of a .NET based TypeScript (and resultant JavaScript) library. Contributions are welcomed as the .NET Library (meaning it's class structure and classes, not necessarily its content) has a substantial amount of usefulness. With the open sourcing of .NET, TypeScript seems the most logical means to take advantage of it. Typing, generics, classes, modules, inheritance, all are required to make a resultant JavaScript library that takes advantage of this elegance.

Much inspiration comes from TypeScript itself and from libraries like linq.js. There is of course some variance away from .NET's convention (camelCase methods in favor of TitleCase) and some things simply have to be done different. "Extensions" as a feature might be one of the greatest additions to .NET that JavaScript doesn't have a plan for, but it does have some tricky equivalents.

If you have a .NET Library class that you want to see represented in TypeScript, submit it (as an issue), or contriubte it yourself! :)

Why should I use this, let alone TypeScript?

  1. It's 100% compatible with JavaScript. Currently TypeScript.NET's target is ES5, so legacy JavaScript won't work. Mainly because of accessors. But going forward, TypeScript is nearly the same as ES6 and you don't have to change your source code to target newer versions. :)

  2. TypeScript is lead by Anders Hejlsberg, the founder of C#. You will feel quite at home in TypeScript if you are a fan of typed languages (like C#), but at the same time you'll get all the flexibility and compatibility of JavaScript.

See http://www.typescriptlang.org/ for more information about the TypeScript language.

Also some more good info on WikiPedia: http://en.wikipedia.org/wiki/TypeScript.

  1. The benefits of intellisense and using an IDE for programming should be obvious especially if you are coding for a larger project. Typed compilation is less forgiving in a good way. You simply make much less mistakes in the long run. TypeScript might be the best answer to JavaScript yet. It's still JavaScript, but with many bonuses including a growing community. :)

  2. Most major IDE's and text editors now support TypeScript either built in, or via a plug-in:

  • Visual Studio 2013 (or greater)
  • WebStorm (recommended!)
  • Sublime Text

To name a few.

In my case, I use both Visual Studio and Web Storm to ensure quality.

  1. There's some really good and useful code here already, including a fully typed (with generics) Linq implementation. Take a look!

Usage

This library is meant to be flexible. So for a single project/package there are multiple versions of the result.

For example, System has the following files in the build directory:

/build/System.js
/build/System.min.js

Also if you would prefer to use AMD/Require.js you can use:

/amd/System.js
/amd/System.Linq.js

You can also see an example of how to use a shim:

Build

This project uses 'Gulp' to build the resultant JavaScript files.

Setup:

Simply install node.js. This should include npm (Node Package Manager). Then at any command prompt, type:

This will ensure you can type 'gulp' in any location.

Building

Then if you need to build an individual namespace/package, simply type gulp within that project folder (where there is a gulpfile.js).

If you want to make sure the entire solution is updated, typing gulp inside the gulp-tasks folder will build all registerd project folders.

IDE Support

WebStorm has a terminal and it's simply easy enough to type gulp when you need to build.

Visual Studio has an incredible set of tools for node and task runners. Here's one of them: https://visualstudiogallery.msdn.microsoft.com/8e1b4368-4afb-467a-bc13-9650572db708

Learn, Connect & Evolve

https://www.youtube.com/channel/UCG2QyAgVUEKSMBaC0Fkp5GQ

Ready for Beta Level Use

System.Linq: Nearly 100% of the original linq.js is present with some exceptions. There's no string to lamda conversion because it's unnecessary when using TypeScript. Enumerable is currently a static class with utility for calling Enumerable(collection). Instead it is more explicit by calling Enumerable.fromArray(array). Unit test coverage is ongoing. Please report any issues you might find and they will be fixed immediately.

Future

Planning to make this a bower and other package systems (easy) install.

Full documentation and references (dreaming).