Are you tired of choosing between simplicity and functionality when it comes to Object-Relational Mappers (ORMs)? Meet Vitorm, the lightweight yet comprehensive ORM designed to offer you the best of both worlds.

source address: https://github.com/Vit-Orm/Vitorm

What is Vitorm?

Vitorm is a lightweight ORM that strikes the perfect balance between simplicity and functionality. It’s inspired by the minimalist design of Dapper, offering an easy-to-use and efficient interface for data access. But Vitorm doesn’t stop there. It goes beyond the basic capabilities of lightweight ORMs to provide a rich feature set comparable to Entity Framework.

Why Choose Vitorm?

• Simplicity and Efficiency: With a design reminiscent of Dapper, Vitorm ensures you can quickly and efficiently perform data access tasks without the overhead of complex configurations.
• Robust Features: Similar to Entity Framework, Vitorm offers a comprehensive set of features, including advanced querying, relationship mapping, and change tracking.
• Performance: Get the high performance and speed you expect from a lightweight ORM while still enjoying the advanced capabilities typically found in more heavyweight solutions.

Key Features

• Easy-to-Use Interface: Intuitive and straightforward, making it accessible for developers of all skill levels.
• Advanced Querying: Supports complex queries, ensuring you can handle any data access scenario.
• Relationship Mapping: Easily manage relationships between entities, just like you would with more feature-rich ORMs.

Who Should Use Vitorm?

Vitorm is ideal for developers who want the performance and simplicity of Dapper but need the robust features and flexibility of Entity Framework. Whether you’re building a small project or a large-scale application, Vitorm provides a powerful yet streamlined solution that can adapt to your needs.

Join the conversation and start exploring what Vitorm can do for your next project. Happy coding!

Comparison of performance with other ORMs

Through benchmarks, there may be slight variations depending on the database source, for reference only.
code address: Vitorm.Data.Benchmark

SqlServer

MySql

Sqlite

Examples

Let's walk through the steps to set up and use Vitorm with SQLite.

Installation

Before using Vitorm, install the necessary package:

dotnet add package Vitorm.Sqlite

Minimum viable demo

code address: Program_Min.cs

using Vitorm;
namespace App
{
    public class Program_Min
    {
        static void Main2(string[] args)
        {
            // #1 Init
            using var dbContext = new Vitorm.Sql.SqlDbContext();
            dbContext.UseSqlite("data source=sqlite.db");

            // #2 Query
            var user = dbContext.Get<User>(1);
            var users = dbContext.Query<User>().Where(u => u.name.Contains("li")).ToList();
        }

        // Entity Definition
        [System.ComponentModel.DataAnnotations.Schema.Table("User")]
        public class User
        {
            [System.ComponentModel.DataAnnotations.Key]
            public int id { get; set; }
            public string name { get; set; }
            public DateTime? birth { get; set; }
            public int? fatherId { get; set; }
        }
    }
}

For full example please check here: Program.cs

Vitorm.Data Documentation

Vitorm.Data is a static class that allows you to use Vitorm without explicitly creating or disposing of a DbContext.

Installation

Before using Vitorm.Data, install the necessary package:

dotnet add package Vitorm.Data
dotnet add package Vitorm.Sqlite

Config settings

// appsettings.json
{
  "Vitorm": {
    "Data": [
      {
        "provider": "Sqlite",
        "namespace": "App",
        "connectionString": "data source=sqlite.db;"
      }
    ]
  }
}

Minimum viable demo

After configuring the appsettings.json file, you can directly perform queries without any additional configuration or initialization, Vitorm.Data is that easy to use.

code address: Program_Min.cs

using Vitorm;
namespace App
{
    public class Program_Min
    {
        static void Main2(string[] args)
        {
            //  Query Records
            var user = Data.Get<User>(1);
            var users = Data.Query<User>().Where(u => u.name.Contains("li")).ToList();
        }

        // Entity Definition
        [System.ComponentModel.DataAnnotations.Schema.Table("User")]
        public class User
        {
            [System.ComponentModel.DataAnnotations.Key]
            public int id { get; set; }
            public string name { get; set; }
            public DateTime? birth { get; set; }
            public int? fatherId { get; set; }
        }
    }
}

For full example please check here: Program.cs