Add content to aspnet-core roadmap (#3294)
* Initial commit * Initial commit * Initial commit * Initial commit * Initial commit * Initial commit * Initial commit * Initial commit * Initital commit * Initial commit * Initial commit * Committing 107-databases * Content added in aspnet-core/content/108-log-frameworks * Content added in aspnet-core/content/109-api-clients * Content added in aspnet-core/content/110-real-time-communication * Content added in aspnet-core/content/111-object-mapping * Content added in aspnet-core/content/112-task-scheduling * Fix Eager Loading heading * Fix lazy loading heading * Update src/roadmaps/aspnet-core/content/104-orm/103-nhibernate.md * Update src/roadmaps/aspnet-core/content/100-basics-of-csharp/101-dotnet.md * Update src/roadmaps/aspnet-core/content/103-basics-of-aspnet-core/101-rest.md * Update src/roadmaps/aspnet-core/content/109-api-clients/102-graphql/100-graphql-dotnet.md * Update src/roadmaps/aspnet-core/content/103-basics-of-aspnet-core/index.md * Update src/roadmaps/aspnet-core/content/104-orm/100-entity-framework-core/102-change-tracker-api.md * Update src/roadmaps/aspnet-core/content/104-orm/102-repodb.md * Update src/roadmaps/aspnet-core/content/104-orm/102-repodb.md * Update src/roadmaps/aspnet-core/content/105-dependency-injection/102-life-cycles/index.md * Update src/roadmaps/aspnet-core/content/105-dependency-injection/index.md * Update src/roadmaps/aspnet-core/content/109-api-clients/102-graphql/100-graphql-dotnet.md * Update src/roadmaps/aspnet-core/content/109-api-clients/102-graphql/index.md * Update src/roadmaps/aspnet-core/content/110-real-time-communication/101-singlar-core.md * Update src/roadmaps/aspnet-core/content/111-object-mapping/100-atuo-mapper.md * Update src/roadmaps/aspnet-core/content/107-databases/100-search-engines/100-elasticsearch.md * Update src/roadmaps/aspnet-core/content/107-databases/102-relational/101-postgresql.md * Update src/roadmaps/aspnet-core/content/107-databases/102-relational/103-mysql.md * Update src/roadmaps/aspnet-core/content/107-databases/103-nosql/101-mongodb.md * Update src/roadmaps/aspnet-core/content/108-log-frameworks/101-nlog.md * Update src/roadmaps/aspnet-core/content/108-log-frameworks/100-serilog.md * Update src/roadmaps/aspnet-core/content/108-log-frameworks/102-log-management-system/100-elk-stack.md * Update src/roadmaps/aspnet-core/content/108-log-frameworks/102-log-management-system/104-elmah.md * Update src/roadmaps/aspnet-core/content/108-log-frameworks/index.md * Update src/roadmaps/aspnet-core/content/109-api-clients/100-rest/101-odata.md * Update src/roadmaps/aspnet-core/content/109-api-clients/100-rest/index.md * Update src/roadmaps/aspnet-core/content/109-api-clients/102-graphql/100-graphql-dotnet.md * Update src/roadmaps/aspnet-core/content/109-api-clients/101-grpc.md * Adding content to 115-ci-cd * Adding content to 116-client-side-libraries * Adding content to 117-template-engines * Adding content to 118-good-to-know-libraries * Adding content to 113-testing * Adding content to 114-microservices Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>pull/3305/head
syedmouaazfarrukh
2 years ago
committed by
GitHub
parent
ee843cc9e2
commit
bb9878fdb7
161 changed files with 1511 additions and 159 deletions
@ -1 +1,9 @@ |
|||||||
# Dotnet |
# .NET Framework |
||||||
|
|
||||||
|
.NET (pronounced "dot net") is a software framework developed by Microsoft that can be used to create a wide range of applications, including Windows desktop and web applications, mobile apps, and gaming. The .NET Framework provides a large library of pre-built functionality, including collections, file input/output, and networking, that can be used by .NET applications. It also includes a Common Language Runtime (CLR) which manages the execution of code, providing features such as memory management, security, and exception handling. |
||||||
|
|
||||||
|
For more information, visit the following link: |
||||||
|
|
||||||
|
- [What is .NET?](https://dotnet.microsoft.com/en-us/learn/dotnet/what-is-dotnet) |
||||||
|
- [Intro to .NET](https://www.codecademy.com/article/what-is-net) |
||||||
|
- [An Overview of .NET](https://auth0.com/blog/what-is-dotnet-platform-overview/) |
||||||
@ -1 +1,16 @@ |
|||||||
# Azure devops services |
# Azure Devops Services |
||||||
|
|
||||||
|
Azure DevOps Services is a collection of services provided by Microsoft that can be used to plan, build, test, and deploy .NET applications. These services can be used together or independently to support various aspects of the software development process. Some of the main services include: |
||||||
|
|
||||||
|
- Azure Boards: Provides features for agile planning and tracking, such as backlogs, boards, and sprint planning. |
||||||
|
- Azure Repos: Provides source control management for Git and Team Foundation Version Control (TFVC) repositories. |
||||||
|
- Azure Artifacts: Provides package management for NuGet, npm, and Maven packages. |
||||||
|
- Azure Test Plans: Provides support for manual and exploratory testing, as well as continuous testing and testing in production. |
||||||
|
- Azure Pipeline: Provides a way to build, test, and deploy code automatically, with support for multiple languages and platforms, including .NET. |
||||||
|
|
||||||
|
These services can be used to create a full-featured development environment that can be used to manage all aspects of a software development project, from planning and design to testing and deployment. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Build, test, and deploy .NET Core apps](https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/dotnet-core?view=azure-devops&tabs=dotnetfive) |
||||||
|
- [Microsoft Azure DevOps for ASP .NET Core Web apps](https://techmindfactory.com/Microsoft-Azure-DevOps-for-ASP-.NET-Core-Web-apps/) |
||||||
@ -1 +1,24 @@ |
|||||||
# General development skills |
# General development skills |
||||||
|
|
||||||
|
There are several skills that are generally considered to be important for working with .NET and C#: |
||||||
|
|
||||||
|
- Object-oriented programming: Understanding the concepts of classes, objects, inheritance, and polymorphism is essential for working with C# and the .NET Framework. |
||||||
|
|
||||||
|
- C# language: A strong understanding of the C# language, including its syntax, keywords, and built-in classes and types, is necessary for writing efficient and maintainable code. |
||||||
|
|
||||||
|
- .NET Framework: Familiarity with the .NET Framework, including the Common Language Runtime (CLR) and the Base Class Library (BCL), is important for understanding how C# code is executed and for utilizing the framework's many built-in features. |
||||||
|
|
||||||
|
- Web & Software development: Knowledge of web development technologies such as HTML, CSS, JavaScript, and ASP.NET is important for creating web applications using C# and the .NET Framework and knowledge of software development methodologies such as Agile, Scrum, or Waterfall is also useful. |
||||||
|
|
||||||
|
- Database: Familiarity with database concepts and technologies, such as SQL and ADO.NET, is important for working with data in C# applications. |
||||||
|
|
||||||
|
- Cloud computing: Familiarity with cloud computing concepts and technologies, such as Azure, is becoming increasingly important for deploying and scaling C# applications. |
||||||
|
|
||||||
|
- DevOps: Understanding of DevOps concepts and practices, such as continuous integration and continuous deployment, is necessary for automating and streamlining the software development process. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [A Step-by-Step Approach to Learn OOP](https://www.geeksforgeeks.org/a-step-by-step-approach-to-learn-object-oriented-programming/) |
||||||
|
- [Asp.net - Complete Tutorial](https://www.youtube.com/watch?v=kdPtNMb8tPw) |
||||||
|
- [Learn Cloud Computing](https://www.youtube.com/watch?v=eWwK2FKWp0g) |
||||||
|
- [DevOps Course for Beginners](https://www.youtube.com/watch?v=hQcFE0RD0cQ) |
||||||
@ -1 +1,14 @@ |
|||||||
# Triggers |
# Triggers |
||||||
|
|
||||||
|
Triggers are special type of stored procedures that are automatically executed in response to specific events that occur within a database. These events can include: |
||||||
|
|
||||||
|
- Data modification events (INSERT, UPDATE, DELETE) on a specific table or view. |
||||||
|
- Data definition events (CREATE, ALTER, DROP) on specific database objects such as tables or views. |
||||||
|
- Logon events (CONNECT, DISCONNECT) that occur when a user connects to or disconnects from the database. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Database Triggers](https://docs.oracle.com/cd/A57673_01/DOC/server/doc/SCN73/ch15.htm) |
||||||
|
- [Database Triggers: Examples & Overview](https://study.com/academy/lesson/database-triggers-examples-overview.html) |
||||||
|
- [What are Triggers in SQL?](https://www.edureka.co/blog/triggers-in-sql/) |
||||||
|
- [What is a SQL Trigger?](https://www.essentialsql.com/sql-trigger/) |
||||||
@ -1 +1,9 @@ |
|||||||
# Rest |
# REST |
||||||
|
|
||||||
|
REST (Representational State Transfer) is an architectural style for building web services. In the context of .NET, RESTful web services can be created using the ASP.NET Web API framework, which allows developers to create HTTP-based services that can be consumed by a wide range of clients, including web browsers and mobile devices. The Web API framework provides a set of tools and libraries for creating RESTful services, including routing, request/response handling, and support for a variety of data formats, such as JSON and XML. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [What is REST Services?](http://www.codedigest.com/quick-start/16/what-is-rest-services-how-to-create-rest-services-in-aspnet) |
||||||
|
- [Restful API In ASP.NET: Introduction of REST & Web API](https://www.c-sharpcorner.com/UploadFile/4b0136/restful-api-in-Asp-Net-introduction-of-rest-web-api/) |
||||||
|
- [What are RESTful APIs](https://www.pragimtech.com/blog/blazor/what-are-restful-apis/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Razor pages |
# Razor Pages |
||||||
|
|
||||||
|
Razor Pages is a feature of the ASP.NET Core framework that allows developers to build web applications using a combination of Razor markup (a markup syntax for defining dynamic HTML) and C# code. Razor Pages is built on top of the ASP.NET Core MVC (Model-View-Controller) framework, and provides a simpler, more intuitive way to build web pages and handle user input. |
||||||
|
|
||||||
|
Razor Pages are useful for building simple, self-contained web pages that do not require a complex navigation or layout structure, and are often used for building small to medium-size web applications. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Basics of Razor Pagess](https://www.jetbrains.com/dotnet/guide/tutorials/basics/razor-pages/) |
||||||
|
- [Get started with Razor Pages in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/?view=aspnetcore-7.0) |
||||||
|
- [What Is Razor Pages?](https://www.learnrazorpages.com/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Razor components |
# Razor Components |
||||||
|
|
||||||
|
Razor Components is a feature of ASP.NET Core that allows developers to build reusable, self-contained components that can be used across multiple pages or even multiple applications. Razor Components is built on top of the Razor view engine, which allows developers to define components using a combination of Razor markup and C# code. |
||||||
|
|
||||||
|
Razor Components are useful for building complex, dynamic, and reusable UI elements, such as forms, tables, or dialogs, and can be used to build both small and large-scale web applications. |
||||||
|
|
||||||
|
For more information, vist the following links: |
||||||
|
|
||||||
|
- [ASP.NET Core Razor components](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/?view=aspnetcore-7.0) |
||||||
|
- [What is Core razor components?](https://www.youtube.com/watch?v=KseDLejhYi0) |
||||||
|
- [Core Razor Componets in .NET](https://www.c-sharpcorner.com/blogs/asp-net-core-razor-componets) |
||||||
@ -1 +1,11 @@ |
|||||||
# Middlewares |
# Middlewares |
||||||
|
|
||||||
|
Middleware is software that sits between an operating system and application software, and facilitates communication and data exchange between them. In the context of web development, middleware refers to software components that handle requests and responses in a web application. These components are typically executed in a pipeline, with each component performing a specific task, such as authentication, logging, or routing. |
||||||
|
|
||||||
|
In the ASP.NET Core framework, middleware is a key concept that is used to build web applications. Middleware components are added to the application pipeline using the `IApplicationBuilder` interface, and are executed in the order in which they are added. For example, an application might have middleware components for handling authentication, logging, and routing, in that order. |
||||||
|
|
||||||
|
Visit the following links for more resources: |
||||||
|
|
||||||
|
- [What is Middleware?](https://www.redhat.com/en/topics/middleware/what-is-middleware) |
||||||
|
- [Introduction to Middleware](https://www.techtarget.com/searchapparchitecture/definition/middleware) |
||||||
|
- [What is Middleware in .NET?](https://www.talend.com/resources/what-is-middleware/) |
||||||
@ -1 +1,7 @@ |
|||||||
# Filters and attributes |
# Filters and Attributes |
||||||
|
|
||||||
|
In the ASP.NET Core framework, filters and attributes are used to add additional functionality to controllers and action methods, such as authentication, authorization, caching, and exception handling. |
||||||
|
|
||||||
|
- **Filters** are classes that implement one or more of the filter interfaces provided by the framework, such as `IActionFilter`, `IResultFilter`, `IExceptionFilter`, and `IAuthorizationFilter`. Filters can be applied to controllers, action methods, or globally to the entire application. They can be used to perform tasks such as logging, caching, and handling exceptions. |
||||||
|
|
||||||
|
- **Attributes** are classes that derive from `Attribute` class, and are used to decorate controllers, action methods, or properties with additional metadata. For example, the Authorize attribute can be used to require that a user is authenticated before accessing a specific action method, and the `ValidateAntiForgeryToken` attribute can be used to protect against cross-site request forgery (CSRF) attacks. |
||||||
@ -1 +1,13 @@ |
|||||||
# App settings and configurations |
# App Settings and Configurations |
||||||
|
|
||||||
|
In the ASP.NET Core framework, app settings and configurations refer to the process of storing and managing application-specific settings and configuration data. |
||||||
|
|
||||||
|
- **App Settings** refers to the key-value pairs of data that an application uses to configure its behavior, such as database connection strings, api keys, or other settings. These settings are typically stored in configuration files, such as `appsettings.json`, `appsettings.development.json`, or `appsettings.production.json`, and can be accessed using the IConfiguration interface. |
||||||
|
|
||||||
|
- **Configurations** refer to the process of loading and managing the app settings, including specifying the source of the settings and the format of the configuration files. In ASP.NET Core, the `Startup` class is responsible for configuring the application's settings, and typically loads configuration data from various sources, such as JSON files, environment variables, or command-line arguments. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [What is Azure App Configuration?](https://learn.microsoft.com/en-us/azure/azure-app-configuration/overview) |
||||||
|
- [What are App Configurations and how do I work with them?](https://support.procore.com/faq/what-are-app-configurations) |
||||||
|
- [Configuration & AppSettings](https://docs.servicestack.net/appsettings) |
||||||
@ -1 +1,9 @@ |
|||||||
# Basics of aspnet core |
# Basics of ASP.NET Core |
||||||
|
|
||||||
|
ASP.NET Core is a open-source, cross-platform web framework for building modern web applications using .NET. Some of the basics of ASP.NET Core are Cross-platform, Open-source, Modular, High performance, MVC pattern, Dependency Injection, Middleware, Razor Pages and Razor Components, EF Core. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [ASP.NET documentation](https://learn.microsoft.com/en-us/aspnet/core/?view=aspnetcore-7.0) |
||||||
|
- [ASP.NET Core Tutorial](https://www.tutorialspoint.com/asp.net_core/index.htm) |
||||||
|
- [Learn ASP.NET Core from Scratch](https://www.tutorialsteacher.com/core) |
||||||
@ -1 +1,12 @@ |
|||||||
# Framework basics |
# Framework Basics |
||||||
|
|
||||||
|
An ORM (Object-Relational Mapping) framework is a tool that maps the objects in an application to the database tables, allowing developers to work with the database using familiar, object-oriented concepts. |
||||||
|
|
||||||
|
ORM frameworks are tools that map the objects in an application to the database tables, allowing developers to work with the database using familiar, object-oriented concepts such as Entities, Mapping, Context, Queries, Lazy Loading, Change Tracking, and Caching. |
||||||
|
|
||||||
|
For more resources, visit the following link: |
||||||
|
|
||||||
|
- [ORM Framework](https://www.h2kinfosys.com/blog/orm-framework/) |
||||||
|
- [What are Frameworks in ORM](https://www.killerphp.com/articles/what-are-orm-frameworks/) |
||||||
|
- [Essentials of ORM Framework](https://medium.com/@mikependon/the-essentials-of-orm-framework-in-your-software-development-837131efd91b) |
||||||
|
- [ORM Frameworks – What is an Object-Relational Mapping Framework](https://onlinecode.org/what-are-orm-frameworks/) |
||||||
@ -1 +1,12 @@ |
|||||||
# Change tracker api |
# Change Tracker API |
||||||
|
|
||||||
|
The Change Tracker API is a feature of ORM (Object-Relational Mapping) frameworks, such as Entity Framework Core, that allows developers to track changes to entities and automatically persist them to the database. |
||||||
|
|
||||||
|
The Change Tracker API is typically exposed through the context class, which is the main class that manages the connection to the database and provides access to the entities. |
||||||
|
|
||||||
|
When an entity is retrieved from the database, the Change Tracker API marks it as "unchanged". When a property of the entity is modified, the Change Tracker API marks the entity as "modified". And when a new entity is added to the context, the Change Tracker API marks it as "added". |
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [Change Tracking in EF Core](https://learn.microsoft.com/en-us/ef/core/change-tracking/) |
||||||
|
- [Intro to Change Tracking](https://www.oreilly.com/library/view/programming-entity-framework/9781449331825/ch05.html) |
||||||
|
- [ChangeTracker in Entity Framework Core](https://www.entityframeworktutorial.net/efcore/changetracker-in-ef-core.aspxs) |
||||||
@ -1 +1,15 @@ |
|||||||
# Lazy eager explicit loading |
# Lazy Eager Explicit Loading |
||||||
|
|
||||||
|
## Eager Loading |
||||||
|
|
||||||
|
Eager Loading helps you to load all your needed entities at once; i.e., all your child entities will be loaded at single database call. This can be achieved, using the Include method, which returs the related entities as a part of the query and a large amount of data is loaded at once. |
||||||
|
|
||||||
|
## Lazy Loading |
||||||
|
|
||||||
|
It is the default behavior of an Entity Framework, where a child entity is loaded only when it is accessed for the first time. It simply delays the loading of the related data, until you ask for it. |
||||||
|
|
||||||
|
Visit the following links for more resources: |
||||||
|
|
||||||
|
- [Eager Loading & Lazy Loading](https://www.c-sharpcorner.com/article/eager-loading-lazy-loading-and-explicit-loading-in-entity-framework/) |
||||||
|
- [Difference between Eager and Lazy Loading](https://stackoverflow.com/questions/31366236/lazy-loading-vs-eager-loading) |
||||||
|
- [Working With Lazy & Eager Loading in Entity Framework](https://dzone.com/articles/working-with-lazy-loading-and-eager-loading-in-ent) |
||||||
@ -1 +1,9 @@ |
|||||||
# Entity framework core |
# Entity Framework Core |
||||||
|
|
||||||
|
Entity Framework Core (EF Core) is an open-source Object-Relational Mapping (ORM) framework for .NET. It is a lightweight, cross-platform version of Entity Framework, the ORM framework that was part of the .NET Framework. EF Core allows developers to work with relational data using domain-specific objects, eliminating the need to write raw SQL statements. Instead, EF Core provides a set of APIs that can be used to interact with a database, providing a simple and efficient way to perform common database operations such as querying, inserting, updating, and deleting data. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Example of Entity Framework Core](https://learn.microsoft.com/en-us/ef/core/) |
||||||
|
- [Entity Framework Core Documentation](https://learn.microsoft.com/en-us/ef/) |
||||||
|
- [What are the Basics of Entity Framework Core?](https://www.jetbrains.com/dotnet/guide/tutorials/basics/entity-framework-core/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Repodb |
# RepoDB |
||||||
|
|
||||||
|
RepoDB is an open-source ORM (Object-Relational Mapping) library for .NET that simplifies the process of working with databases. It is a lightweight, fast, and easy-to-use library that provides a simple and consistent API for performing common database operations such as querying, inserting, updating, and deleting data. |
||||||
|
|
||||||
|
RepoDb is built on top of ADO.NET, which is the native data access technology in .NET, and provides a higher-level abstraction on top of it. This allows RepoDb to take advantage of the performance and scalability of ADO.NET while providing a simpler and more convenient API for developers. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Get Started with RepoDB](https://repodb.net/) |
||||||
|
- [Complete Guide to RepoDB](https://medium.com/nerd-for-tech/everything-you-need-to-know-about-repodb-23cd4b9939c1) |
||||||
|
- [Why Choose RepoDB?](https://blog.devgenius.io/why-choose-repodb-orm-over-dapper-da87432c7830) |
||||||
@ -1 +1,11 @@ |
|||||||
# Nhibernate |
# NHibernate |
||||||
|
|
||||||
|
NHibernate is an open-source Object-Relational Mapping (ORM) framework for .NET. It is a powerful and flexible framework that can greatly simplify working with relational data in .NET. NHibernate is similar to other ORM frameworks such as Entity Framework and RepoDb in that it provides a higher-level abstraction on top of the underlying data access technology (ADO.NET in this case) and allows developers to work with data using domain-specific objects, eliminating the need to write raw SQL statements. |
||||||
|
|
||||||
|
NHibernate uses the concept of "mapping files" which are XML files that define how the classes in the application map to the tables and columns in the database. These mapping files are used to create a conceptual model of the data in the form of classes, and then NHibernate uses this model to generate the SQL statements necessary to interact with the database. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [What is Nhibernate?](https://www.partech.nl/en/publications/2021/08/what-is-nhibernate-and-how-is-it-different-from-entity-framework) |
||||||
|
- [NHibernate - ORM](https://www.tutorialspoint.com/nhibernate/nhibernate_orm.htm) |
||||||
|
- [Get Started with NHibernate](https://nhibernate.info/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Scrutor |
# Scrutor |
||||||
|
|
||||||
|
Scrutor is an open-source library for .NET that extends the functionality of the built-in dependency injection framework in .NET Core. It provides a set of extension methods for the `IServiceCollection` interface, which can be used to register and configure services in a more convenient and flexible way. |
||||||
|
|
||||||
|
One of the main features of Scrutor is its ability to automatically scan assemblies for services and register them with the dependency injection container, allowing you to avoid having to manually register each service one by one. It also provides a fluent API that makes it easy to configure services, such as specifying the lifetime of a service, adding decorators, and more. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [How to use Scrutor in ASP.Net Core?](https://www.infoworld.com/article/3321356/how-to-use-scrutor-in-aspnet-core.html) |
||||||
|
- [Complete Guide to Scrutor](https://andrewlock.net/using-scrutor-to-automatically-register-your-services-with-the-asp-net-core-di-container/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Microsoft extensions dependency injection |
# Microsoft Extensions Dependency Injection |
||||||
|
|
||||||
|
Microsoft.Extensions.DependencyInjection is a dependency injection framework that is part of the Microsoft.Extensions.DependencyInjection NuGet package. It is used to create and manage instances of objects and their dependencies, and is particularly useful for implementing the Dependency Inversion Principle in .NET applications. |
||||||
|
|
||||||
|
The package provides a simple and consistent API for registering services and resolving dependencies, which can be used to configure and manage the lifetime of objects in an application. It also provides built-in support for various types of service lifetime, such as transient, singleton and scoped. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Guide to Microsoft Extensions Dependency Injection](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection?view=dotnet-plat-ext-7.0) |
||||||
|
- [Exploring the Microsoft.Extensions.DependencyInjection](https://www.codeproject.com/Articles/5339241/Exploring-the-Microsoft-Extensions-DependencyInjec) |
||||||
|
- [How to use Microsoft.Extensions.DependencyInjection](https://stackoverflow.com/questions/53825155/how-can-i-use-microsoft-extensions-dependencyinjection-in-an-net-core-console-a) |
||||||
@ -1 +1,11 @@ |
|||||||
# Auto fac |
# Autofac |
||||||
|
|
||||||
|
Autofac is an open-source dependency injection framework for .NET. It is designed to make it easier to manage the dependencies of an application by automatically resolving and managing the lifetime of objects and their dependencies. |
||||||
|
|
||||||
|
Autofac uses a technique called "component registration" to define the objects and dependencies of an application. This is done by creating instances of the `ContainerBuilder` class and using its methods to register types, instances and factories. Then, the `Build()` method is called to create an instance of the `IContainer` interface, which can be used to resolve dependencies throughout the application. |
||||||
|
|
||||||
|
Visit the following resources for more information: |
||||||
|
|
||||||
|
- [Autofac’s Documentation](https://autofac.readthedocs.io/en/latest/) |
||||||
|
- [Getting started with Autofac](https://autofac.org/) |
||||||
|
- [Dependency Injection with Autofac](https://www.codeproject.com/Articles/25380/Dependency-Injection-with-Autofac) |
||||||
@ -1 +1,11 @@ |
|||||||
# Ninject |
# Ninject |
||||||
|
|
||||||
|
Ninject is an open-source dependency injection framework for .NET. It is designed to make it easier to manage the dependencies of an application by automatically resolving and managing the lifetime of objects and their dependencies. |
||||||
|
|
||||||
|
Ninject uses a technique called "binding" to define the objects and dependencies of an application. This is done by creating instances of the `StandardKernel` class and using its methods to register types, instances and factories. Then, the `Get()` method is called to resolve the dependencies throughout the application. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [Intro to Ninject](http://www.ninject.org/) |
||||||
|
- [What is Ninject and when do you use it?](https://stackoverflow.com/questions/17375234/what-is-ninject-and-when-do-you-use-it) |
||||||
|
- [How to use NInject?](https://www.infoworld.com/article/3191648/how-to-implement-di-in-webapi-using-ninject.html) |
||||||
@ -1 +1,11 @@ |
|||||||
# Castle windsor |
# Castle Windsor |
||||||
|
|
||||||
|
Castle Windsor is an open-source dependency injection framework for .NET. It is designed to make it easier to manage the dependencies of an application by automatically resolving and managing the lifetime of objects and their dependencies. |
||||||
|
|
||||||
|
Castle Windsor uses a technique called "registration" to define the objects and dependencies of an application. This is done by creating instances of the `WindsorContainer` class and using its methods to register types, instances and factories. Then, the `Resolve()` method is called to resolve the dependencies throughout the application. |
||||||
|
|
||||||
|
Visit the following links for more resources: |
||||||
|
|
||||||
|
- [Getting Started with Dependency Injection Using Castle Windsor](https://www.codementor.io/@copperstarconsulting/getting-started-with-dependency-injection-using-castle-windsor-4meqzcsvh) |
||||||
|
- [What is Castle Windsor?](https://stackoverflow.com/questions/124871/what-is-castle-windsor-and-why-should-i-care) |
||||||
|
- [Intro to Castle Windsor](http://www.castleproject.org/projects/windsor/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Simple injector |
# Simple Injector |
||||||
|
|
||||||
|
Simple Injector is an open-source dependency injection framework for .NET. It is designed to make it easy to manage the dependencies of an application by automatically resolving and managing the lifetime of objects and their dependencies. |
||||||
|
|
||||||
|
Simple Injector uses a technique called "registration" to define the objects and dependencies of an application. This is done by creating an instance of the `Container` class and using its methods to register types, instances and factories. Then, the `GetInstance()` method is called to resolve the dependencies throughout the application. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [How to use Simple Injector?](https://www.infoworld.com/article/3636242/how-to-use-simple-injector-in-aspnet-core-mvc.html) |
||||||
|
- [Simple Injector's Documentation](https://docs.simpleinjector.org/en/latest/) |
||||||
|
- [Example of Dependency Injection Using Simple Injector](https://www.c-sharpcorner.com/UploadFile/4d9083/dependency-injection-using-simple-injector/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Di containers |
# DI Containers |
||||||
|
|
||||||
|
A dependency injection (DI) container is a software component that is responsible for managing the dependencies of an application. It is used to create and manage instances of objects and their dependencies, and is particularly useful for implementing the Dependency Inversion Principle in software development. |
||||||
|
|
||||||
|
A DI container typically consists of two main parts: a configuration API, which is used to register the types and their dependencies, and a resolution API, which is used to retrieve instances of the registered types. The DI container automatically resolves the dependencies of the objects it creates, and manages the lifetime of the objects and their dependencies. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [What is DI Container?](https://www.dotnettricks.com/learn/dependencyinjection/what-is-ioc-container-or-di-container) |
||||||
|
- [Getting Started with DI Container](https://stackoverflow.com/questions/50718586/what-is-a-di-container) |
||||||
|
- [How to Use DI Container?](https://learn.userfrosting.com/services/the-di-container) |
||||||
@ -1 +1,10 @@ |
|||||||
# Scoped |
# Scoped |
||||||
|
|
||||||
|
Scoped lifetime is a type of dependency injection that creates a new instance of an object for each unique request, but reuses the same instance for the same request. This means that if multiple components within the same request depend on the same service, they will all receive the same instance. However, if another request is made, a new instance of the service will be created for that request. |
||||||
|
|
||||||
|
Scoped lifetime is useful when you have services that are specific to a given request, such as a request-scoped database context. This allows you to have a separate and isolated instance of a service for each unique request, which can help to prevent cross-request contamination of data and improve performance. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [Dependency Injection - What is Scope?](https://javaranch.com/journal/2008/10/dependency-injection-what-is-scope.html) |
||||||
|
- [Effective Dependency Injection Scoping](https://medium.com/android-news/effective-dependency-injection-scoping-4bac813d4491) |
||||||
@ -1 +1,11 @@ |
|||||||
# Transient |
# Transient |
||||||
|
|
||||||
|
Transient lifetime is a type of dependency injection that creates a new instance of an object each time it is requested. This means that if multiple components within the same request or across different requests depend on the same service, they will each receive a new instance of the service. |
||||||
|
|
||||||
|
Transient lifetime is useful when you have services that are stateless and do not need to maintain any data between requests, such as a service that performs a simple calculation or returns data from a database. |
||||||
|
|
||||||
|
For more information: |
||||||
|
|
||||||
|
- [What are Transient Dependencies?](https://blazor-university.com/dependency-injection/dependency-lifetimes-and-scopes/transient-dependencies/) |
||||||
|
- [Dependency Injection Lifetime](https://www.tektutorialshub.com/asp-net-core/asp-net-core-dependency-injection-lifetime/) |
||||||
|
- [Dependency Injection Explained with Transient](https://www.youtube.com/watch?v=NkTF_6IQPiY) |
||||||
@ -1 +1,11 @@ |
|||||||
# Singleton |
# Singleton |
||||||
|
|
||||||
|
Singleton lifetime is a type of dependency injection that creates a single instance of an object and reuses it throughout the lifetime of the application. This means that if multiple components within the same request or across different requests depend on the same service, they will all receive the same instance of the service. |
||||||
|
|
||||||
|
Singleton lifetime is useful when you have services that need to maintain state or shared data across requests, such as a service that caches data or maintains a connection to a resource. |
||||||
|
|
||||||
|
For more information: |
||||||
|
|
||||||
|
- [What are Singleton Dependencies?](https://blazor-university.com/dependency-injection/dependency-lifetimes-and-scopes/transient-dependencies/) |
||||||
|
- [Dependency Injection Lifetime](https://www.tektutorialshub.com/asp-net-core/asp-net-core-dependency-injection-lifetime/) |
||||||
|
- [Dependency Injection Explained with Singleton](https://www.youtube.com/watch?v=NkTF_6IQPiY) |
||||||
@ -1 +1,15 @@ |
|||||||
# Life cycles |
# Life Cycles |
||||||
|
|
||||||
|
In ASP.NET, dependency injection (DI) lifecycles determine the lifetime of objects that are resolved through the DI container. There are several predefined lifecycle options in the `Microsoft.Extensions.DependencyInjection` library, including: |
||||||
|
|
||||||
|
- **Transient:** A new instance of the object is created every time it is requested. |
||||||
|
- **Scoped:** A new instance of the object is created for each request within the same scope. |
||||||
|
- **Singleton:** A single instance of the object is created and shared across the entire application. |
||||||
|
|
||||||
|
Additionally, you can also create a custom lifecycle by implementing the `Microsoft.Extensions.DependencyInjection.IServiceScopeFactory` interface |
||||||
|
|
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [Complete Guide to Dependency Injection Lifecycles](https://www.youtube.com/watch?v=wA5bPsv2CLA) |
||||||
|
- [What are Service Life Cyles in ASP.NET Core?](https://endjin.com/blog/2022/09/service-lifetimes-in-aspnet-core) |
||||||
|
- [Learn Service Lifetimes in .NET Core](https://henriquesd.medium.com/dependency-injection-and-service-lifetimes-in-net-core-ab9189349420) |
||||||
@ -1 +1,12 @@ |
|||||||
# Dependency injection |
# Dependency Injection |
||||||
|
|
||||||
|
Dependency injection (DI) is a software design pattern that is used to manage the dependencies of an application. It is a technique that allows developers to write loosely-coupled code, by separating the responsibility of creating and managing objects from the objects themselves. |
||||||
|
|
||||||
|
In a typical implementation, a DI container is used to manage the dependencies of the application. The container is responsible for creating and managing instances of objects and their dependencies, and providing them to other objects as needed. |
||||||
|
|
||||||
|
There are different types of dependency injection, such as Constructor injection, Property injection, and Method injection, which can be used depending on the requirement and the design of the application. |
||||||
|
Visit the following links for more resources: |
||||||
|
|
||||||
|
- [What is Dependency Injection?](https://stackoverflow.com/questions/130794/what-is-dependency-injection) |
||||||
|
- [Dependency Injection, It's Definition & principles](https://www.growin.com/blog/what-is-dependency-injection/) |
||||||
|
- [Intro to Dependency Injections](https://www.freecodecamp.org/news/a-quick-intro-to-dependency-injection-what-it-is-and-when-to-use-it-7578c84fa88f/) |
||||||
@ -1,8 +1,9 @@ |
|||||||
# Memory cache |
# Memory Cache |
||||||
|
|
||||||
Memory caching (often simply referred to as caching) is a technique in which computer applications temporarily store data in a computer’s main memory (i.e., random access memory, or RAM) to enable fast retrievals of that data. The RAM that is used for the temporary storage is known as the cache. |
Memory caching (often simply referred to as caching) is a technique in which computer applications temporarily store data in a computer’s main memory (i.e., random access memory, or RAM) to enable fast retrievals of that data. The RAM that is used for the temporary storage is known as the cache. |
||||||
|
|
||||||
Visit the following resources to learn more: |
Visit the following resources to learn more: |
||||||
|
|
||||||
- [Cache in-memory in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/performance/caching/memory?view=aspnetcore-7.0) |
- [Cache in-memory in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/performance/caching/memory?view=aspnetcore-7.0) |
||||||
- [Intro to In-Memory Caching in C#](https://www.youtube.com/watch?v=2jj2wH60QuE) |
- [Intro to In-Memory Caching in C#](https://www.youtube.com/watch?v=2jj2wH60QuE) |
||||||
|
- [What is Memory Caching?](https://hazelcast.com/glossary/memory-caching/) |
||||||
@ -1,8 +1,9 @@ |
|||||||
# Stackexchange redis |
# Stackexchange Redis |
||||||
|
|
||||||
StackExchange.Redis is a high performance general purpose redis client for .NET languages (C#, etc.). It is the logical successor to BookSleeve, and is the client developed-by (and used-by) Stack Exchange for busy sites like Stack Overflow. |
StackExchange.Redis is a high performance general purpose redis client for .NET languages (C#, etc.). It is the logical successor to BookSleeve, and is the client developed-by (and used-by) Stack Exchange for busy sites like Stack Overflow. |
||||||
|
|
||||||
Visit the following resources to learn more: |
Visit the following resources to learn more: |
||||||
|
|
||||||
- [Using StackExchange.Redis with .NET](https://docs.redis.com/latest/rs/references/client_references/client_csharp/) |
- [Using StackExchange.Redis with .NET](https://docs.redis.com/latest/rs/references/client_references/client_csharp/) |
||||||
- [Introduction to StackExchange.Redis](https://www.youtube.com/watch?v=rsXvpCHdldg) |
- [Introduction to StackExchange.Redis](https://www.youtube.com/watch?v=rsXvpCHdldg) |
||||||
|
- [Getting Started with Stackexchange Redis](https://stackexchange.github.io/StackExchange.Redis/) |
||||||
@ -1,8 +1,9 @@ |
|||||||
# Distributed cache |
# Distributed Cache |
||||||
|
|
||||||
A distributed cache is a cache shared by multiple app servers, typically maintained as an external service to the app servers that access it. A distributed cache can improve the performance and scalability of an ASP.NET Core app, especially when the app is hosted by a cloud service or a server farm. |
A distributed cache is a cache shared by multiple app servers, typically maintained as an external service to the app servers that access it. A distributed cache can improve the performance and scalability of an ASP.NET Core app, especially when the app is hosted by a cloud service or a server farm. |
||||||
|
|
||||||
Visit the following resources to learn more: |
Visit the following resources to learn more: |
||||||
|
|
||||||
- [Distributed caching in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-7.0) |
- [Distributed caching in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-7.0) |
||||||
- [Distributed Caching In ASP.NET Core With Redis](https://www.youtube.com/watch?v=Tt5zIKVMMbs) |
- [Distributed Caching In ASP.NET Core With Redis](https://www.youtube.com/watch?v=Tt5zIKVMMbs) |
||||||
|
- [What is a Distributed Cached?](https://hazelcast.com/glossary/distributed-cache/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Elasticsearch |
# Elasticsearch |
||||||
|
|
||||||
|
Elasticsearch is a distributed, open-source search and analytics engine that can be used to index, search, and analyze large volumes of data quickly and in near real-time. It is built on top of the Apache Lucene library and can be used to perform full-text search, faceted search, and geospatial search, among other things. |
||||||
|
|
||||||
|
In an ASP.NET application, Elasticsearch can be integrated as a search engine to provide advanced search functionality to the application. There are several libraries available for integrating Elasticsearch with an ASP.NET application, such as Nest and Elasticsearch.Net. These libraries provide a .NET client for Elasticsearch, which can be used to interact with the Elasticsearch engine from within an ASP.NET application. |
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Elasticsearch in ASP.NET Core](https://code-maze.com/elasticsearch-aspnet-core/) |
||||||
|
- [An Elasticsearch Tutorial for .NET Developers](https://www.toptal.com/dot-net/elasticsearch-dot-net-developers) |
||||||
|
- [How to integrate ElasticSearch in ASP.NET?](https://blexin.com/en/blog-en/how-to-integrate-elasticsearch-in-asp-net-core/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Solr |
# Solr |
||||||
|
|
||||||
|
Apache Solr is a search engine platform based on the Apache Lucene library. It is a standalone enterprise search server that provides a REST-like API for indexing, searching, and updating documents. Solr can be used to perform full-text search, faceted search, and geospatial search, among other things. |
||||||
|
|
||||||
|
Solr can be useful in ASP.NET application to provide advanced search capabilities, such as full-text search, faceted search and geospatial search, which can be useful in e-commerce, content management systems, and logging and monitoring applications. It is known for its scalability, performance and its ability to handle large volumes of data with complex queries. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [Guide to Solr in ASP.NET](https://www.codeproject.com/Tips/480091/Using-Solr-for-Search-with-NET-Csharp) |
||||||
|
- [How to get Started with Solr.NET?](https://stackoverflow.com/questions/5646615/how-to-get-started-with-solr-net) |
||||||
|
- [Integrate Solr Instance With .NET Core](https://stacksecrets.com/dot-net-core/integrate-solr-instance-with-net-core) |
||||||
@ -1 +1,11 @@ |
|||||||
# Sphinx |
# Sphinx |
||||||
|
|
||||||
|
Sphinx is an open-source full-text search engine that can be used to index, search and analyze large volumes of data quickly and in near real-time. It is designed to handle high-traffic websites and large data sets and can be used for full-text search, faceted search, and geospatial search. |
||||||
|
|
||||||
|
In an ASP.NET application, Sphinx can be integrated as a search engine to provide advanced search functionality to the application. There are several libraries available for integrating Sphinx with an ASP.NET application, such as SphinxQL.NET and SphinxClient. These libraries provide a .NET client for Sphinx, which can be used to interact with the Sphinx engine from within an ASP.NET application. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Overview of Sphinx in ASP.NET](https://www.sphinxconnector.net/) |
||||||
|
- [Intro to Sphinx](http://sphinxsearch.com/forum/view.html?id=3609) |
||||||
|
- [Documentation of Sphinx in ASP.NET](https://www.ericholscher.com/blog/2016/jul/1/sphinx-and-rtd-for-writers/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Search engines |
# Search Engines |
||||||
|
|
||||||
|
A search engine in an ASP.NET application is a tool or module that allows users to search for and retrieve specific information from the application's database or other data sources. Search engines can be used to perform full-text search, faceted search, and geospatial search, among other things. |
||||||
|
|
||||||
|
Search engines can be integrated into an ASP.NET application by using libraries or frameworks that provide a .NET client for interacting with the search engine. Some popular search engines that can be integrated with an ASP.NET application include Elasticsearch, Apache Solr, Sphinx, and Microsoft Azure Search. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Search Engine Optimization with ASP.NET](https://learn.microsoft.com/en-us/archive/msdn-magazine/2009/september/search-engine-optimization-with-asp-net-4-0-visual-studio-2010-and-iis7) |
||||||
|
- [Creating an ASP.NET Search Engine](https://www.developerfusion.com/article/4389/create-a-site-search-engine-in-aspnet/) |
||||||
|
- [Simple Search Engine in ASP.NET](https://www.youtube.com/watch?v=KTkubhS-u50) |
||||||
@ -1 +1,10 @@ |
|||||||
# Dynamodb |
# DynamoDB |
||||||
|
|
||||||
|
Amazon DynamoDB is a fully-managed, NoSQL database service provided by Amazon Web Services (AWS) that can be used to store and retrieve large amounts of data. It is a highly-scalable, fast, and flexible NoSQL database service that supports both document and key-value data models. |
||||||
|
|
||||||
|
DynamoDB is designed to handle extremely high levels of read and write throughput, and it automatically scales to accommodate the traffic of an application. It also provides built-in support for data replication, allowing data to be automatically spread across multiple availability zones for increased durability and availability. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Getting started with DynamoDB](https://aws.amazon.com/dynamodb/) |
||||||
|
- [Introduction to DynamoDB](https://cloudacademy.com/lab/introduction-dynamodb/) |
||||||
@ -1 +1,9 @@ |
|||||||
# Cosmosdb |
# CosmosDB |
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [What is Azure Cosmos DB?](https://intellipaat.com/blog/what-is-azure-cosmos-db/) |
||||||
|
- [Cosmos DB, Its Features, Benefits, Pricing etc](https://stackify.com/what-is-azure-cosmos-db/) |
||||||
|
- [Getting started with Cosmos DB](https://acloudguru.com/blog/engineering/azure-cosmos-db-lets-you-focus-on-the-good-stuff) |
||||||
@ -1 +1,11 @@ |
|||||||
# Cloud |
# Cloud |
||||||
|
|
||||||
|
Cloud in the context of ASP.NET refers to the use of cloud computing services to host and run ASP.NET web applications. Cloud computing is a model of delivering computing resources (such as servers, storage, and applications) over the internet on a pay-per-use basis. |
||||||
|
|
||||||
|
In the case of ASP.NET, cloud providers such as Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP) offer services specifically tailored to host and run ASP.NET web applications. These services include virtual machines, web roles, and serverless computing, which can be used to deploy and run ASP.NET web applications in the cloud. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Building a .NET Cloud Application](https://www.c-sharpcorner.com/article/building-the-net-cloud-application/) |
||||||
|
- [How to make a .NET Cloud Application?](https://dotnet.microsoft.com/en-us/apps/cloud) |
||||||
|
- [Getting started with Cloud](https://aws.amazon.com/free/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Postgresql |
# PostgreSQL |
||||||
|
|
||||||
|
PostgreSQL, often simply "Postgres", is an open-source relational database management system (RDBMS) emphasizing extensibility and SQL compliance. It was originally developed at the University of California, Berkeley in the 1980s and is now maintained by the PostgreSQL Global Development Group. |
||||||
|
|
||||||
|
Postgres is known for its robustness and reliability, as well as its support for advanced features such as concurrency control, full-text search, and geospatial data. It is also highly extensible, allowing developers to create custom functions and operators in a variety of programming languages, including C, Python, and JavaScript. |
||||||
|
|
||||||
|
For more information, visit the following resources: |
||||||
|
|
||||||
|
- [Postgresql - Open Source Relational Database](https://www.postgresql.org/) |
||||||
|
- [What is Postgresql?](postgresqltutorial.com/postgresql-getting-started/what-is-postgresql/) |
||||||
|
- [Introduction, Advantages & Disadvantages of PostgreSQL](https://guru99.com/introduction-postgresql.htmlPostgresql) |
||||||
@ -1 +1,11 @@ |
|||||||
# Mariadb |
# MariaDB |
||||||
|
|
||||||
|
MariaDB is an open-source relational database management system (RDBMS) that is a fork of the MySQL database. It is fully compatible with MySQL, but it also includes additional features and improvements. MariaDB is developed and maintained by the MariaDB Corporation and the MariaDB community, and it is widely used as a replacement for MySQL in many web and enterprise applications. |
||||||
|
|
||||||
|
In an ASP.NET application, MariaDB can be used as the underlying database for storing and retrieving data. There are several libraries available for integrating MariaDB with an ASP.NET application, such as MariaDB.Data, MySql.Data, and Dapper. These libraries provide a .NET client for MariaDB, which can be used to interact with the MariaDB database from within an ASP.NET application. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [How to use MariaDB in ASP.NET?](https://blog.georgekosmidis.net/using-mariadb-in-an-aspnet-core-api-with-entity-framework-core.html) |
||||||
|
- [Working with MariaDB and .Net](https://mariadb.com/kb/en/mariadb-and-net/) |
||||||
|
- [Building an application with ASP.NET & MariaDB](https://medium.com/@BMatt92656920/building-a-web-application-with-asp-net-core-mvc-entity-framework-core-mariadb-bootstrap-a2bf0927d20e) |
||||||
@ -1 +1,11 @@ |
|||||||
# Mysql |
# MySQL |
||||||
|
|
||||||
|
MySQL is an open-source relational database management system (RDBMS) that is widely used in web and enterprise applications. It is developed, distributed, and supported by Oracle Corporation. MySQL provides a rich set of features to handle high-performance, high-availability, and high-scalability requirements of modern web applications. |
||||||
|
|
||||||
|
In an ASP.NET application, MySQL can be used as the underlying database for storing and retrieving data. There are several libraries available for integrating MySQL with an ASP.NET application, such as MySql.Data, Dapper and EF Core. These libraries provide a .NET client for MySQL, which can be used to interact with the MySQL database from within an ASP.NET application. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Getting started with ASP.NET Core and MySQL](https://dev.mysql.com/blog-archive/getting-started-with-asp-net-core-and-mysql-connectornet/) |
||||||
|
- [MySql database connectivity with ASP.Net](https://www.c-sharpcorner.com/UploadFile/brij_mcn/mysql-database-connectivity-with-Asp-Net/) |
||||||
|
- [How To Connect MySQL With ASP.NET](https://www.youtube.com/watch?v=g5rVd1JGbIg) |
||||||
@ -1 +1,10 @@ |
|||||||
# Relational |
# Relational |
||||||
|
|
||||||
|
A relational database is a type of database that stores data in a structured format, using tables and relationships between them. It is based on the relational model, which organizes data into one or more tables, with each table consisting of a set of rows and columns. |
||||||
|
|
||||||
|
The main feature of a relational database is the ability to establish relationships between tables, using a feature called a foreign key. A foreign key is a column or set of columns in one table that is used to link to the primary key of another table. This allows data to be spread across multiple tables, but still be connected and easily accessed through these relationships. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Introduction to Working with Database in ASP.NET](https://learn.microsoft.com/en-us/aspnet/web-pages/overview/data/5-working-with-data) |
||||||
|
- [Implement a Relational Database with ASP.NET](https://openclassrooms.com/en/courses/5671811-implement-a-relational-database-with-asp-net-core) |
||||||
@ -1 +1,11 @@ |
|||||||
# Redis |
# Redis |
||||||
|
|
||||||
|
Redis (Remote Dictionary Server) is an open-source, in-memory data structure store that can be used as a database, cache, and message broker. It supports various data structures such as strings, hashes, lists, sets, and sorted sets. |
||||||
|
|
||||||
|
In an ASP.NET application, Redis can be used as a caching mechanism to store frequently accessed data in memory, rather than reading it from a slower storage system like a traditional relational database. This can greatly improve the performance of an application by reducing the number of database queries and the amount of data that needs to be read from disk. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Redis OM .NET](https://redis.io/docs/stack/get-started/tutorials/stack-dotnet/) |
||||||
|
- [Caching in ASP.NET using Redis](https://www.codemag.com/Article/2205091/Distributed-Caching-in-ASP.NET-Core-6-Using-Redis-in-Azure) |
||||||
|
- [Getting started in Redis with .NET](https://docs.redis.com/latest/rs/references/client_references/client_csharp/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Mongodb |
# MongoDB |
||||||
|
|
||||||
|
MongoDB is a cross-platform, open-source, NoSQL document-oriented database that can be used to store and retrieve large amounts of data. It uses a flexible, JSON-like data structure called BSON (binary JSON) and it is designed to handle large amounts of unstructured data. |
||||||
|
|
||||||
|
In an ASP.NET application, MongoDB can be used as a data store to persist and retrieve application data. There are several libraries available for integrating MongoDB with an ASP.NET application, such as MongoDB.Driver and C# MongoDB Driver. These libraries provide a .NET client for MongoDB, which can be used to interact with the MongoDB server from within an ASP.NET application. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Use MongoDB in Your C# ASP.NET Apps](https://developer.okta.com/blog/2020/01/02/mongodb-csharp-aspnet-datastore) |
||||||
|
- [MongoDB With ASP.NET Core Web API](https://www.c-sharpcorner.com/article/using-mongodb-with-asp-net-core-web-api/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Litedb |
# LiteDB |
||||||
|
|
||||||
|
LiteDB is a lightweight, open-source, NoSQL embedded document-oriented database engine for .NET and .NET Core. It uses a file-based storage system, meaning that the entire database is stored in a single file on disk. It uses a similar syntax to MongoDB, but it is designed to be simple and easy to use, and it does not require a separate server or installation. |
||||||
|
|
||||||
|
LiteDB supports data types like string, int, decimal, DateTime, and also supports binary data and serialized objects. It also supports LINQ, transactions, indexes and collections. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Getting started with LiteDB](https://www.litedb.org/) |
||||||
|
- [Overview of LiteDB in ASP.NET](https://www.litedb.org/docs/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Cassandra |
# Cassandra |
||||||
|
|
||||||
|
Apache Cassandra is a free and open-source, NoSQL, distributed, wide-column store, and high-performance database management system designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. It is designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. |
||||||
|
|
||||||
|
Cassandra is a column-family store and it stores data in a structured format, using tables and columns. It is based on a data model that is similar to that of Google's Bigtable, and it provides a query language that is similar to SQL. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Introduction to Cassandra](https://www.tutorialspoint.com/cassandra/cassandra_introduction.htm) |
||||||
|
- [Overview of Cassandra in ASP.NET](https://www.spiceworks.com/tech/big-data/articles/what-is-cassandra/) |
||||||
|
- [Introduction to Apache Cassandra](https://www.geeksforgeeks.org/introduction-to-apache-cassandra/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Ravendb |
# RavenDB |
||||||
|
|
||||||
|
RavenDB is an open-source, NoSQL document database designed for the .NET platform. It is a document database, which means that it stores data in semi-structured JSON format, and it is designed to be simple and easy to use. It is also a multi-model database, which allows you to store and query data using a variety of data models, including document, key-value, graph, and column-family. |
||||||
|
|
||||||
|
In an ASP.NET application, RavenDB can be used as a data store to persist and retrieve application data. There are several libraries available for integrating RavenDB with an ASP.NET application, such as RavenDB.Client, which provides a .NET client for RavenDB that can be used to interact with the RavenDB server from within an ASP.NET application. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Using RavenDB in ASP.NET Applications](https://www.codeguru.com/dotnet/using-ravendb-in-asp-net-applications/) |
||||||
|
- [Getting started with RavenDB](https://ravendb.net/docs/article-page/5.4/csharp/start/getting-started) |
||||||
|
- [Using RavenDB Unit of Work and .NET Core MVC](https://ayende.com/blog/187906-B/using-ravendb-unit-of-work-and-net-core-mvc) |
||||||
@ -1 +1,11 @@ |
|||||||
# Couchdb |
# CouchDB |
||||||
|
|
||||||
|
CouchDB is an open-source, NoSQL document database designed for the web. It uses a document-oriented data model, which means that it stores data in semi-structured JSON format, and it is designed to be simple and easy to use. CouchDB provides a built-in web interface, called Futon, which can be used to interact with the database, and it also provides an HTTP API that can be used to interact with the database from an ASP.NET application. |
||||||
|
|
||||||
|
In an ASP.NET application, CouchDB can be used as a data store to persist and retrieve application data. There are several libraries available for integrating CouchDB with an ASP.NET application, such as Couchbase, which provides a .NET client for CouchDB that can be used to interact with the CouchDB server from within an ASP.NET application. |
||||||
|
|
||||||
|
|
||||||
|
Visit the following resources to learn more: |
||||||
|
|
||||||
|
- [CouchDB in ASP.NET Core Application](https://www.c-sharpcorner.com/article/crud-operation-to-couchdb-via-rest-api-in-asp-net-core-application/) |
||||||
|
- [Use CouchDB with .NET](https://stackoverflow.com/questions/1050152/use-couchdb-with-net) |
||||||
@ -1 +1,11 @@ |
|||||||
# Nosql |
# Nosql |
||||||
|
|
||||||
|
NoSQL (Not Only SQL) is a type of database that does not use the traditional table-based relational model. It is designed to handle large amounts of unstructured or semi-structured data, and it is often used in big data and real-time web applications. NoSQL databases are highly scalable and can handle high-performance needs and large data sets. |
||||||
|
|
||||||
|
There are several types of NoSQL databases, such as document databases, key-value databases, graph databases, and column-family databases, each with their own unique features and use cases. Some examples of NoSQL databases include MongoDB, Cassandra, RavenDB, CouchDB, and Redis. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [NoSQL in .NET Applications](https://www.slideshare.net/shijucv/nosql-database-in-net-apps) |
||||||
|
- [Open Source NoSQL Database for .NET](https://www.alachisoft.com/nosdb/) |
||||||
|
- [Use NoSQL databases in ASP.NET](https://learn.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/nosql-database-persistence-infrastructure) |
||||||
@ -1 +1,18 @@ |
|||||||
# Databases |
# Databases |
||||||
|
|
||||||
|
In an ASP.NET application, there are several types of databases that can be used to store and retrieve data. Some of the most commonly used databases include: |
||||||
|
|
||||||
|
- Relational databases |
||||||
|
- NoSQL databases |
||||||
|
- In-memory databases |
||||||
|
- Embedded databases |
||||||
|
- Cloud-based databases |
||||||
|
|
||||||
|
Each database type has its own set of features and use cases, and the choice of which database to use will depend on the specific requirements of the application. |
||||||
|
|
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [ASP.NET Database Tutorial](https://www.guru99.com/insert-update-delete-asp-net.html) |
||||||
|
- [Introduction to Working with a Database in ASP.NET](https://learn.microsoft.com/en-us/aspnet/web-pages/overview/data/5-working-with-data) |
||||||
|
- [ASP.NET Web Pages - Databases](https://www.w3schools.com/asp/webpages_database.asp) |
||||||
@ -1 +1,9 @@ |
|||||||
# Serilog |
# Serilog |
||||||
|
|
||||||
|
Serilog is a third-party logging library for ASP.NET Core that allows developers to easily create structured and searchable log data. It is built on top of the `Microsoft.Extensions.Logging` framework, which is included in ASP.NET Core. Serilog provides features such as automatic logging of request and response data, and the ability to write logs to a variety of destinations, including the console, files, and various logging services. It also supports for filtering and formatting log messages. |
||||||
|
|
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [How to Work with Serilog in ASP.NET?](https://www.codeguru.com/dotnet/serilog-c-sharp/) |
||||||
|
- [Complete guide to Serilog in ASP.NET](https://github.com/serilog/serilog-aspnetcore) |
||||||
|
- [Advanced Serilog features in ASP.NET](https://www.infoworld.com/article/3624022/how-to-use-advanced-serilog-features-in-aspnet-core-mvc.html) |
||||||
@ -1 +1,11 @@ |
|||||||
# Nlog |
# NLog |
||||||
|
|
||||||
|
NLog is an open-source logging library for .NET applications, including ASP.NET. It is designed to be easy to use, highly configurable, and extensible, and it provides a number of features that help developers to log and analyze data in their applications. |
||||||
|
|
||||||
|
NLog is a powerful, flexible, and easy-to-use logging library that can be used in ASP.NET applications to provide detailed log data. It allows developers to easily configure their logging pipeline, and to write log data to a variety of destinations, making it easier to analyze and troubleshoot issues in the application. |
||||||
|
|
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [Logging with NLog in ASP.NET](https://codewithmukesh.com/blog/logging-with-nlog-in-aspnet-core/) |
||||||
|
- [Introduction To NLog With ASP.NET Core](https://www.c-sharpcorner.com/article/introduction-to-nlog-with-asp-net-core2/) |
||||||
|
- [Tutorial of Nlog with ASP.NET](https://www.youtube.com/watch?v=PnlxRmHg0lU) |
||||||
@ -1 +1,13 @@ |
|||||||
# Elk stack |
# ELK Stack |
||||||
|
|
||||||
|
The ELK Stack is a collection of three open-source products — Elasticsearch, Logstash, and Kibana. ELK stack provides centralized logging in order to identify problems with servers or applications. It allows you to search all the logs in a single place. It also helps to find issues in multiple servers by connecting logs during a specific time frame. |
||||||
|
|
||||||
|
- **E** stands for ElasticSearch: used for storing logs |
||||||
|
- **L** stands for LogStash : used for both shipping as well as processing and storing logs |
||||||
|
- **K** stands for Kibana: is a visualization tool (a web interface) which is hosted through Nginx or Apache |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [What Is Elk?](https://aws.amazon.com/what-is/elk-stack/) |
||||||
|
- [Complete Guide to Elk](https://logz.io/learn/complete-guide-elk-stack/) |
||||||
|
- [ELK Stack Tutorial: What is Kibana, Logstash & Elasticsearch?](https://www.guru99.com/elk-stack-tutorial.html) |
||||||
@ -1 +1,11 @@ |
|||||||
# Sentry |
# Sentry |
||||||
|
|
||||||
|
Sentry is an open-source error tracking platform that helps developers identify and fix errors in their applications. It provides detailed error reports, including stack traces, context data, and user feedback, making it easy to understand and reproduce errors. Sentry can be integrated with a variety of platforms, including .NET and ASP.NET. |
||||||
|
|
||||||
|
In an ASP.NET application, Sentry can be used to capture and track errors that occur in the application. Sentry provides an SDK, called Sentry.NET, which can be integrated with an ASP.NET application to automatically capture and track errors. The SDK can be configured to capture and track different types of errors, including unhandled exceptions, handled exceptions, and custom events. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Sentry Documentation in .NET](https://docs.sentry.io/platforms/dotnet/) |
||||||
|
- [ASP.NET and Sentry](https://docs.sentry.io/platforms/dotnet/guides/aspnetcore/) |
||||||
|
- [Usage of Sentry in ASP.NET](https://docs.sentry.io/platforms/dotnet/guides/aspnetcore/usage/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Datadog |
# Datadog |
||||||
|
|
||||||
|
Datadog is a cloud-based monitoring and analytics platform that helps organizations to monitor, troubleshoot, and optimize their applications and infrastructure. It provides a wide range of features including real-time monitoring, log management, tracing, and alerting, and it can be integrated with a variety of platforms, including .NET and ASP.NET. |
||||||
|
|
||||||
|
In an ASP.NET application, Datadog can be used to monitor and analyze the performance and behavior of the application. Datadog provides an SDK, called Datadog.Trace, which can be integrated with an ASP.NET application to automatically collect and report performance data. The SDK can be configured to report data such as request and response times, error rates, and custom metrics. |
||||||
|
|
||||||
|
Visit the following links: |
||||||
|
|
||||||
|
- [Documentation of Datadog](https://www.datadoghq.com/) |
||||||
|
- [Configuring the .NET Core with Datadog](https://docs.datadoghq.com/tracing/trace_collection/library_config/dotnet-core/?tab=environmentvariables) |
||||||
@ -1 +1,10 @@ |
|||||||
# Loggly |
# Loggly |
||||||
|
|
||||||
|
Loggly is a cloud-based log management and analytics platform that helps organizations to collect, store, and analyze log data from a variety of sources, including .NET and ASP.NET applications. It provides a wide range of features such as real-time log search and analysis, alerting, and reporting, and allows for easy integration with other tools such as Datadog, Splunk, and New Relic. |
||||||
|
|
||||||
|
In an ASP.NET application, Loggly can be used to collect and analyze log data. Loggly provides an SDK, called Loggly.Serilog, which can be integrated with an ASP.NET application to automatically collect log data and send it to Loggly. The SDK can be configured to collect different types of log data, such as log messages, error messages, and custom events. |
||||||
|
|
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [Loggly in ASP.NET Core using Serilog](https://itnext.io/loggly-in-asp-net-core-using-serilog-dc0e2c7d52eb) |
||||||
|
- [Using Loggly For Troubleshooting Bugs](https://www.loggly.com/blog/use-loggly-troubleshooting-bugs-code/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Elmah |
# ELMAH |
||||||
|
|
||||||
|
ELMAH (Error Logging Modules and Handlers) is an open-source error logging and management library for ASP.NET applications. It is designed to be easy to use and easy to integrate into existing ASP.NET applications. |
||||||
|
|
||||||
|
ELMAH is widely used for error logging, management and tracking in ASP.NET applications, it's easy to use, easy to integrate with existing applications, and provides a wealth of features that help developers to identify, diagnose and fix errors in their applications. |
||||||
|
|
||||||
|
For more resources, visit the following links: |
||||||
|
|
||||||
|
- [Introduction To ELMAH](https://www.c-sharpcorner.com/article/introduction-to-elmah-in-mvc/) |
||||||
|
- [How to Configure Elmah in ASP.net MVC](https://www.youtube.com/watch?v=oqheVBZR0PM) |
||||||
|
- [ELMAH Integration in ASP.NET MVC Application](https://www.ecanarys.com/Blogs/ArticleID/184/ELMAH-Integration-in-ASP-NET-MVC-Application) |
||||||
@ -1 +1,11 @@ |
|||||||
# Log management system |
# Log Management System |
||||||
|
|
||||||
|
A log management system is a software or service that is designed to collect, store, and analyze log data from a variety of sources. Logs are records of events that occur in a system, such as application logs, system logs, and network logs. Log management systems are used to gather, store and analyze these logs in order to provide insight into the performance, stability and security of a system. |
||||||
|
|
||||||
|
The use of log management system can help IT professionals to identify and troubleshoot issues, monitor performance, detect security threats and meet regulatory compliance requirements, also it's a fundamental part of IT infrastructure management, and provides a way to measure the health and security of the system. |
||||||
|
|
||||||
|
Visit the following resources for more information: |
||||||
|
|
||||||
|
- [Structured Logging and Logs Management in ASP.NET](https://medium.com/@stavsofer/structured-logging-and-logs-management-asp-net-core-serilog-seq-61109f740696) |
||||||
|
- [ASP.NET Logging Basics](https://www.loggly.com/ultimate-guide/net-logging-basics/) |
||||||
|
- [Logging and Monitoring in ASP.NET](https://www.pluralsight.com/courses/logging-monitoring-aspdotnet-core-6) |
||||||
@ -1 +1,16 @@ |
|||||||
# Log frameworks |
# Log Frameworks |
||||||
|
|
||||||
|
In ASP.NET, log frameworks are libraries that provide a way to log and analyze data in an application. Some popular log frameworks for ASP.NET include: |
||||||
|
|
||||||
|
- Serilog |
||||||
|
- NLog |
||||||
|
- Log4Net |
||||||
|
- ELMAH |
||||||
|
- Microsoft.Extensions.Logging |
||||||
|
|
||||||
|
These are some of the most popular log frameworks in ASP.NET, each of them has its own set of features and use cases, and the choice of which log framework to use will depend on the specific requirements of the application. |
||||||
|
|
||||||
|
Visit the following links to learn more: |
||||||
|
|
||||||
|
- [Implement logging in ASP.NET](https://learn.microsoft.com/en-us/training/modules/aspnet-logging/) |
||||||
|
- [ASP.NET Core: Logging with log4net](https://www.linkedin.com/learning/asp-dot-net-core-logging-with-log4net) |
||||||
|
|||||||
@ -1 +1,11 @@ |
|||||||
# Odata |
# OData |
||||||
|
|
||||||
|
OData (Open Data Protocol) is a web protocol for querying and updating data. It is an open standard for creating and consuming RESTful web services. OData is built on top of the HTTP protocol, and it uses the conventions of REST to expose data through a standard interface. |
||||||
|
|
||||||
|
In ASP.NET, OData can be used to create RESTful web services that expose data in a standardized way. OData provides a set of conventions for defining the structure of the data, and it also provides a set of conventions for querying and updating the data. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Create an OData v4 Endpoint Using ASP.NET](https://learn.microsoft.com/en-us/aspnet/web-api/overview/odata-support-in-aspnet-web-api/odata-v4/create-an-odata-v4-endpoint) |
||||||
|
- [Working with OData in ASP.NET Core](https://www.pluralsight.com/blog/software-development/odata-asp-net-core) |
||||||
|
- [Example of OData Protocol With ASP.NET Core](https://www.youtube.com/watch?v=L9HdnNCi0R0) |
||||||
@ -1 +1,10 @@ |
|||||||
# Sieve |
# Sieve |
||||||
|
|
||||||
|
Sieve is a language for filtering email messages, it's defined in the Internet standard, also it's called as Sieve: An Email Filtering Language. It provides a simple, human-readable syntax for specifying rules that determine what actions to take on incoming email messages. These actions can include filing messages into different folders, forwarding messages to other addresses, discarding messages, and more. |
||||||
|
|
||||||
|
Sieve is typically used in email servers and clients, and it can be used to implement server-side and client-side email filtering. It allows users to create their own rules for filtering email, without requiring access to the server's configuration or the need for complex server-side scripts. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Analysis of Sieve](https://en.wikipedia.org/wiki/Sieve_analysis) |
||||||
|
- [Sorting in a .NET Core API using Sieve](https://www.youtube.com/watch?v=x0utCah3cFk) |
||||||
@ -1 +1,11 @@ |
|||||||
# Rest |
# REST |
||||||
|
|
||||||
|
REST (Representational State Transfer) is an architectural style for building web services. It is based on the principles of the HTTP protocol, and it uses the conventions of HTTP to create a standard interface for interacting with web services. |
||||||
|
|
||||||
|
In ASP.NET, REST can be used to create web services that expose data in a standardized way. RESTful web services in ASP.NET are typically built using the Web API framework, which provides a set of libraries and tools for building RESTful web services. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [What is REST Services in ASP.NET?](http://www.codedigest.com/quick-start/16/what-is-rest-services-how-to-create-rest-services-in-aspnet) |
||||||
|
- [What are RESTful APIs?](https://www.pragimtech.com/blog/blazor/what-are-restful-apis/) |
||||||
|
- [Tutorial of Rest and Restful API](https://www.youtube.com/watch?v=4r1CIUs5s2I) |
||||||
@ -1 +1,11 @@ |
|||||||
# Grpc |
# gRPC |
||||||
|
|
||||||
|
gRPC is a high-performance, open-source framework for building remote procedure call (RPC) APIs. It uses the Protocol Buffers data serialization format and the HTTP/2 protocol to create highly efficient and scalable APIs. gRPC supports a variety of programming languages, including C# and ASP.NET. |
||||||
|
|
||||||
|
In ASP.NET, gRPC can be used to create high-performance, low-latency APIs for a variety of use cases. gRPC allows for bi-directional streaming of data, which can be useful for real-time applications such as gaming, financial trading, and more. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Overview for gRPC on .NET](https://learn.microsoft.com/en-us/aspnet/core/grpc/?view=aspnetcore-7.0) |
||||||
|
- [Getting Started with ASP.NET Core and gRPC](https://blog.jetbrains.com/dotnet/2021/07/19/getting-started-with-asp-net-core-and-grpc/) |
||||||
|
- [Create a gRPC client & server in ASP.NET](https://learn.microsoft.com/en-us/aspnet/core/tutorials/grpc/grpc-start?view=aspnetcore-7.0&tabs=visual-studio) |
||||||
@ -1 +1,10 @@ |
|||||||
# Graphql dotnet |
# GraphQL .NET |
||||||
|
|
||||||
|
GraphQL is a query language for your API, it allows clients to define the structure of the data they need, and the server will return only the requested data. It is an alternative to RESTful web services, and it is gaining popularity because of its flexibility and efficiency. |
||||||
|
|
||||||
|
In ASP.NET, GraphQL can be used to create web services that expose data in a more flexible and efficient way. GraphQL.NET is a popular open-source library that can be used to create GraphQL services in ASP.NET. This library provides a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. |
||||||
|
Learn more from the following resources: |
||||||
|
|
||||||
|
- [Introduction to GraphQL .NET in ASP.NET](https://graphql-dotnet.github.io/docs/getting-started/introduction/) |
||||||
|
- [How to use GraphQL in .NET?](https://softchris.github.io/pages/dotnet-graphql.html) |
||||||
|
- [Building and consuming GraphQL API in ASP.NET](https://www.red-gate.com/simple-talk/development/dotnet-development/building-and-consuming-graphql-api-in-asp-net-core-5/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Hot chocolate |
# Hot Chocolate |
||||||
|
|
||||||
|
Hot Chocolate is a GraphQL server implementation for .NET and .NET Core. It is an open-source library that provides a simple and flexible way to build GraphQL APIs in ASP.NET. |
||||||
|
|
||||||
|
Hot Chocolate provides a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. It also provides a number of features to help with things such as validation, authorization, caching, and more. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Getting started with HotChocolate](https://learn.microsoft.com/en-us/shows/on-net/getting-started-with-hotchocolate) |
||||||
|
- [ASP.NET Core and HotChocolate](https://chillicream.com/docs/hotchocolate/v12/api-reference/aspnetcore) |
||||||
|
- [Intro to HotChocolate](https://chillicream.com/docs/hotchocolate) |
||||||
@ -1 +1,11 @@ |
|||||||
# Graphql |
# GraphQL |
||||||
|
|
||||||
|
GraphQL is a query language for your API that allows clients to define the structure of the data they need, and the server will return only the requested data. It is an alternative to RESTful web services, and it is gaining popularity because of its flexibility and efficiency. |
||||||
|
|
||||||
|
In ASP.NET, GraphQL can be used to create web services that expose data in a more flexible and efficient way. There are several libraries available to implement GraphQL in an ASP.NET application, such as GraphQL.NET, Hot Chocolate, and others. These libraries provide a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [How to implement GraphQL in ASP.Net](https://blog.christian-schou.dk/how-to-implement-graphql-in-asp-net-core/) |
||||||
|
- [Intro to GraphQL](https://graphql-dotnet.github.io/docs/getting-started/introduction/) |
||||||
|
- [Developing API In .NET Core With GraphQL](https://www.c-sharpcorner.com/article/building-api-in-net-core-with-graphql2/) |
||||||
@ -1 +1,13 @@ |
|||||||
# Api clients |
# API Clients |
||||||
|
|
||||||
|
API clients in ASP.NET are software libraries that allow applications to interact with external APIs. They provide a set of methods and classes that make it easy to send requests to an API and process the responses. |
||||||
|
|
||||||
|
API clients can be used to access a wide variety of services, such as web services, cloud services, and social media platforms. They can be used to perform tasks such as fetching data, posting updates, and deleting resources. |
||||||
|
|
||||||
|
API clients in ASP.NET are typically built using the HttpClient class, which is part of the System.Net.Http namespace. This class provides a set of methods for sending HTTP requests and receiving HTTP responses. |
||||||
|
|
||||||
|
Visit the following links to learn more: |
||||||
|
|
||||||
|
- [How to Call a Web API From a .NET Client](https://learn.microsoft.com/en-us/aspnet/web-api/overview/advanced/calling-a-web-api-from-a-net-client) |
||||||
|
- [Overview of Web API REST Service in ASP.NET](https://www.c-sharpcorner.com/article/consuming-asp-net-web-api-rest-service-in-asp-net-mvc-using-http-client/) |
||||||
|
- [Building an ASP.NET Web API With ASP.NET](https://www.toptal.com/asp-dot-net/asp-net-web-api-tutorial) |
||||||
@ -1 +1,11 @@ |
|||||||
# Web sockets |
# Web Sockets |
||||||
|
|
||||||
|
WebSockets is a protocol that allows for real-time, bidirectional communication between a client and a server. It is based on the same principle as HTTP, but it uses a different protocol to establish and maintain a connection between the client and the server. Once a connection is established, WebSockets enables the client and server to send messages to each other in real-time. |
||||||
|
|
||||||
|
In ASP.NET, WebSockets can be used to create real-time, highly interactive web applications. The ASP.NET Core framework provides built-in support for WebSockets through the Microsoft.AspNetCore.WebSockets package. This package provides a set of classes and methods that make it easy to create and manage WebSockets connections. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [WebSockets support in ASP.NET](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/websockets?view=aspnetcore-7.0) |
||||||
|
- [Understanding WebSockets with ASP.NET](https://sahansera.dev/understanding-websockets-with-aspnetcore-5/) |
||||||
|
- [Writing a WebSocket server in ASP.NET](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_server) |
||||||
@ -1 +1,7 @@ |
|||||||
# Singlar core |
# SignalR Core |
||||||
|
|
||||||
|
SignalR is a real-time communication library for .NET that allows for the creation of real-time web applications. SignalR Core is the latest version of SignalR, which has been rebuilt from the ground up to be cross-platform and lightweight. It allows for bidirectional communication between a client (such as a web page) and a server, enabling real-time updates, notifications, and other interactions. SignalR Core can be used in a variety of scenarios such as chat applications, gaming, and real-time dashboards. It supports multiple transports like WebSockets, Server-Sent Events and Long polling. It also supports for authentication and authorization. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Overview of ASP.NET Core SignalR](https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-7.0) |
||||||
@ -1 +1,10 @@ |
|||||||
# Real time communication |
# Real Time Communication |
||||||
|
|
||||||
|
Real-time communication in ASP.NET refers to the ability to send and receive data between a client and a server in real-time, typically with low latency. It allows the server to push updates to the client as they happen, instead of the client having to continuously poll the server for updates. |
||||||
|
|
||||||
|
There are several technologies and libraries available for implementing real-time communication in ASP.NET, such as WebSockets, SignalR, gRPC, and more. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Overview of ASP.NET Core SignalR](https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-7.0) |
||||||
|
- [Real-time ASP.NET with SignalR](https://dotnet.microsoft.com/en-us/apps/aspnet/signalr) |
||||||
@ -1 +1,11 @@ |
|||||||
# Atuo mapper |
# AutoMapper |
||||||
|
|
||||||
|
AutoMapper is a library for .NET that allows you to easily map between objects of different types. It is particularly useful when working with domain models and data transfer objects (DTOs) in a layered architecture. It can also be used to map between different versions of an object, or to map between objects in different formats, such as JSON and XML. |
||||||
|
|
||||||
|
AutoMapper uses a convention-based approach to mapping, which means that it automatically maps properties with the same name and type from one object to another. It also provides a fluent API for configuring more complex mappings, such as ignoring certain properties, using custom logic to map properties, or mapping properties based on a value in another property. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [What is Automapper in ASP.NET?](https://www.simplilearn.com/tutorials/asp-dot-net-tutorial/automapper-in-c-sharp) |
||||||
|
- [Getting Started with AutoMapper in ASP.NET](https://code-maze.com/automapper-net-core/) |
||||||
|
- [Examples of AutoMapper in ASP.NET](https://dotnettutorials.net/lesson/automapper-in-c-sharp/) |
||||||
@ -1 +1,10 @@ |
|||||||
# Express mapper |
# Express Mapper |
||||||
|
|
||||||
|
ExpressMapper is an open-source object-to-object mapping library for .NET, similar to AutoMapper. It allows you to easily map between objects of different types, and it is particularly useful when working with domain models and data transfer objects (DTOs) in a layered architecture. |
||||||
|
|
||||||
|
ExpressMapper uses a convention-based approach to mapping, which means that it automatically maps properties with the same name and type from one object to another. It also provides a fluent API for configuring more complex mappings, such as ignoring certain properties, using custom logic to map properties, or mapping properties based on a value in another property. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Intro to Express Mapper](https://expressmapper.org/) |
||||||
|
- [Express Mapper - The New .NET Mapper](https://www.codeproject.com/Tips/1009198/Expressmapper-The-New-NET-Mapper) |
||||||
@ -1 +1,10 @@ |
|||||||
# Agile mapper |
# Agile Mapper |
||||||
|
|
||||||
|
AgileMapper is an open-source, convention-based object-to-object mapping library for .NET, similar to AutoMapper and ExpressMapper. It allows you to easily map between objects of different types, and it is particularly useful when working with domain models and data transfer objects (DTOs) in a layered architecture. |
||||||
|
|
||||||
|
AgileMapper uses a convention-based approach to mapping, which means that it automatically maps properties with the same name and type from one object to another. It also provides a fluent API for configuring more complex mappings, such as ignoring certain properties, using custom logic to map properties, or mapping properties based on a value in another property. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Comparison of Object Mapper Libraries](https://www.simplilearn.com/tutorials/asp-dot-net-tutorial/automapper-in-c-sharp) |
||||||
|
- [Overview of Agile Mapper](https://readthedocs.org/projects/agilemapper/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Mapster |
# Mapster |
||||||
|
|
||||||
|
Mapster is an open-source, high-performance object-to-object mapping library for .NET, similar to AutoMapper, ExpressMapper, AgileMapper, and AgileMapster. It allows you to easily map between objects of different types, and it is particularly useful when working with domain models and data transfer objects (DTOs) in a layered architecture. |
||||||
|
|
||||||
|
Mapster uses a convention-based approach to mapping, which means that it automatically maps properties with the same name and type from one object to another. It also provides a fluent API for configuring more complex mappings, such as ignoring certain properties, using custom logic to map properties, or mapping properties based on a value in another property. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Getting Started With Mapster in ASP.NET](https://code-maze.com/mapster-aspnetcore-introduction/) |
||||||
|
- [Overview of Mapster in .Net ](https://medium.com/@M-S-2/enjoy-using-mapster-in-net-6-2d3f287a0989) |
||||||
|
- [Introduction to Mapster](youtube.com/watch?v=bClE7Uon9e8) |
||||||
@ -1 +1,11 @@ |
|||||||
# Object mapping |
# Object Mapping |
||||||
|
|
||||||
|
Object mapping in ASP.NET refers to the process of converting an object of one type to an object of another type. This can be useful in a number of scenarios, such as when working with domain models and data transfer objects (DTOs) in a layered architecture, or when mapping between different versions of an object or different formats such as JSON and XML. |
||||||
|
|
||||||
|
There are several libraries available for object mapping in ASP.NET, such as AutoMapper, ExpressMapper, AgileMapper, AgileMapster and Mapster. These libraries provide a convenient and flexible way to map between objects, using a convention-based approach or a fluent API to configure more complex mappings. They also support for a wide range of mapping scenarios, including nested and circular object graphs, collections, and different types of inheritance. |
||||||
|
|
||||||
|
Visit the following links to learn more: |
||||||
|
|
||||||
|
- [Building a Fast Object-to-Object Mapper in .NET](https://www.twilio.com/blog/building-blazing-fast-object-mapper-c-sharp-net-core) |
||||||
|
- [Overview of Object Mapping in ASP.NET](https://docs.abp.io/en/abp/latest/Object-To-Object-Mapping) |
||||||
|
- [Comparison of Object Mapper Libraries](https://www.simplilearn.com/tutorials/asp-dot-net-tutorial/automapper-in-c-sharp) |
||||||
@ -1 +1,11 @@ |
|||||||
# Hangfire |
# Hangfire |
||||||
|
|
||||||
|
Hangfire is an open-source, lightweight library for .NET that allows you to easily perform background processing in your ASP.NET application. It provides a simple and elegant way to run background jobs, schedule future tasks, and monitor the progress of your background jobs. |
||||||
|
|
||||||
|
Hangfire uses a storage backend, such as SQL Server or Redis, to persist the state of your background jobs. This allows you to easily scale your background processing and to monitor and manage your background jobs, even if your application restarts or crashes. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Hangfire with ASP.NET Core](https://code-maze.com/hangfire-with-asp-net-core/) |
||||||
|
- [Intro to Hangfire](https://www.partech.nl/nl/publicaties/2021/05/a-beginners-guide-to-hangfire) |
||||||
|
- [How to use Hangfire with ASP.NET](https://blog.christian-schou.dk/how-to-use-hangfire-with-asp-net-core-5-0-api/) |
||||||
@ -1 +1,11 @@ |
|||||||
# Native background service |
# Native Background Service |
||||||
|
|
||||||
|
A Native Background Service in ASP.NET is a type of service that can run in the background on a device, without the need for an active user session. These services are typically used for tasks that need to run continuously, such as sending notifications, polling for updates, or processing data. |
||||||
|
|
||||||
|
In ASP.NET, a Native Background Service can be implemented using the IHostedService interface, which is part of the Microsoft.Extensions.Hosting namespace. This interface allows you to create a background service that can run continuously, even when the main application is not running. |
||||||
|
|
||||||
|
Visit the following links to learn more: |
||||||
|
|
||||||
|
- [Background tasks with hosted services in ASP.NET](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/hosted-services?view=aspnetcore-7.0&tabs=visual-studio) |
||||||
|
- [BackgroundService in ASP.NET Core](https://medium.com/@daniel.sagita/backgroundservice-for-a-long-running-work-3debe8f8d25b) |
||||||
|
- [Tutorial on Background Tasks in ASP.NET](youtube.com/watch?v=rugxQIH_p3A) |
||||||
@ -1 +1,10 @@ |
|||||||
# Quartz |
# Quartz |
||||||
|
|
||||||
|
Quartz is an open-source, job scheduling library for .NET that can be used in ASP.NET applications. It is based on the popular Quartz scheduler for Java, and provides a similar feature set for scheduling and executing background jobs in .NET applications. |
||||||
|
|
||||||
|
With Quartz, you can schedule jobs to run at specific times or intervals, and you can also set up triggers to start a job based on certain events. Quartz also provides a rich set of options for configuring and managing your jobs, such as pausing, resuming, and canceling jobs, as well as job chaining and priorities. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Intro to Quartz in ASP.NET](https://aspnetboilerplate.com/Pages/Documents/Quartz-Integration) |
||||||
|
- [How to work with Quartz.Net in ASP.NET](https://www.infoworld.com/article/3078781/how-to-work-with-quartz-net-in-c.html) |
||||||
@ -1 +1,11 @@ |
|||||||
# Coravel |
# Coravel |
||||||
|
|
||||||
|
Coravel is an open-source, lightweight library for .NET that allows you to easily perform background processing and scheduling in your ASP.NET Core application. It provides a simple and elegant way to schedule tasks, run background jobs, and manage queues in your application. |
||||||
|
|
||||||
|
Coravel is inspired by Laravel's task scheduler and it's built on top of the .NET Core built-in Dependency Injection. It uses a fluent API to schedule tasks, allowing you to easily specify the frequency, start time, and end time of the task. It also provides a simple way to queue and process background jobs, allowing you to easily process large amounts of data or perform long-running tasks. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Documentation of Coravel](https://docs.coravel.net/) |
||||||
|
- [ASP.NET Task Scheduling with Coravel](https://www.youtube.com/watch?v=vu0fxlWl0wo) |
||||||
|
- [How to Run a .Net Console App with Coravel](https://www.youtube.com/watch?v=KQpw_OYkKq8) |
||||||
@ -1 +1,10 @@ |
|||||||
# Task scheduling |
# Task Scheduling |
||||||
|
|
||||||
|
Task scheduling in ASP.NET refers to the process of scheduling and executing background tasks in an application. This can include tasks such as sending emails, processing data, generating reports, or performing maintenance tasks. |
||||||
|
|
||||||
|
In ASP.NET, task scheduling can be implemented using a variety of libraries and frameworks such as Quartz.NET, Hangfire, Coravel and Microsoft's built-in IHostedService interface. These libraries and frameworks provide a way to schedule tasks to run at specific times or intervals, and also provide APIs for managing and monitoring the progress of scheduled tasks. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Task Scheduling in ASP.NET](https://www.youtube.com/watch?v=Vg4AOpb7OqA) |
||||||
|
- [How schedule Tasks in ASP.NET?](https://beansoftware.com/ASP.NET-Tutorials/Scheduled-Tasks.aspx) |
||||||
@ -1 +1,8 @@ |
|||||||
# Selenium |
# Selenium |
||||||
|
|
||||||
|
Selenium is an open-source library that allows developers to automate web browsers and simulate user interactions, it's commonly used for testing web applications. It can be integrated with .NET and provides a .NET binding for interacting with the Selenium API. The Selenium WebDriver API for .NET allows developers to write tests for web applications in C# or other .NET languages and supports various programming paradigms like Page Object Model. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Automated UI Tests with Selenium and ASP.NET](https://code-maze.com/selenium-aspnet-core-ui-tests/) |
||||||
|
- [Selenium Web Driver in .NET](https://stephan-bester.medium.com/automated-testing-with-selenium-web-driver-in-net-bde6854d3207) |
||||||
@ -1 +1,9 @@ |
|||||||
# Playwright |
# Playwright |
||||||
|
|
||||||
|
Playwright is an open-source library for automating web browsers built by Microsoft, similar to Selenium, it's commonly used for testing web applications. It's built on top of the .NET Core runtime and it provides bindings for C#, it allows developers to write tests for web applications in C# or other .NET languages. Playwright is designed to be fast and reliable and allows developers to run tests in multiple browsers. |
||||||
|
|
||||||
|
To learn more, visit the following: |
||||||
|
|
||||||
|
- [Playwright for .NET](https://github.com/microsoft/playwright-dotnet) |
||||||
|
- [How to test Apps with Playwright and .NETs](https://www.twilio.com/blog/test-web-apps-with-playwright-and-csharp-dotnet) |
||||||
|
- [End-to-End Tests With ASP.NET and Playwright](https://khalidabuhakmeh.com/end-to-end-test-with-aspnet-core-xunit-and-playwright) |
||||||
@ -1 +1,8 @@ |
|||||||
# Puppeteer |
# Puppeteer |
||||||
|
|
||||||
|
Puppeteer is an open-source library for automating web browsers, similar to Selenium and Playwright. It's built on top of the Chrome DevTools protocol and it provides a set of APIs that allows developers to interact with web browsers and simulate user interactions, such as clicking buttons, filling out forms, and navigating between pages. It's commonly used for testing web applications, web scraping, and generating screenshots and PDFs of web pages. Puppeteer for .NET is built on top of the .NET Core runtime and it provides bindings for C# and allows developers to write tests for web applications in C# or other .NET languages. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Why use Puppeteer?](https://www.kiltandcode.com/puppeteer-sharp-crawl-the-web-using-csharp-and-headless-chrome/) |
||||||
|
- [Documentations of Puppeteer](https://www.puppeteersharp.com/) |
||||||
@ -1 +1,8 @@ |
|||||||
# Cypress |
# Cypress |
||||||
|
|
||||||
|
Cypress is an open-source end-to-end testing framework for web applications, it's built on top of JavaScript and provides a set of APIs that allows developers to automate browser interactions. It's commonly used for testing web applications, as it can be used to automate browser-based tests and assert that the application behaves as expected. Cypress for .NET is not built on top of the .NET Core runtime and it does not provide bindings for C# or any other .NET languages, it's built on top of JavaScript and can be run in the browser. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [Cypress - End To End Testing Tool](https://www.c-sharpcorner.com/article/getting-started-with-cypress-io/) |
||||||
|
- [Overview of Cypress](https://www.cypress.io/) |
||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue