This is taken from Jon Hilton, Quick Tip Friday newsletter.
You can subscribe to the newsletter here: https://jonhilton.net/
Its a great tip regarding example code for popular web frameworks (also mobile in the works), for example ASP.NET Core on the backend side and Angular or Vuejs on the frontend side etc. See list of backends and frontends here: (scroll down there are many options…)
Building software applications is hard, but doing it in isolation is even harder.
And, unless you’re one of the fortunate few who work in a perfectly balanced team with just the right amount of experienced developers to lean on, you’re often left figuring all this stuff out for yourself.
· Architectural best practices
· How to organise your code
· How to separate your concerns
· Which ORM to use
· How to KISS (keep it simple stupid) and avoid incurring loads of technical debt
But, just because you haven’t got a supportive, experienced and wise team physically on your doorstep doesn’t mean you have to re-invent all the wheels yourself!
Specifically I really want to recommend you check out the “real world” examples over at https://github.com/gothinkster/realworld.
There, they take the exact same application (a Medium clone) and show examples built in all manner of front-end and back-end frameworks.
So if you’re looking to see what a good ASP.NET Core API application looks like (or React, Angular, Vue.js or anything else you can think of)
When you reference a .js framework or library from your ASP.NET application, it makes sense to use the development version when you’re working on your own machine.
Referencing the development versions brings more useful error messages and integration with the React Developer tools.
But, you wouldn’t want to use these in production for performance reasons.
When you run the site in production, you’d want to reference the minified production versions of the React scripts.
Source: Different js scripts for different ASP.NET core environments· jonhilton.net – Making sense of .NET
“Razor Pages are a new feature in ASP.NET Core 2.0. They provide a simpler way to organize code within ASP.NET Core applications, keeping implementation logic and view models closer to the view implementation code. They also offer a simpler way to get started developing ASP.NET Core apps, but that doesn’t mean you should dismiss them if you’re an experienced .NET developer. You can also use Razor Pages to improve the organization of larger and more complex ASP.NET Core apps.”
Source: ASP.NET Core – Simpler ASP.NET MVC Apps with Razor Pages
.NET Core and ASP.NET Core offer several advantages over traditional .NET development. You should use .NET Core for your server applications if some or all of the following are important to your application’s success:
- Use of microservices
- Use of Docker containers
- High performance and scalability requirements
Side-by-side versioning of .NET versions by application on the same server
Online: Architect modern web applications with ASP.NET Core and Azure | Microsoft Docs