by bill-s, 2019-09-04T13:14:21.663Z
Single Page Applications are the new wave of the moment. In the midst of several frameworks and libraries that arose during the last decade to tackle better ways to build web applications, React is now the most popular one. It’s a lightweight library (yes, React is not a framework, so it means it doesn’t come with all the rules, specifications and patterns that Angular, e.g., comes with), that is embraced and powered by the community, simple to use, flexible, and relies on a strong concept: components.
by bill-s, 2019-09-04T13:17:25.750Z
One of the great extensibility points in the routing feature of the older versions of the ASP.NET MVC and ASP.NET Core MVC frameworks was the ability to pick up any route and dynamically point it at a given controller/action.
This had a lot of excellent use cases – as we will briefly see – and since ASP.NET Core 3.0 Preview 7, the feature is actually finally available in ASP.NET Core 3.0 (despite not being mentioned in the official release blog post).
So, let’s have a look at dynamic routing in ASP.NET Core 3.0 together!
by bill-s, 2019-09-04T13:17:05.020Z
This is the first post in the series: Exploring ASP.NET Core 3.0.
Part 1 - Exploring the new project file, Program.cs, and the generic host (this post)
Part 2 - Comparing Startup.cs between the ASP.NET Core 3.0 templates
In this post I take a look at some of the fundamental pieces of ASP.NET Core 3.0 applications - the .csproj project file and the Program.cs file. I'll describe how they've changed in the default templates from ASP.NET Core 2.x, and discuss some of the changes in the the APIs they use.
by cezarypiatek, 2019-09-02T19:20:48.199Z
How I built a very simple macro system for C# that works right in the code editor.
by bill-s, 2019-09-04T13:26:21.775Z
.NET Conf is back again this year and will be live streaming to a device near you September 23-25 on www.dotnetconf.net! .NET Conf is a FREE, 3 day virtual developer event co-organized by the .NET community and Microsoft. This year .NET Core 3.0 will launch at .NET Conf 2019! Come celebrate and learn about the new release. You won’t want to miss this one.
by bill-s, 2019-09-04T13:24:49.295Z
Purpose of this repository
This is list of main goals of this repository:
Showing how you can implement the monolith application in a modular way
Presentation of the full implementation of the application. This is not another simple application. This is not another proof of concept (PoC). The assumption is to present the implementation of the application that would be ready to run on production
Showing the application of best practices and object-oriented programming principles
Presentation of the use of design patterns. When, how and why they can be used
Presentation of some architectural considerations, decisions, approaches
Presentation of the implementation using Domain-Driven Design approach (tactical patterns)
by bill-s, 2019-09-04T13:15:04.313Z
In my last post, I introduced you to a tool for looking up licenses of .NET projects called delice.
This week I released the first update, version 1.1.0, that brings a big improvement to the license detection for the legacy licensing format of many NuGet packages.
Determine Licenses via the GitHub API
By-and-large the dependencies we rely on are the output of an OSS project and that project is more often than not hosted on GitHub. Because of this, we can use the GitHub License API to try and get the license information of a project, which delice now supports:
by bill-s, 2019-09-04T13:23:25.123Z
Want to learn hooks, but you've been too busy?
Here's a mini-crash course just for you!
by bill-s, 2019-09-04T13:18:16.568Z
I don't believe that the web development community is having an honest discussion about GraphQL. This is because, GraphQL is almost exclusively presented as an alternative to REST (Representational State Transfer). And, while GraphQL may remove points-of-friction found in REST, the dishonesty is rooted in a false and implicit dichotomy when it comes to API implementations. The truth is, GraphQL and REST are not your only choices when it comes to building an HTTP-based API. And while this may be obvious to many experienced web application developers, it is not nearly as obvious to newcomers. As such, I think that the community should be striving to have a more nuanced conversation.
by bill-s, 2019-09-04T13:16:22.703Z
This post is part of the series 'Web Performance'. Be sure to check out the rest of the blog posts of the series!
Website performance: Why and how to measure?
Website performance: How I've improved the performance of this website? (this post)
In the previous post, I wrote about why performance is important and how to measure it for your website. In this post, I'll talk about the different things I've made on this website to improve the performance. Some of the optimizations are just some configuration flags to turn on, others require more changes in your code.
by andrea.angella, 2019-09-04T22:24:23.014Z
Learn the Pros and Cons of Visual Studio and Rider, the two main IDEs for .NET developers.