Skip to main content

Enabling Intellisense for AngularJS in Visual Studio Code

Visual Studio Code is a feature-rich code editor developed by Microsoft. Extensions can be added to the application to make it more usable. Intellisense is a developer feature that is present n almost all modern code editors and VSCode supports it. However, it does not support it out of the box. Follow the steps below to install Angular intellisense on VSCode Windows.



  • Install the typings package through npm. Install it globally.
  • npm install -g typings
  • Install the Angular specific typings on the directory of your project.
  • typings install dt~angular --save
  • The typigs folder and files will be created on your projects folder.
  • The typings.json file will be created too. Eventually this will be filled up by configuration entries but since we are just starting out and we are only interested in intellisense, this is blank.
  • Create the jsconfig.json file in the projects root directory'
  • Validate that the AngularJS intellisense is working. 


With the release of Angular 2 and 4, the VSCode Marketplace has plenty of extensions are available to help developers. Check out the marketplace here.


Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless