Just to throw out the obvious: it should be trivial to get some old Node code up and running, particularly if you don't mind using an old runtime version. If you've run npm shrinkwrap you have a log of the exact versions of each package used. You don't have to use ES6 or Typescript, you can keep on trucking the same as you ever did.<p>It sounds like the author was an ASP.NET developer, dabbled a little in Node, then worked with Xamarin (also .NET) then moved to ASP.NET Core. Nothing wrong with any of that, but it only stands to reason you'll find ASP.NET easier to work with than Node when you've used it extensively and Node not very much at all.
I personally find the title could better be worded "Moving my blog from Node.js to ASP.NET" or "I just found out that ASP.NET got much better than it used to be"<p>When I first read the title I thought it was a node.js dev moving to ASP.NET.<p>TL;DR The poster of the blog found out that ASP.NET fits his needs better, since he seems more capable on that bit etc and he wants to highlight that ASP.NET has improved a lot towards supporting other platforms than Windows and other capabilities other than webforms etc.
"very mature und stable"<p>Sorry but please don't spread these kind of lies. I love .NET Core to death, but the ecosystem is VERY immature. Just today I have been trying to authenticate with the Azure API for 8 hours because:<p>1) There is barely any support for .NET Core in the Azure SDK.<p>2) The documentation on the website is very outdated and does not take .NET Core into account. For example the documentation about Table Storage is talking about a TableQuery function that does NOT exist for .NET Core (and this isn't mentioned anywhere), the Azure Webjobs SDK does NOT support .NET Core (again, never mentioned anywhere).<p>3) .NET Core itself and the tooling surrounding it is full of bugs still. Yesterday I've been trying to reference the TableEntity class in my file, but VS couldn't find it anywhere. I've been trying really hard to get it working, even decompiling the source code to see what's up, but in the end apparently I just had to unload the project and reload it.<p>Developing for .NET Core is still very, very, very painful. So many things will break and will not be supported (yet).
He moved from a dynamically served website using node.js backed by mongo DB to a website that reads markdown files in asp.net and renders them. The website is his personal blog. Alternatively the author could have used Hugo and generated his site statically before deploying it.
There's absolutely nothing wrong with having a static website, but there are already tools like pelican, hugo, jekyll, sphinx and stuff that are better suited for it. So while I'm happy for the person's effort and that he got to use Azure, the more glaring thing is I suspect he could be happier using a static site generator.<p>Also Armin Ronacher released a new one late 2015, Lektor. <a href="https://www.getlektor.com/" rel="nofollow">https://www.getlektor.com/</a><p>Show me a team replacing their medium-sized django or rails website with ASP.net Core. Or a YCombinator startup huddling up to their screens late at night in Visual Studio pushing code to azure. And them shipping and making customer's happy.
Rather lacking in details on what actually went wrong. Then, instead of figuring it out the best solution is just to switch stacks? Seems a bit.. lazy to me.<p>Tons of breaking changes between 2 years ago node and current stable node.. that's like.. 0.12.x to 6.x? Is it a package issue? I've not had a problem as long as my package config was the same.
One critical thing I don't feel the article answers is why you would want to move to .NET, what the advantages are over Node.js, TypeScript et al.<p>I don't mean this as criticism, I'm working on some Node/TS projects and I'm very interested to hear the strengths .NET has over Node.
Do you really need to stick a an animated gif in the middle of the article?<p>The one thing I would say about JS on the server is writing EJS templates is much faster than something like razor.<p>Otherwise, go trumps node in every other way.
Why weren't they using nvm? Did they have a build server? I'm confused how it suddenly stopped working, but TBH I got a bit confused and bored.
I can't figure out the circle jerk around Node. Debugging sucks A LOT, JS syntax sucks, single thread sucks, NPM is filled with 95% junk.<p>Python, Java, golang, C#, and maybe even PHP have more mature and reasonable stacks.