There are several templates for new Node.js projects, but the appropriate one for me seemed to be ‘From Existing Node.js code’.Īfter setting the usual Name/Location/Solution name fields, I was guided through a short and simple wizard where I chose the folder of your existing project (pre-populated based on the location), selected the entry point (also intelligently pre-selected), and the name of my project…Īnd that’s it! Hitting F5 launches my project and I’m away. As it happens, I’m currently working on a couple of MEAN stack applications, so once I’d finished installing, I decided to give it a go. With the RTM now available however, I decided I should get hold of it.įiring up the installer (which is much nicer than the last couple of versions I must say) I was met with an intriguing option – Node.js tooling. NET Core projects (which I’ve mainly been working on lately) had to undergo a one way conversion process, as project.json has been deprecated. I’d not actually played around with any of the pre-release versions as I was aware that. So, the other day Visual Studio 2017 was officially released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |