Skip to main content

Basic OOPS concept with TypeScript

Some time back I had written article on Introduction of TypeScript. We already know that OOPS concept can be used on JavaScript, but with TypeScript we can achieve in much simpler way.

In this particular article we will check interaction of object in different way to handle HTML interaction situations in cleaner way with the help of objects and functions.

We will check out by creating TS interface and passing it to some other function which will change some of the object properties and same can be communicated back to the source.

I am trying to keep things simple only by using simple approach

 interface ICar {  
   Model: string  
   Speed: number;  
   SpeedChange: (speed:number) => void;  
 }  

Let's consume the above to other class which can be initialized be calling constructor. It is having simple method which is defining the SpeedChange body.

 class Main {  
   constructor(private option: ICar) {  
     option.SpeedChange = (speed) => {  
       console.log(speed);  
     };  
   }  
 }  

The same option object can be stored and send across any other function. By calling SpeedChange the logging would be done from Main class.
Ex:

 public static SomeOtherClassFunction(car: ICar) {  
     car.SpeedChange(20);  
   }  

The example is simple but can be very useful in real world client side driven development.

NOTE: The objects can be stored as JS variable as well and can be referred to somewhere else with the help of window object. Out of OOPS and flexibility of JS :)


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 ASPNet Core Identity in MVC Core

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.

AspNet Identity Core is a new offering from Microsoft in replacement of AspNet Identity for managing users.

In this tutorial, we would be looking for implementing LDAP with AspNet Identity Core to allow users to be able to log in through AD or AspNet Identity Core members.

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": "4.0.0.0", "System.DirectoryServices.AccountManagement": "4.0.0.0" } } },
These System.DirectoryServices and System.DirectoryServices.AccountManagement references are used to consume LDAP functiona…

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.

Startup.cs
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; }…