PowNet 2025.10.12.22

PowNet

Modern, modular utilities & extension framework for .NET 10 � performance-aware, test-backed, extensible.

<div align="center">

</div>

Quick Navigation

• Overview
• Key Features
• Why PowNet?
• Installation
• Getting Started
• Data Layer (DbIO)
• Performance & Diagnostics
• Architecture
• Examples
• Documentation Index
• Roadmap
• Contributing
• License

Overview

PowNet is a lightweight yet comprehensive extension & utility toolkit for building high-quality .NET backends, tools, services and test harnesses. It focuses on:

• Developer ergonomics
• Observability (diagnostics, profiling hooks, performance measurement)
• Configuration clarity
• Safe, explicit patterns (logging, retries, structured exceptions)

All modules are covered by unit tests (currently 395 passing tests).

Key Features

Why PowNet?

• Avoid boilerplate: Unified wrappers for data, events, diagnostics.
• Observability built-in: hooks for logging & metrics (no hard dependency on a single logging framework).
• Production-ready defaults with development affordances.
• Explicit, documented patterns (architecture + usage docs per feature).
• Framework-agnostic: use in console apps, services, tests, microservices.

Installation

Currently consumed via project reference (monorepo style):

git clone https://github.com/mirshahreza/PowNet.git
cd PowNet
# build
 dotnet build
# run tests
 dotnet test

(Optional) Create a NuGet package:

dotnet pack PowNet/PowNet.csproj -c Release

Add reference in your solution:

dotnet add <YourProject>.csproj reference PowNet/PowNet.csproj

Getting Started

using PowNet.Extensions;

// Collection helper
var items = new[] {1,2,3,4};
var batched = items.Batch(2); // [[1,2],[3,4]]

// Event bus quick usage
public record UserCreated(int Id);
EventBusExtensions.Subscribe<UserCreated>((e, ct) => { Console.WriteLine($"User {e.Id}"); return Task.CompletedTask; });
await new UserCreated(10).PublishAsync();

// Configuration access
int timeout = PowNetConfiguration.GetConfigValue("PowNet:Database:CommandTimeout", 30);

Data Layer (Db IO)

DbIO abstracts ADO.NET interaction:

• Execution wrappers (sync & async) with timing + exception enrichment
• Transaction helpers (BeginTransaction, CommitTransaction, RollbackTransaction)
• Extensible provider model (add PostgreSQL/MySQL by subclassing DbIO)
• Hooks: OnBeforeExecute, OnAfterExecute

Example:

using var db = DbIO.Instance("DefaultConnection");
var userCount = (int)(db.ExecuteScalar("SELECT COUNT(1) FROM Users") ?? 0);

More: DbIO Overview � Design � Usage

Performance & Diagnostics

The DevelopmentExtensions module provides:

• Method performance sampling (AnalyzeMethodPerformance)
• Allocation analysis (AnalyzeMemoryAllocations)
• Code quality and smell detection (AnalyzeCodeQuality)
• Benchmark + comparison utilities (CompareMethodImplementations, CompareBenchmarks)

Example:

Func<int> add = () => 1+1;
var perf = add.AnalyzeMethodPerformance(iterations: 100);
if (!perf.IsAnalysisSkipped) Console.WriteLine(perf.AverageExecutionTime);

Architecture

PowNet
 |- Configuration (PowNetConfiguration, EnvironmentManager)
 |- Extensions
 |  |- Collections & Concurrency
 |  |- Diagnostics & Development
 |  |- EventBus (retry, pipeline, debounce)
 |  |- Security & Encryption
 |  |- Data (DbIO + provider)
 |  |- JSON / Text / Date / Object
 |- Data (Providers, Abstract Facade)
 |- Logging (PowNetLogger integration points)
 |- Tests (395 validated scenarios)

Design documents: see Documentation/INDEX.

Examples

Documentation

Central docs live in the Documentation/ folder (each feature isolated). Start here:

• Full Index
• Popular entries:
  • PowNetConfiguration
  • EventBusExtensions
  • PerformanceExtensions
  • DbIO
  • SecurityExtensions

Roadmap

Feel free to open issues for proposals.

Contributing

1. Fork & branch (feat/<name> or fix/<issue>).
2. Add/adjust tests (no feature merged without coverage).
3. Follow existing naming & folder patterns.
4. Run: dotnet format (if configured) & dotnet test.
5. Submit PR with concise description + motivation.

Development Guidelines

• Keep extension methods focused & side-effect free.
• Prefer explicit configuration keys (PowNet:Section:Key).
• Avoid static mutable state unless guarded (see EventBus reset).
• Add design notes for complex subsystems (Documentation/*.md).

License

MIT � see LICENSE.

Generated & curated; contributions to improve clarity or performance patterns are welcome.