Back before .NET Core 2.0 shipped, I wrote a post highlighting various performance improvements in .NET Core 2.0 when compared with .NET Core 1.1 and the .NET Framework. As .NET Core 2.1 is in its final stages of being released, I thought it would be a good time to have some fun and take a tour through some of the myriad of performance improvements that have found their way into this release.

In this post I shown how you can use an IActionFilter in ASP.NET Core MVC to read the method parameters for an action method before it executes.

Today we’re releasing the second preview of EF Core 2.1, alongside .NET Core 2.1 Preview 2 and ASP.NET Core 2.1 Preview 2. Thank you so much to everyone who has tried our early builds and has helped shape this release with their feedback and code contributions! The new preview bits are now available in NuGet as individual packages, and as part of the ASP.NET Core 2.1 Preview 2 metapackage and in the .NET Core 2.1 Preview 2 SDK, also released today.

In this post, Premier Developer Consultant Randy Patterson introduces the new configuration API for ASP.NET Core and its order of precedence. In previous version of ASP.NET, configuration was primarily handled by the ConfigurationManager class. This class typically obtained the user configurable settings from the AppSettings section located in the XML file web.config. While these limited...

API Versioning is one of those never ending debates that happens anytime you want to build an API no matter how many APIs you have built…

The runtime code generation is a powerful practice that many developers are still reluctant to use. A typical, useful and simple point to start exploring the...

Today, we are announcing .NET Core 2.1 Preview 2. The release is now ready for broad testing, as we get closer to a final build within the next two to three months. We’d appreciate any feedback that you have.

Have you had to design general purpose “metadata” tables in your SQL database that basically store column names and values? Do you often serialize/de-serialize XML or JSON from your SQL tables to handle volatile schemas and data? .NET developers have traditionally worked with relational database management systems (RDMS) like SQL Server. RDMS systems have withstood the test of time and are production-ready. Like many tools, however, RDMS systems aren’t always the best solution. You may benefit from a different approach called NoSQL. Contrary to popular belief, NoSQL doesn’t mean “NO SQL” but rather “Not Only SQL.”

Microsoft has recently announced the release of a new .NET web framework – Blazor. In this article we are going to create a web application using Blazor with the help of Entity Framework Core. We will be creating a sample Employee Record Management system and perform CRUD operations on it.

When the global news organization Reuters wanted to enhance its news readers’ experience and generate more value from its visual assets, it used Microsoft Azure Machine Learning to build a video recommendation engine that matches news articles to related videos on the Reuters.com website. With automated matching, Reuters drives higher engagement on its website, realizes more news and business value from video assets, and creates new revenue opportunities.