Merged PR 11270: Devkit renames

renames

Author: vip32

.gitignore

@@ -37,13 +37,6 @@ bld/
 
 # Visual Studio 2015/2017 cache/options directory
 .vs/
-!.vs
-.vs/*
-!.vs/BridgingIT.DevKit
-.vs/BridgingIT.DevKit/*
-!.vs/BridgingIT.DevKit/color.txt
-# Uncomment if you have tasks that create the project's static files in wwwroot
-#wwwroot/
 
 # Visual Studio 2017 auto generated files
 Generated\ Files/

.vs/BridgingIT.DevKit/color.txt

@@ -20,5 +20,5 @@
     "commandCenter.border": "#e7e7e799"
 },
   "peacock.color": "#14389d",
-  "dotnet.defaultSolution": "BridgingIT.DevKit.sln"
+  "dotnet.defaultSolution": "bITdevKit.slnx"
 }

.vscode/settings.json

@@ -7,7 +7,7 @@
       "type": "process",
       "args": [
         "build",
-        "${workspaceFolder}/BridgingIT.DevKit.sln",
+        "${workspaceFolder}/bITdevKit.slnx",
         "--nologo",
         "/property:GenerateFullPaths=true",
         "/consoleloggerparameters:NoSummary"

.vscode/tasks.json

@@ -5,27 +5,33 @@
         <!--package-->
         <Authors>BridgingIT GmbH</Authors>
         <Description>
-            BridgingIT DevKit: Empowering developers with modular components for modern application development, centered around Domain-Driven Design principles. Our goal is to empower developers by offering modular components that can be easily integrated into your projects. Whether you're working with repositories, commands, queries, or other components, the bITDevKit provides flexible solutions that can adapt to your specific needs.
+            bITdevKit: Empowering developers with modular components for modern application development, centered around Domain-Driven Design principles. Our goal is to empower developers by offering modular components that can be easily integrated into your projects. Whether you're working with repositories, commands, queries, or other components, the bITDevKit provides flexible solutions that can adapt to your specific needs.
         </Description>
-        <Copyright>Copyright 2024 (c) BridgingIT GmbH. All rights reserved.</Copyright>
-        <PublishRepositoryUrl>true</PublishRepositoryUrl>
+        <Copyright>Copyright 2025 (c) BridgingIT GmbH. All rights reserved.</Copyright>
+        <PackageTags>bridgingit;devkit;bitdevkit;dotnet;clean-architecture;solution;cqrs;ddd</PackageTags>
+        <RepositoryUrl>https://github.com/BridgingIT-GmbH/bITdevKit</RepositoryUrl>
+        <PackageProjectUrl>https://github.com/BridgingIT-GmbH/bITdevKit</PackageProjectUrl>
+        <RepositoryType>git</RepositoryType>
+        <PackageLicenseExpression>MIT</PackageLicenseExpression>
+        <PackageRequireLicenseAcceptance>false</PackageRequireLicenseAcceptance>
+
         <AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>
         <SourceRevisionId>build$([System.DateTime]::UtcNow.ToString("yyyyMMddHHmmss"))</SourceRevisionId>
         <DebugType>embedded</DebugType>
         <EmbedAllSources>true</EmbedAllSources>
         <AccelerateBuildsInVisualStudio>true</AccelerateBuildsInVisualStudio>
         <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
-        <!--https://learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/caching-nuget?view=azure-devops#lock-dependencies-->
+    <!--https://learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/caching-nuget?view=azure-devops#lock-dependencies-->
         <DisableImplicitNuGetFallbackFolder>true</DisableImplicitNuGetFallbackFolder>
         <MinVerDefaultPreReleaseIdentifiers>preview.0</MinVerDefaultPreReleaseIdentifiers>
         <NoWarn>NU1903</NoWarn>
     </PropertyGroup>
 
-    <!--<PropertyGroup Condition="$(MSBuildProjectDirectory.Contains('src'))">
+  <!--<PropertyGroup Condition="$(MSBuildProjectDirectory.Contains('src'))">
     <PackageReleaseNotes>$([System.IO.File]::ReadAllText("$(MSBuildProjectDirectory)/../../RELEASES.md"))</PackageReleaseNotes>
   </PropertyGroup>-->
 
-    <!--<ItemGroup>
+  <!--<ItemGroup>
     <None Include="../../README.md" Pack="true" PackagePath="\"/>
   </ItemGroup>-->
 
@@ -37,9 +43,9 @@
         <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
         <WarningsAsErrors>true</WarningsAsErrors>
 
-        <!--    <CodeAnalysisRuleSet></CodeAnalysisRuleSet>-->
-        <!--<UseSharedCompilation>true</UseSharedCompilation>-->
-        <!--roslyn build speed-->
+    <!--    <CodeAnalysisRuleSet></CodeAnalysisRuleSet>-->
+    <!--<UseSharedCompilation>true</UseSharedCompilation>-->
+    <!--roslyn build speed-->
     </PropertyGroup>
 
     <ItemGroup>
@@ -53,7 +59,7 @@
         <None Remove="**\*.lock.json" Visible="false"/>
     </ItemGroup>
 
-    <!--<ItemGroup>
+  <!--<ItemGroup>
     <Compile Include="..\..\GlobalSuppressions.cs" Link="GlobalSuppressions.cs" />
   </ItemGroup>-->
 
@@ -68,7 +74,7 @@
     </ItemGroup>
 
     <Target Name="CheckPackageVersion" BeforeTargets="Build"> <!-- prevent some unwanted package upgrades due to licensing -->
-        <Error Condition="'%(PackageVersion.Identity)' == 'AutoMapper' AND '%(PackageVersion.Version)' != '[14.0.0]'" Text="Invalid package version for AutoMapper. Expected: 14.0.0." />
+        <!-- <Error Condition="'%(PackageVersion.Identity)' == 'AutoMapper' AND '%(PackageVersion.Version)' != '[14.0.0]'" Text="Invalid package version for AutoMapper. Expected: 14.0.0." /> -->
         <Error Condition="'%(PackageVersion.Identity)' == 'MediatR' AND '%(PackageVersion.Version)' != '[12.5.0]'" Text="Invalid package version for MediatR. Expected: 12.5.0." />
     </Target>
 

Directory.Build.props

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 BridgingIT GmbH
+Copyright (c) 2025 BridgingIT GmbH
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

LICENSE

@@ -1,4 +1,4 @@
-## Release 3.0.1 [25.04.24]
+## Release 9.0.0 [25.04.24]
 
 - [N] Initial release
 

RELEASES.md

@@ -5,15 +5,7 @@
     }
   ],
   "settings": {
-    "dotnet.defaultSolution": "BridgingIT.DevKit.sln",
-    "github.copilot.chat.codeGeneration.instructions": [
-      {
-        "file": ".github/.copilot-instructions.md"
-      },
-      {
-        "file": "CODE-STYLE.md"
-      }
-    ],
+    "dotnet.defaultSolution": "bITdevKit.slnx",
     "workbench.colorCustomizations": {
         "activityBar.activeBackground": "#1a48ca",
         "activityBar.activeBorder": "#e9567c",
@@ -34,6 +26,14 @@
         "titleBar.inactiveForeground": "#e7e7e799",
         "commandCenter.border": "#e7e7e799"
     },
-    "peacock.color": "#14389d"
+    "peacock.color": "#14389d",
+    "github.copilot.chat.codeGeneration.instructions": [
+      {
+        "file": ".github/.copilot-instructions.md"
+      },
+      {
+        "file": "CODE-STYLE.md"
+      }
+    ],
   }
 }

BridgingIT.DevKit.code-workspace bITdevKit.code-workspaceBridgingIT.DevKit.code-workspace renamed to bITdevKit.code-workspace

@@ -4,7 +4,7 @@
 
 ## Overview
 
-The ActiveEntity feature in the bITDevKit reimagines the classic [Active Record pattern](https://en.wikipedia.org/wiki/Active_record_pattern), for .NET developers. This modern take embeds CRUD operations and queries directly into entity classes, providing a streamlined data access solution. Unlike its traditional form, it is persistence-neutral, relying on pluggable providers that can integrate with Entity Framework Core (EF Core), in-memory stores or custom data sources, configurable per entity. Entities inherit from `ActiveEntity<TEntity, TId>`, extending the `Entity<TId>` base class for ID handling, equality and transient checks, while employing the `Result` pattern for consistent operation outcomes (success/failure with messages and errors). Tailored for developers building CRUD-heavy or domain-rich applications, it complements complex query needs with repository patterns when necessary, aligning with the DevKit's commitment to modular, effective solutions.
+The ActiveEntity feature in the bITDevKit reimagines the classic [Active Record pattern](https://en.wikipedia.org/wiki/Active_record_pattern), for .NET developers. This modern take embeds CRUD operations and queries directly into entity classes, providing a streamlined data access solution. Unlike its traditional form, it is persistence-neutral, relying on pluggable providers that can integrate with Entity Framework Core (EF Core), in-memory stores or custom data sources, configurable per entity. Entities inherit from `ActiveEntity<TEntity, TId>`, extending the `Entity<TId>` base class for ID handling, equality and transient checks, while employing the `Result` pattern for consistent operation outcomes (success/failure with messages and errors). Tailored for developers building CRUD-heavy or domain-rich applications, it complements complex query needs with repository patterns when necessary, aligning with the bITdevKit commitment to modular, effective solutions.
 
 ## Challenges
 
@@ -32,7 +32,7 @@ The [Active Record pattern is described by Martin Fowler](https://www.martinfowl
 
 ### Components
 
-The feature centers on `ActiveEntity<TEntity, TId>`, which embeds persistence logic and delegates to an `IActiveEntityEntityProvider<TEntity, TId>` for data access. Behaviors, implementing `IActiveEntityEntityBehavior<T>`, intercept operations to manage concerns like logging or auditing, executed in registration order. The global service provider, configured via `ActiveEntityConfigurator`, resolves these components at runtime, ensuring flexibility and testability.  
+The feature centers on `ActiveEntity<TEntity, TId>`, which embeds persistence logic and delegates to an `IActiveEntityEntityProvider<TEntity, TId>` for data access. Behaviors, implementing `IActiveEntityEntityBehavior<T>`, intercept operations to manage concerns like logging or auditing, executed in registration order. The global service provider, configured via `ActiveEntityConfigurator`, resolves these components at runtime, ensuring flexibility and testability.
 The **`ActiveEntityContext<TEntity, TId>`** is a lightweight object that bundles the `IActiveEntityEntityProvider` and its associated `IActiveEntityEntityBehavior` instances, ensuring that all components within a given operation share the same underlying DI scope and transactional context, simplifying complex scenarios.
 
 ```mermaid
@@ -114,7 +114,7 @@ classDiagram
         +AfterFindOneAsync(id, options, entity, success, ct) Task~Result~
         // ... other Before/After hooks for FindAll, Count, Exists, Project
     }
-    
+
     class ActiveEntityContext~TEntity, TId~ {
         +IActiveEntityEntityProvider~TEntity, TId~ Provider
         +IReadOnlyCollection~IActiveEntityEntityBehavior~T~~ Behaviors
@@ -241,7 +241,7 @@ var customer = new Customer
     LastName = "Doe",
     Title = "Mr."
 };
-var insertResult = await customer.InsertAsync(); 
+var insertResult = await customer.InsertAsync();
 
 if (insertResult.IsSuccess)
 {
@@ -257,7 +257,7 @@ var results = await Customer.InsertAsync(
 [
     new() { FirstName = "John", LastName = "Doe", Email = EmailAddressStub.Create("john.doe@example.com"), Title = "Mr." },
     new() { FirstName = "Jane", LastName = "Doe", Email = EmailAddressStub.Create("jane.doe@example.com"), Title = "Ms." }
-]); 
+]);
 
 foreach (var result in results)
 {
@@ -273,7 +273,7 @@ First, load the entity, modify it and then call `UpdateAsync`.
 ```csharp
 var customer = (await Customer.FindOneAsync(customerId)).Value;
 customer.FirstName = "Janet";
-var updateResult = await customer.UpdateAsync(); 
+var updateResult = await customer.UpdateAsync();
 
 if (updateResult.IsSuccess)
 {
@@ -292,7 +292,7 @@ var customer2 = (await Customer.FindOneAsync(customerId2)).Value;
 customer1.FirstName = "Janet";
 customer2.FirstName = "Johnu";
 
-await Customer.UpdateAsync([customer1, customer2]); 
+await Customer.UpdateAsync([customer1, customer2]);
 ```
 
 ### Update existing entity properties directly
@@ -301,7 +301,7 @@ For an entity instance only specific properties are updated using a fluent synta
 
 ```csharp
 var customer = (await Customer.FindOneAsync(customerId)).Value;
-var updateResult = await customer.UpdateAsync(u => u 
+var updateResult = await customer.UpdateAsync(u => u
     .Set(c => c.FirstName, "Janet")              // constant assignment
     .Set(c => c.Visits, c => c.Visits + 1)       // computed assignment
     .Set(c => c.Title, _ => "Archived"));        // dynamic constant
@@ -337,7 +337,7 @@ First, load the entity and then call `DeleteAsync`.
 
 ```csharp
 var customer = (await Customer.FindOneAsync(customerId)).Value;
-var deleteResult = await customer.DeleteAsync(); 
+var deleteResult = await customer.DeleteAsync();
 
 if (deleteResult.IsSuccess)
 {
@@ -353,7 +353,7 @@ First, load the entities and then call `DeleteAsync` with a collection.
 var customer1 = (await Customer.FindOneAsync(customerId1)).Value;
 var customer2 = (await Customer.FindOneAsync(customerId2)).Value;
 
-await Customer.DeleteAsync([customer1, customer2]); 
+await Customer.DeleteAsync([customer1, customer2]);
 ```
 
 ### Delete multiple existing entities by ID
@@ -387,7 +387,7 @@ if (deleteResult.IsSuccess)
 Find an entity by its ID.
 
 ```csharp
-var findResult = await Customer.FindOneAsync(customerId); 
+var findResult = await Customer.FindOneAsync(customerId);
 if (findResult.IsSuccess)
 {
     var customer = findResult.Value;
@@ -398,7 +398,7 @@ if (findResult.IsSuccess)
 ### Find multiple entities (unfiltered)
 
 ```csharp
-var findAllResult = await Customer.FindAllAsync(); 
+var findAllResult = await Customer.FindAllAsync();
 if (findAllResult.IsSuccess)
 {
     var customers = findAllResult.Value;
@@ -412,7 +412,7 @@ if (findAllResult.IsSuccess)
 ### Find multiple entities (filtered)
 
 ```csharp
-var findAllResult = await Customer.FindAllAsync(e => e.LastName == "Doe"); 
+var findAllResult = await Customer.FindAllAsync(e => e.LastName == "Doe");
 if (findAllResult.IsSuccess)
 {
     var customers = findAllResult.Value;
@@ -427,7 +427,7 @@ if (findAllResult.IsSuccess)
 
 ```csharp
 var options = new FindOptions<Customer> { Skip = 0, Take = 10 };
-var pagedResult = await Customer.FindAllPagedAsync(options); 
+var pagedResult = await Customer.FindAllPagedAsync(options);
 if (pagedResult.IsSuccess)
 {
     var customers = pagedResult.Value.Items;
@@ -464,7 +464,7 @@ public static class CustomerService
             {
                 // Example: custom logging behavior specific to this service's logic
                 // You might need to adjust the behavior interface to accept additional arguments
-                // await behavior.LogSomethingAsync(updatedCustomer, ct); 
+                // await behavior.LogSomethingAsync(updatedCustomer, ct);
             }
 
             return Result.Success();
@@ -493,13 +493,13 @@ var customer = new Customer
 var transactionResult = await Customer.WithTransactionAsync(async ctx => // ctx contains provider and behaviors
 {
     // All CRUD operations within this block must use the provided 'ctx'
-    var insertResult = await customer.InsertAsync(ctx); 
+    var insertResult = await customer.InsertAsync(ctx);
     if (insertResult.IsFailure) return Result.Failure(insertResult.Errors); // propagate failure, will trigger rollback
 
     // Perform another operation in the same transaction
     var updatedCustomer = (await ctx.Provider.FindOneAsync(customer.Id)).Value;
     if (updatedCustomer == null) return Result.Failure("Customer not found in transaction.");
-    
+
     updatedCustomer.Title = "Sir";
     var updateResult = await updatedCustomer.UpdateAsync(ctx); // use ctx to ensure it's part of the same transaction
     if (updateResult.IsFailure) return Result.Failure(updateResult.Errors); // propagate failure, will trigger rollback
@@ -900,7 +900,7 @@ public static class CustomerQueryExtensions
     {
         var thirtyDaysAgo = DateTimeOffset.UtcNow.AddDays(-30);
         var spec = new Specification<Customer>(c => c.Orders.Any(o => o.DateSubmitted >= thirtyDaysAgo));
-        return Customer.FindAllAsync(spec, null, ct); 
+        return Customer.FindAllAsync(spec, null, ct);
     }
 }
 ```
@@ -951,13 +951,13 @@ While powerful, callbacks should be used sparingly for logic that is truly intri
 
 ## Appendix A: Disclaimer
 
-The ActiveEntity feature provides a modern, entity-embedded approach to data access, ideal for CRUD-heavy applications within the bITDevKit ecosystem. It is not a replacement for comprehensive ORM frameworks or repository patterns in scenarios requiring complex queries, high-performance batch operations or multi-database support. Entity configurations are standard EF Core configurations, defined in `OnModelCreating` using the fluent API, ensuring compatibility with existing EF Core workflows. For advanced use cases, consider integrating with repositories or using EF Core directly. This feature prioritizes simplicity and alignment with DevKit principles, allowing developers to choose the simplest tool that meets their needs.
+The ActiveEntity feature provides a modern, entity-embedded approach to data access, ideal for CRUD-heavy applications within the bITDevKit ecosystem. It is not a replacement for comprehensive ORM frameworks or repository patterns in scenarios requiring complex queries, high-performance batch operations or multi-database support. Entity configurations are standard EF Core configurations, defined in `OnModelCreating` using the fluent API, ensuring compatibility with existing EF Core workflows. For advanced use cases, consider integrating with repositories or using EF Core directly. This feature prioritizes simplicity and alignment with bITdevKit principles, allowing developers to choose the simplest tool that meets their needs.
 
 ## Appendix B: Comparison with Repository Pattern
 
 ### Overview
 
-The Active Record (AR) pattern embeds data access and domain logic directly into entities, making them responsible for their own persistence. The Repository pattern, a common alternative in the bITDevKit, abstracts persistence behind a repository interface, treating entities as plain data objects and separating data access from domain logic. Both patterns are supported within the DevKit, with AR offering a modern twist through per-entity providers and behaviors, while Repository provides a traditional abstraction layer.
+The Active Record (AR) pattern embeds data access and domain logic directly into entities, making them responsible for their own persistence. The Repository pattern, a common alternative in the bITDevKit, abstracts persistence behind a repository interface, treating entities as plain data objects and separating data access from domain logic. Both patterns are supported within the bITdevKit, with AR offering a modern twist through per-entity providers and behaviors, while Repository provides a traditional abstraction layer.
 
 ### Characteristics of Each Pattern