Sunday, December 10, 2017

[ADVENT 2017] Current state of F# 4.x tooling and IDE ecosystem on December 2017

Hi my dear blog readers!

Thanks to Sergey Tihon for organizing this community-driven advent blog gathering in this year-end of 2017!


So here we are, on the edge of 2017. There are lots of advances in F# toolings and ecosystem, including the nature of open source ecosystem that has been available since the beginning of F# in VS 2010. When I say F# toolings. I’m not limiting myself to F# tooling in Visual Studio. Toolings in my context is tooling in Visual Studio, Visual Studio Code, and new contender/competitor of Visual Studio IDE, Jetbrains Rider.

F# state

Most advances in F# itself are without IDE. These are the current state of F# itself:

  1. F# supports .NET Core 2.0/.NET Standard 2.0 TFM development. This is also in sync with tooling support, starting with VS 2017 15.5.0, but I suggest you to install 15.5.1 update. (Please read my notes below)
  2. F# implements async interop with C#/VB async correctly, especially those xxxTask function such as Async.StartAsTask. See
  3. F# now supports goto definition correctly. I know this is quite IDE-related, but it needs some reworks on existing F# compiler. Thanks to relentless community support of F# contributors, especially Saul and Vasily Kirichenko. These are the PRs related to “go to definition” works: 
  4. Also now goto definition can go from F# to C#/VB.

