Skip to main content

TypeScript introduction

In newer web application development we are more and more diving into client side scripts. Slowly AJAX calls are completely or at least mostly replacing regular post backs for rich user experience. Somewhere we are dealing HTMLs returns or just interacting with model but with time we are ending up writing lot of JavaScript on pages or dedicated JavaScript files.

After starting project, in short of span of time we are ending up with lot of scripts. Writing those script itself is problematic process as we do not get any type safety and on execution only we can know we have missed typed or added some variable in place of some other type. Mostly through comments only we are understanding the code association with pages unless we put JavaScript in respective pages or with naming JS according to respective page names. I know we can use some OOPS concept or JS framework like Backbone, Knockout etc. to manage things through MVC or MVVM approach. Those are really good way to handle JavaScript but we do not get any type safety as it is JavaScript.

I am a really great fan of OOPS concept but have never tried on JavaScript. May be I do not understand JavaScript much or too lazy to write extra script to manage it. I was looking for solution for easy and happy scripting then I come to know TypeScript.

What is TypeScript?

TypeScript is an open source scripting language and super-set of JavaScript with type safety. That means whatever JavaScript script code we have written till now is TypeScript only. Oh! what is the point then if it is TypeScript and how that type safety works. JavaScript is subset of TypeScript, where all JavaScript code will workout without doing anything extra but for taking advantage of TypeScript we can follow there guideline.

What are guidelines of TypeScript and how to code?

It is more of like JScript .NET or could be related with C#. It is pretty simple to catch up with TypeScript if we have worked on any OOP languages. It is having classes, interfaces, modules (namespace), generics, type declaration, most lovely compile time checks etc. 
For getting started with we can look into

How it works?

The extension of JavaScript is ts. It comes with tsc compiler which could be downloaded from The compiler compiles the ts file into JavaScript files to have compatibility with any browser and doing every hard work for us. 

TypeScript helping tools 

For taking advantage of various JavaScript libraries, it is having huge list of type definition which could be found on
By importing those we can have type safety checks. Ex: jQuery has lot of functionality with various types declared in it. By importing the definition we can have intellisense with type checks.
Web Essential is an extension of Visual Studio through which we can have JavaScript file generation at a time of writing only, which you might have seen from Playground link.

TypeLITE is a tool to generate up TypeScript interfaces according to server side classes or models.

Popular posts from this blog

Architecture solution composting Repository Pattern, Unit Of Work, Dependency Injection, Factory Pattern and others

Project architecture is like garden, we plant the things in certain order and eventually they grow in similar manner. If things are planted well then they will all look(work) great and easier to manage. If they grow as cumbersome it would difficult to maintain and with time more problems would be happening in maintenance.

There is no any fixed or known approach to decide project architecture and specially with Agile Methodology. In Agile Methodology, we cannot predict how our end products will look like similarly we cannot say a certain architecture will fit well for entire development lifespan for project. So, the best thing is to modify the architecture as per our application growth. I understand that it sounds good but will be far more problematic with actual development. If it is left as it is then more problems will arise with time. Just think about moving plant vs a full grown tree.

Coming to technical side, In this article, I will be explaining about the various techniques tha…

LDAP with ASP.Net Identity Core in MVC with project.json

Lightweight Directory Access Protocol (LDAP), the name itself explain it. An application protocol used over an IP network to access the distributed directory information service.

The first and foremost thing is to add references for consuming LDAP. This has to be done by adding reference from Global Assembly Cache (GAC) into project.json

"frameworks": { "net461": { "frameworkAssemblies": { "System.DirectoryServices": "", "System.DirectoryServices.AccountManagement": "" } } },
These System.DirectoryServices and System.DirectoryServices.AccountManagement references are used to consume LDAP functionality.

It is always better to have an abstraction for irrelevant items in consuming part. For an example, the application does not need to know about PrincipalContext or any other dependent items from those two references to make it extensible. So, we can begin with some bas…

Configuring Ninject, Asp.Net Identity UserManager, DataProtectorTokenProvider with Owin

It can be bit tricky to configure both Ninject and Asp.Net Identity UserManager if some value is expected from DI to configure UserManager. We will look into configuring both and also use OwinContext to get UserManager.

As usual, all configuration need to be done on Startup.cs. It is just a convention but can be used with different name, the important thing is to decorate class with following attribute to make it Owin start-up:

[assembly: OwinStartup(typeof(MyProject.Web.Startup))]
Ninject configuration

Configuring Ninject kernel through method which would be used to register under Owin.

public IKernel CreateKernel() { var kernel = new StandardKernel(); try { //kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>(); // TODO: Put any other injection which are required. return kernel; } catch { kernel.Dispose(); throw; }…