BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage .NET Core Content on InfoQ

  • InfoQ .NET Trends Report 2022

    Every year, all InfoQ editors invite seasoned developers and practitioners from the industry to discuss the current trends in the entire software development landscape. In this article, we discuss some of the .NET Trends for 2022, divided into four stages of adoption.

  • Deep Diving into EF Core: Q&A with Jeremy Likness

    Entity Framework (EF) Core is a cross-platform, extensible, open-source object-database mapper for .NET. Since its first release in 2016, EF Core evolved until reaching its current form: a powerful and lightweight .NET ORM. InfoQ interviewed Jeremy Likness, program manager for .NET Data at Microsoft, to understand more about EF Core and what we should expect for its next release later this year.

  • Custom Response Caching Using NCache in ASP.NET Core

    NCache is a cross-platform, open-source distributed caching framework from Alachisoft. It is an extremely fast distributed caching framework that is linearly scalable. This article presents a discussion on how we can work with NCache and response caching middleware in ASP.NET Core.

  • Mono: from Xamarin to WebAssembly, Blazor, and .NET 5 - Q&A with Miguel de Icaza

    Mono started as an open source .NET platform in 2001, being developed by Xamarin until 2011. Since the company’s acquisition by Microsoft in 2016, both Mono and .NET Core have been developed in parallel. In the light of the most recent releases, InfoQ interviewed Miguel de Icaza —the original author of the Mono project—to talk about the current state of Mono and its future in the .NET ecosystem.

  • Preparing Entity Framework Core for Static Analysis and Nullable Reference Types

    In this article we walk through the process of updating an EF Core 3.1 based DAL to adhere to modern best practices such as TreatWarningsAsErrors, FxCopAnalyzers, and C# 8’s nullable reference types.

  • Angular & ASP.NET Core 3.0 - Deep Dive

    While there are many advantages to using Angular for building SPAs, some parts including trivial, static content such as Contact As, Licensing, etc. don’t need the extra complexity. In this article Evgueni Tsygankov shows how to build reusable Angular components that can be hosted in ASP.NET Core pages, allowing you to choose the right tool for each page.

  • Using the .Net Core Template Engine to Create Custom Templates and Projects

    The tooling story changed dramatically with .NET Core, because of its serious emphasis on the command line. This is a great fit for .NET Core's cross-platform, tooling-agnostic image.

  • Single Page Applications and ASP.NET Core 3.0

    Web development has changed in the past few years, with the maturity of Angular, React, Vue, and others. We’ve moved from building web pages to building apps. We’ve also been shifting from rendering markup on the server, to more commonly rendering it directly in the browser. But as developers continue to transition to client-side development, many are asking if they should still be using ASP.NET.

  • Article Series - .NET Core 3

    In this series, we explore the benefits of .NET Core and how it can help not only traditional .NET developers, but all technologists who need to bring robust, performant and economical solutions to market.

  • Interview with Scott Hunter on .NET Core 3.0

    Chris Woodruff talks to director of program management for the .NET platform, Scott Hunter, about what developers can expect from .NET Core 3.

  • Navigating the .NET Ecosystem

    In 2002, .NET was released. Over the next 12+ years, the .NET developer community patiently grew at a seemingly steady pace. Then, things started evolving rapidly. Microsoft anticipated the changing ecosystem and embraced the open-source development mindset, even acquiring GitHub.

  • WebAssembly and Blazor: A Decades Old Problem Solved

    A framework, named Blazor because it runs in the browser and leverages a templating system or "view engine" called Razor, enables the scenario .NET developers almost gave up on. It doesn't just allow developers to build client-side code with C#, but also allows developers to run existing .NET Standard DLLs in the browser without a plugin. Here's the story of WebAssembly and Blazor.

BT