Now, at F# IDE support:

  1. Ionide (Visual Studio Code extension for F#) gets nice updates! One of the notable feature is automatic project reloading, especially when dealing with F#/.NET Core 2.0 project. This is the latest release notes of Ionide:
  2. Jetbrains Rider (visual Studio competitor) has provided support for F#. Still, many works need to be done in .NET Core 2.0 full support. Read the original announcement of F# support here:
  3. In Visual Studio 2017 15.5.0: on the installation of a Workload that requires .NET Core 2.0, it will also install F# language support by default. The .NET Core, ASP.NET, and Azure workloads now do this.

Therefore, if you use Visual Studio 2017, it is highly recommended to update or directly use at least 15.5.0 update instead.

NOTE on Visual Studio 2017 15.5.0:

There’s one catch: if you use Xamarin in your worload, the 15.5.0 update on previous version will somehow override Xamarin MonoDroid VSIX packages. Fortunately, on 7th December, there is a fresh maintenance update on 15.5.0, the 15.5.1. This 15.5.1 provides the Xamarin package issue.

Now let’s meet F# and .NET Core using command prompt and in Visual Studio!

F# <3 .NET Core

Now, let’s try F# support for .NET Core.

We could check F# support availability as template, within the .NET Core tool of dotnet.

Using dotnet’s CLI tool, we can display list of templates installed in our .NET Core 2.0 SDK by using new command (parameter that acts as command to execute further) with –l for parameter of new:

dotnet new –l

On .NET Core SDK 2.0.3, run the dotnet above and we will have this list:


Let’s just focus on Short Name and the Language section on the list:


So we can compose and create any kinds of project that has F# as language support. The Short Name will be used as new parameter to define what template we’re going to use, the language parameter define the used language.

For example, we can create .NET Core console app with F#:

dotnet new console -n HelloFSharp -lang F#

NOTE: we should use -name parameter to give name to our project, instead of having default name from the template.

Run that in command prompt, we will have the creation of F# .NET Core 2.0 console project:


Now let’s look at the content of Program.fs:

// Learn more about F# at

open System

let main argv =
    printfn "Hello World from F#!"
    0 // return an integer exit code

Yes, it’s the same as our good old .NET Framework’s F# Console template from VS 2010/2012/2013/2015!

Then we can run it:


We can also provide more granular TFM as the target framework, but this option is only available for classlib template, not for console project template.

For more information, please visit dotnet new docs page:

What about Visual Studio 2017?

In Visual Studio 2017 starting from 15.5.0, we now have this:


YES! We now have F# .NET Core 2.0 fsproj support within Visual Studio 2017!

What are you waiting for? Go code in F# now!

Saturday, October 14, 2017

Speaking at MUGI Jakarta Gathering 2017 (October 2017)

Hi my blog 6audiences! Now it’s my speaking time for MUGI (Microsoft User Group Indonesia) community for Jadetabek (Jakarta, Tangerang, Bekasi region) under the umbrella of MUGI Nasional (nationwide). Although MUGI has quite a long hiatus (for about 7 months), we’re now ready to gather again full speed ahead.

Basically MUGI is a community of Microsoft’s product users ranging from MS Office users, Visual Studio developers (including C#/F#/VB/Xamarin/WPF/.NET), IT-pro (Windows Server, Exchange Server, Sharepoint) and other software users such as database developers that use SQL Server.

The event is called MUGI Jakarta Gathering 2017, on 7th October 2017. Thanks to Microsoft Indonesia’s support, we have venue support at Microsoft Indonesia’s office, located at BEJ Indonesia.

Thanks to the works of Hendra and Leo, we have secured some sponsorship fundings from Rhipe, Dell, Infront, Gulver and Omaging. Many thanks, guys!


The speaking sessions are not  just me, there are from IT-pros such as talks from Leonardo, Hendra, and Fazar. Also a power user talk from Abdullah, as lead of MUGI nationwide.

About 2 months ago I have been assigned as MUGI Jadetabek lead, therefore I’m eager to have this meetup more frequent!

I gave talk about C# and Visual Studio 2017, especially what’s new since VS 2015 and VS 2017.


Yes, C# 7.0 now has REPL, a feature that F# already has since initial release of F# 1.0!

But most of my talk is demo, based on the audience’s requests.


Here’s some other pictures:


Here is Abdullah gave talk about Digital Transformation:


Here’s Leonardo Irawan brought Windows Server 2016:


And here we had little break in the middle of sessions:


And Hendra in action:


And we are having a photo session for all audiences and speaker: (Leo did not join)


Thanks for this memorable meetup, guys!

Next, MUGI Jadetabek has plan to have meetups about DevOps in December or no later than January 2018.

Sunday, April 23, 2017

Speaking at Global Azure Bootcamp 2017 in Jakarta

Hi my dear blog readers!

I’m glad to share my experiences when I was speaking on Global Azure Bootcamp in Jakarta, on  22th April, 2017!

This is my first time speaking for Global Azure Bootcamp, many thanks to my Indonesian community DX, Irving Hutagalung and his staff, Debby, and my MUGI best friend Aprizon for giving me the chance to speak at this cool event!

Actually, Global Azure Bootcamp is a global wide event that is held simultaneously at the same day (or one day after) around the world. So there are Global Azure Bootcamp not just in Indonesia, but there were same events (but with separate speakers) in many other countries such as Singapore, Malaysia, Srilanka, Philippines. Mostly organized by Microsoft’s local country DX and MVP, this event is so crucial because it has full supports from Microsoft, including free Azure pass (Azure trial subscription).


Also thanks to the hard works of Aprizon and his colleagues, we have managed to secure a space for 60 people at IDX Jakarta.

There were many questions and critics as well especially for the lack of adequate documentations about Azure, but now we have a good supports from Indonesia’s support from MIcrosoft’s local support staffs.

My session is about Azure Functions in multiple languages and the implication of having serverless applications. I had demo of Azure Functions using Visual Studio 2015 Update 3 with Azure SDK 2.9.6 and Azure App Services Preview tooling installed.

This Azure App Services tool is essential, because it’s integrated with Visual Studio and supports debugging (through Azure Functions CLI) although it is in preview.


Here’s Azure Functions ran and debugged locally in Visual Studio:


Notice the Azure Functions logo shown in console of Azure Functions CLI Smile

The Azure App Services preview is available to download at:

NOTE: this tool requires that Azure SDK 2.9.6 preinstalled first on Visual Stuido 2015 Update 3.


Global Azure Bootcamp 2017 Jakarta session photos

Here are my session photos:




Yup, VIsual Studio 2015 was showing many/multiple language template!

Here are others in action: (Aprizon, Leonardo Irawan, Julius Fenata)




Well? Can’t wait to do more on the next Azure Global Bootcamp!

Sunday, March 19, 2017

Current state of Visual Studio releases [March 2017]

HI guys! We all know that Visual Studio 2017 has been released! Not jus that, at the time of the release of Visual Studio 2017, Team Foundation Server 2017 (on-premise) is reaching Update 1. There are also some news about Visual Studio 2017, TFS 2017, and the whole tooling and ecosystem as well.

On Visual Studio releases from January 15 to March 15, 2017, these are the notable news:

  1. Visual Studio 2017 is reaching RTM (or RTW, release to web) on March 7 
  2. Visual Studio Team Foundation Server 2017 is now at Update 1 on March 7
  3. General release of Azure Functions support of F# on March 16

Now, let’s start from the latest.

Visual Studio 2017 is reaching RTM

Yes! Visual Studio is reaching RTM! The launch is 2 days event: March 7 to 8. It was broadcasted live, and this is also the 20th anniversary of Visual Studio since the first release of Visual Studio 97. Yes, Visual Studio is reaching more than maturity, if you follow Visual Studio history itself and also one year of iterations/releases can mean more than one year in actual maturity of a software product!

This is the original page of Visual Studio 2017 launch:

The plan for the launch is already announced at Visual Studio’s blog team on February 9:

The original version “1” of Visual Studio is released in around early 1997, it is dubbed as Visual Studio 97. The blog shows the VS 97 setup display:

Previous Visual Studio releases has took quite long unpredicted schedule, especially from Visual Studio 6 (also called Visual Studio 98) to Visual Studio .NET. It takes more than 4 years! Since year 2000, one year in software development can mean anything especially when the other IDE competitors such as Eclipse, Netbeans and Jetbrain’s IntelliJ have been racing to have its own unique/distinctive features as competitive advantages.

So we can safely say that the release is not so surprising, because of the previous VS 2017 release candidates from RC1 to RC4. This announcement also has proven that Visual Studio has very tight cadence, and be prepared to see the next release of Visual Studio 2017 for every 18 months!

Visual Studio 2017 is basically contains these remarkable new features:

  1. Installation is defined as “workload”, categorize common scenarios of Windows development, game development, UWP development, Unity development, Data science, etc
  2. This is the initial release of Visual Studio to use CPS as its project system instead of legacy MSBUILD project system. But MSBUILD is still used to build almost all of the project within Visual Studio, especially .NET related projects (including full .NET Framework, .NET Core, .NET Standard)
  3. This is the initial release of Visual Studio to support .NET Standard. This tooling support is supposed to be available in VS 2015 too, but now all of the effort of .NET Standard support is focused on VS 2017.

For a detail list of what’s new in Visual Studio 2017 RTM, I will describe in a separate blog post after this.

Some things in Visual Studio 2017 are still not addressed/solved

Looking at the long history of Visual Studio releases, these are the remaining interesting issues still remain:

  1. Portability of installation of Visual Studio (since the beginning of Visual Studio)
  2. Full support of .NET Native in F# (since VS 2015 Update 3)
  3. Some of the tools are not mature enough, such as tooling for developing Azure Functions in F# (since VS 2015 Update 3)

Now, let’s start to discuss some of those points below.

Portability of Visual Studio installation

There is one thing for sure, Visual Studio cannot beat Eclipse full portability download. This issue is still tracked as feedback in Visual Studio uservoice feedback:

Unfortunately, this feedback has been going under indefinite status of “UNDER REVIEW” for more than 3 years:


Look at the number of votes! More than 2000 votes, this means this proposal should be heard and considered. Any rejection to this proposal has to be strongly reasonable, otherwise the unreasonable rejection will bring harm to the Visual Studio community as a whole.

Having a portable installation or setup of Visual Studio means that we should have less worry about installation setup, settings, registry, and many others. This also means that any toolings/extensions for Visual Studio must not depends on registry as well, just like Eclipse ecosystem and Eclipse PDE.

No .NET Native full support for F#

Yes, this is crucial and it’s often overlooked. No full support for .NET Native toolchain means that we cannot develop UWP (Universal Windows Platform, the Windows 10 store application) applications using F#.

This might be a strong statement, but I’ll try to explain this to you:

  • .NET UWP application is usually distributed on Windows Store
  • Any .NET UWP application submission to Windows Store is checked against .NET Native release binary
  • Currently in VS 2015 Update 3 and VS 2017, there is no .NET Native toolchain support to support F# generated IL.
  • Therefore, it can be considered impossible to implement all UWP applications in F#

Fortunately, the whole dev team at Microsoft has been aware of this since VS 2015.

We know that F# tooling and compiler is open source, and there has been heroic efforts by F# community members and MIcrosoft’s F# and other .NET team members to solve this by closing the gaps of F# feature with .NET Native.

One big major setback of .NET Native lack of features is the availability of tailcall optimization.

To track the update of the .NET Native support for F#, this is the GitHub issue link under Microsoft Visual F# repository:


Visual Studio Team Foundation Server 2017 Update 1 is released

Yes! Visual Studio TFS 2017 Update 1 is released at the same time with Visual Studio 2017. It is also mentioned at the launch page.

There is also official announcement from Brian Harry, although it is a little bit late:

This is the official link to the release notes:

This Update 1 cannot be ignored, because it has quite tons of new features! In my own personal opinion, these are the most notable additional features of TFS 2017 Update 1:

  1. Personalized welcome page. This is very refreshing and it’s now easier to navigate if we have many team projects.
  2. In the Git support, we can now search for commit in a branch
  3. In the Git support, administrative privileges are now becoming more granular, especially when dealing with repo creation and repo deletion.
  4. In the Git support, we can now have nice preview of markdown editing.

The personalized link of TFS 2017 Update 1is currently the same web page of the page of my own VS Team Service account:


All of the team projects you have will be listed based on your customized list, and if you hover on the team project name, it will display all of the additional link such as the Dashboard, Code, Work, Build and Release, Test.

In the PR comments, it’s a welcome addition to see basic editing tool and preview available:


  • on TFS 2015, Build and Release are under separate page.
  • TFS 2015 Update 3 can accommodate markdown in the PR comments, but the basic editing tool is not available.

While this release of TFS 2017 Update 1 is so promising, I believe many companies are not ready yet to move from TFS 2015 Update 3. Because again, the TFS cadence is becoming shorter than before, and now the race to always have updated TFS might be solved by always using the online Team Services, although some companies are not willing to go to this path because their code is very precious.

The official release of Azure Functions support for F#

Yes! Now we can create Azure Functions using F#, although F# support has been previewed before.

Azure Functions is a serverless application, it is actually a simplified model of already existing Azure Web Jobs. But this serverless model means that we are not dealing with the detail of how the function is deployed, on what platforms, and other things. We are only focusing on the correctness of the functions, and how we are executing it.

Azure Functions itself is generally available since November 2016, according to this Azure’s official blog article:

The initial launch of Azure Functions only support C#, Powershell, Bash, Python. At that time, F# support was still in preview and a little bit unstable.

Fortunately support for F# is now officially stable:

They also have this picture of love relationship of Azure functions and F#:

This is soooo cool!

I have discussed and presented Azure Functions in F# at the meetup of Lambda Jakarta on March also, and the reaction is so priceless although some of the invited and joined guests weren’t there.

This was the picture of myself presenting and demoing Azure Functions in F#:


Here’s my Azure Functions sample (edit and test it directly):


I know that the demo is so simple, but this Azure Functions is much more powerful than Amazon AWS Lambda compared to the readiness of toolings and the full Continuous Integration that Azure has.

This is the landing page of Azure Functions:

The Azure Functions template and the inclusions of libraries are open source! This is the official GitHub landing of Azure Functions:

We have GitHub’s Azure functions page, and therefore we can contribute as well!

Next blog entry: the full journey of the new features of VS 2017.

Thursday, December 29, 2016

F# Advent: F# 4.0 function first constructor

Hi there!
I know it’s been long promised before, that I will discuss constructor as function in F# 4.0 in my previous blog entry of What’s new in F# 4.0.
This blog is part of F# blog Advent in December that contains blogs of F# developer communities, thanks to Sergey Tihan to organize this advent series! Full list of blog series
Now we can simply treat any object constructor as a simple function call that always returns an object typed as the same as the name of the function, and this is the same as constructor in C#/VB.

Quick background of OOP support in F#

F# is functional programming language, and we all know that it is basically what F# really shines as programming language. But F# has very good support for OOP, including the nature of inheritance, encapsulation, polymorphism and mutability. Every class defined in F# also supports method calls that parts of the object’s behaviors, including object’s constructors.
Since F# first release, OOP support is improving, including nice supports for upcast and downcast of a type. But this type casting support is nicely documented in F# documentation at Microsoft’s new documentation repository:

Function constructor in action

Now let’s visit F# tutorial sample on Visual Studio:
And we now have a Tutorial.fsx file opened. Go to the Classes section in the comments, and we will see the sample code to create class with default constructor that has 2 parameters:
We can see that the code instantiate Vector2D by calling the constructor directly instead of using new keyword!
In previous release of F#, we have to use new to call constructor. For example:
let vector3 = new Vector2D(1.5, 4.5)
Now we can simply call the constructor without new, as demonstrated in the tutorial sample:
let vector1 = Vector2D(3.0, 4.0)
Yes, it’s more succinct, cleaner, and one thing is also nice: it’s more functional in style. This new function constructor is typed to return the same object as the function name, therefore there’s no constructor that will return void or unit because this is not allowed.
WARNING: The name resolution is important, we should not have implemented another function with the same name as the name of the class. Otherwise compile error will occur.
Unfortunately, current documentation of F# object expression does not cover this function constructor yet:
I invite all of you, my blog reader, to contribute to F# docs repo. Enjoy contributing and happy coding!

Thursday, March 31, 2016

Current state of Visual Studio releases [March 2016]

Hi there, my blog readers!

I’m back to regular updates of giving what happened in Visual Studio world from February 2016 to the end of March 2016. It’s a bit late (31st March) as there are exciting news!

There were interesting news, including the update of Visual Studio, .NET Core, ASP.NET Core, the shocking nice update: Microsoft acquired Xamarin!

These are the updates from February 2016 to the end of March 2016:

  1. Microsoft acquired Xamarin! – February 25, it was discussed by Scott Gu in his blog entry, also in Xamarin’s blog, as well as others from Wall Street Journal, TechCrunch, etc.
  2. Visual Studio TFS 2015 Update 2 goes RTM!– March 30, 2016, – complete TFS 2015 Update 2 description is available at the official VS TFS 2015 Update 2
  3. Visual Studio 2015 Update 2 goes RTM! – March 30, 2016, – complete Update 2 description is available at the official Visual Studio release note page
  4. Microsoft joins Eclipse Foundation, as described in Brian Harry’s blog and in Visual Studio’s blog.
  5. Visual Studio 2005’s end of support announcement – March 11, 2016 – The official end of date is April 12th, 2016 but it is announced on this Visual Studio blog

These updates are cool! Especially on Xamarin’s acquisition and VS 2015 and TFS 2015 Update 2 releases.

Microsoft acquired Xamarin

Yes, Microsoft acquired Xamarin! Now Miguel de Icaza joins Microsoft as part of Microsoft developers. All of the Xamarin employees are part of Microsoft as well.

For more details, please read Microsoft official announcement in Scott Gu’s blog entry.

We are going to have Microsoft Xamarin Studio? Or new name? This is interesting!

Visual Studio 2015 Update 2 RTM

Yes, we have Update 2 RTM! To me, the most noteworthy notes in this Update 2 release are:

  1. Git indicator of committed changes that not yet pushed and uncommitted local changes
  2. Git submodule update is now available when submodule has to be refreshed for update
  3. Add support for these Git commands: reset –-hard, cherry picking, and staging)
  4. Typescript is updated to TypeScript 1.8

And many more! Again, check the complete list of new features and bug fixes at:

For #1, we can have Git indicator on the status bar below:


This is small new features but it’s very useful to see the number of changes and number of committed changes that is not yet pushed. It might be unnoticed, but this indicator can be clicked. Clicking the “pencil” icon will display the changes page if there’s committed changes. Clicking the “up arrow” will go to the Synchronization page.

These are the new supported Git commands in the Update 2:


The nice thing is the Cherry-Pick support, and I’m going to use this Cherry-Pick often!

Visual Studio TFS 2015 Update 2 RTM

This update is also very good update for TFS 2015 (on premise version of Visual Studio Team Services).

The notable features are:

  1. Creating and deleting team project is now available from the web interface
  2. Work items now can be deleted!
  3. Team Foundation Server extensions!
  4. Create new branch from bugs in Kanban board (new linking capabilities)

For more complete list of new features, changes, and bug fixes, please visit:

Next blog entry will discuss the implications of Xamarin after acquired by Microsoft!

Monday, January 25, 2016

Current state of Visual Studio releases [January 2016]

Hi my dear blog readers!

The “Current state of Visual Studio releases” series has been quite in active for about 4 months. I know this is supposed to be updated regularly, but unfortunately there are very rare notable news and updates of Visual Studio and Microsoft’s Developer Division.

Also the series got a bit delayed, because I was focusing on previous Lambda Jakarta coding dojo meetup.

From the beginning of December 2015 to 20th January 2016, these are the updates of Visual Studio:

  1. Support period ending for .NET 4, 4.5, and 4.5.1
  2. The release of Visual Studio 2015 Update 1 (on November 30, 2015)
  3. Node.js Tools for Visual Studio version 1.1 released (on November 17, 2015)
  4. First preview of Visual Studio Java Language Service for Android

Now, let’s discuss those three! Except for the last one (number #4), I haven’t got the chance to fully use it.

This is still in preview, for more information please see the blog:

Now, let’s start!

Support ending for .NET 4, 4.5 and 4.5.1

The original announcement is here:

This simply translate as “Microsoft will not provide supports anymore for .NET 4.0, 4.5, and 4.5.1 and this include hotfixes for these releases”. The next message is simply please update to at least .NET 4.5.2 or even better, 4.6.

The follow up of the original announcement is here:

The interesting fact is from the link above is:

Applications targeting a .NET Framework version that is no longer supported will not need to retarget or recompile to a newer version as they can be run on a later .NET Framework version. The .NET Framework 4.5.2 and higher versions have higher compatibility, provided by a newer feature called “quirking”. Quirking is a pattern in which a .NET Framework version maintains the semantics of earlier versions, while including updated implementations. The .NET runtime knows which of these semantics or quirks to execute depending on the .NET Framework version that the application targets. More information on migrating an application can be found on the Migration Guide to the .NET Framework MSDN article.

Put it simply, it matches with my translation above. I believe this will bring more burden on the enterprise IT operations especially those that focusing on premises (instead of cloud such as Azure), because .NET 4.5 is still quite new for them.

It’s quite new for them, because .NET 4.5 was released in 2012 (with the same release date of Visual Studio 2012, and also Windows 8/Windows Server 2012). Fast forward to now, end of year of 2015, only less than 3 years but they have to immediately upgrade. Less than three years of platform update is inevitable,

This end of support is not just for us, developers. For those develop .NET applications that runs on Azure, the upgrades on Azure are necessary. Fortunately Microsoft has provided updated images (mostly in form of Virtual Machines) that more focusing on .NET 4.5.2 and above (including .NET 4.6).

Visual Studio 2015 Update 1 RTM

This release although it might seems a service release, it really contains many new things.

These are new features brought by Update 1:

  • Visual C#
  • Debugging enhancements (Visual C++ and IDE aspect)
  • Tools for Apache Cordova (now Update 5)
  • Tools for Universal Windows Apps version 1.2

And many more! For complete list of release notes, visit:

Let’s visit some of the new features:

Visual C# new features

This Update 1 brings you C# Interactive Window and C# scripting API. This C# interactive window is very much like F# interactive window, except it has these two quite subtle differences: it has intellisense and type coloring!


If you are wondering what to do at the C# interactive window, just type “#help” like above.

And now we have C# scripting API. Unfortunately, the documentation of C# scripting API is still incomplete and I could not test it further.

One thing is still missing: VB.NET Interactive window! Unfortunately, we won’t see VB.NET interactive in Visual Studio 2015 at all, even after Update 1.


Debugging and diagnostic enhancements

In VIsual C++, now we have support for Edit and Continue for /BigObj. This looks like minor feature but this is very important, because it enables debugging with Edit and Continue support for WIndows Store applications that’s written in C++.

In Visual C# and Visual Basic, now we have “Go to implementations” feature when you activate context menu in the source code window. This item will display the implementation of the object you want to observe, not just having knowing “Go to definitions” that was available since VS 2002 (also called Visual Studio .NET 2002).


Yup, it’s a minor addition but it’s useful!

There’s also enhancements on Code Analysis, but unfortunately it’s not for Visual Studio Express Edition.

Tools for Apache Cordova (a.k.a. TACO) Update 5

The notable feature is support for iOS 9 and experimental support for Android M, a.k.a. “Marshmallow”. Now TACO is maturing well. The overall experience of using this release is much better than previous releases, including better performance especially responsiveness of the emulators when running Cordova applications.

Beginning with this Update 5, the Node.js will only focus on Node.js version 5. So please update your Node.js installation as well to focus on Node.js 5 and above!

For more information on this TACO update 5, visit:

Node.js tools for Visual Studio version 1.1

This is a very useful tool, and sometimes I use this tool to debug certain Node.js package or applications. Having Node.js support in Visual Studio is a very nice feature although this tool is available as Visual Studio extension:


For more information, please visit the official repo of Node.js for Visual Studio:

Yes, it’s OPEN SOURCE!

After you download from the Visual Studio Extension and Updates (or you can get from VS Gallery), simply install the MSI:


The installation for this release, 1.1.1 will take about 5-7 minutes on VS 2015 Update 1.

One thing you must remember: it needs Node.js at least version 0.91 but it’s recommended to install Node.js 5.

Now, Visual Studio 2015 will have these new project templates: (under TypeScript)


Now, enjoy and I welcome discussions! Smile