41 packages returned for Tags:"Abstract"

An abstract/virtual filesystem framework with many built-ins filesystems for .NET

Provides an abstract multi-dimensional modeling infrastructure, containing extensible model elements like dimensions, classifiers, and value types. Typically used areas and classes/interfaces/services: - IModelSpace, IClassifier, IAnnotation, IProperty, IMethod, IParameter.... More information

Nibiru is a library to help application development.

Exposing different methods interfaces to execute on a Mongo database

Common node patterns and utilities for VVVV

A Library of classes to allow strongly typed class building.

Test Support elements for developing well achitected, developer focussed Umbraco solutions with Umbraco.Pylon.

An Abstract Repository Implmentation for Entity Framework, with Entity2DTO / DTO2Entity conversion. Sources included.

Exposing different methods interfaces to validate Models based on Third party library (Fluent Validation)

Abstract components that provide a common member base to our various Blazor component types.

An abstract package for accessing database using System.Data. The interfaces are database independent and they contain many methods which simplifies writing code. They help writing loosely coupled and unit testable code. The assembly is signed and CLS compliant.

A significant abstraction over integrating any relational database into a .NET application, to the point of query-free interactions where tables are merely classes.

The MySql adapter of the Quermine library.

Abstract DataBase Layer for SQL Server, MySQL and ODBC in C#.

The Sqlite adapter of the Quermine library.

Abstractions for Repository pattern

Abstract classes to use for domain models of Milaneze.DomainModel.* namespaces.

Library of helpers for testing

Library of helpers for testing using the Moq mocking framework

The class4js module is for class-driven development in JavaScript. It allows to emulate classes in JavaScript. Module is based on ECMAScript 5 standart and implements open/close principle: "A module should be open for extension but closed for modifications".