Why does everything have to use interface?

This page summarizes the projects mentioned and recommended in the original post on /r/dotnet

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • Moq

    Discontinued Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]

  • https://github.com/moq/moq4#features-at-a-glance

  • ASP.NET Core

    ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

  • So what you are saying is that companies such as Microsoft have no idea what they are doing? Have you ever looked at their open source repos, such as https://github.com/dotnet/aspnetcore/tree/main/src ? Almost every class implements an interface, otherwise you're not going to unit test it properly.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • referencesource

    Source from the Microsoft .NET Reference Source that represent a subset of the .NET Framework

  • Hmm not exactly. Maybe there's a specific example you're thinking of. Since you mentioned it, IEnumerable has no type constraints. Interfaces aren't part of the picture here.

  • CoreCLR

    Discontinued CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.

  • Docs

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts