VS Code Insiders & Azure

VS Code – Insiders

I didn’t know that Visual Studio Code has a special Insiders build. Around late February/early March I came up across some link and I downloaded it rightaway. It installs side-by-side with your standard, stable VS Code installation and gives you access to the latest builds of VS Code in order to have better access to the newest features included in it. Generally speaking, I encourage you to do the same. One drawback is you will have to install all the extensions once again, but except some unexpected issues, I don’t see much reasons to get back to the other installation.

You can  read about it and find a download link here.

Azure hosting

What’s interesting about Azure is that it offers you such a wide variety of types of applications you can manage there, that when you fist enter this azure portal, it’s hard to find out which is the right one for you. What I needed to do is to find some option to host my node website. But first I had to begin with the account creation. You can create an azure account with $200 credits for free just to try it out. That’s quite a lot if you want just to host some small website and try the features it offers. So I strongly suggest you go and check it out: here.

Once you have the account, you enter the portal and navigate to:

  1. New -> Web + Mobile -> Web App.
  2. Choose the name, your free subscription, add some new resource group (name it somehow, doesn’t matter at this moment) and choose an App Service Plan. There are quite a few, but for the beginning the most standard one should do the job.
  3. Before saving you can ‘pin to desktop’ in order to have easy link to your website from the main screen when you log into the portal.
  4. An interesting option here is that you can host your website from within a git repository, which enables continuous integration at the the speed of light. Basically you just get from azure a git repo to push when you want to publish your code to Azure. You register another remote, push your sources and … that should be it.

Should be, because as usual you may face some unexpected issues, like I did =)


remote: 'typings' is not recognized as an internal or external command,
remote: operable program or batch file.

That of course works fine on my computer, and that’s because I did all this stuff from bash and not via simple publish and ‘npm start’. I have already found the command line on the azure portal, which is actually super-cool so I hope this will move the process forward. The website already got its address, so once I finally resolve my issues it will be publicly available here: http://dotnetvideos.azurewebsites.net/

Oh, and of course there’s at least one known issue to workaround, which I’ve found when browsing some troubleshooting topics. I wrote one post about it before: the famous ‘node-gyp’ issue (python/c++) is also a problem for azure websites. The workaround is to publish your node_modules folder so that the precompiled binaries are already available without having to node-gyp it on azure. This will be my next try when I find time.

Anyway, it seems that I’m moving forward much faster now, except the small fact that most of my ‘free’ time this week I’ve spent watching build, not coding 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *