📚 Documentation: IrbyImaging.DomainClasses.csproj
Path: IrbyImaging.DomainClasses/IrbyImaging.DomainClasses.csproj
Type: .NET SDK-style project file
Target Framework: .NET 9.0
📋 Table of Contents
- 🔍 Overview & Purpose
- ⚙️ Project Configuration
- 📦 Dependencies & Technologies
- 🔗 Project References
- 🛠️ Build & Packaging
- 📈 UML Diagram
- 🚀 Usage Examples
- 📌 Conclusion
🔍 Overview & Purpose
The IrbyImaging.DomainClasses project is a class library that encapsulates the core domain entities, value objects, DTOs, enums and interfaces of the IrbyImaging solution. It establishes the “ubiquitous language” for imaging workflows—defining how data is represented, validated, and transferred throughout the system.
- Centralizes all business‐centric models and domain logic
- Keeps domain code decoupled from presentation, infrastructure, and UI layers
- Facilitates unit testing and maintenance by isolating domain definitions
⚙️ Project Configuration
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<!-- Targeting the latest .NET 9.0 platform -->
<TargetFramework>net9.0</TargetFramework>
</PropertyGroup>
<!-- NuGet & Project References defined below -->
<ItemGroup>…</ItemGroup>
<ItemGroup>…</ItemGroup>
</Project>
- Sdk:
Microsoft.NET.Sdk – the default SDK for .NET class libraries
- TargetFramework:
net9.0 – leverages the performance, C# features, and APIs of .NET 9
📦 Dependencies & Technologies
IrbyImaging.DomainClasses depends on a rich ecosystem of NuGet packages. Below is a categorized breakdown:
3.1 Azure & Cloud SDKs ☁️
| Package |
Version |
Purpose |
| Azure.Extensions.AspNetCore.Configuration.Secrets |
1.3.2 |
Bind Azure Key Vault secrets to ASP.NET Configuration |
| Azure.Security.KeyVault.Secrets |
4.7.0 |
Client for Azure Key Vault secret operations |
| Azure.Storage.Blobs |
12.23.0 |
Blob storage operations (upload, download, list) |
| Microsoft.Extensions.Azure |
1.9.0 |
Simplified Azure client registration in DI container |
3.2 Reporting & Licensing 📊
| Package |
Version |
Purpose |
| Bold.Licensing |
6.3.18 |
Licensing engine for BoldReports |
| BoldReports.AspNet.Core |
6.3.18 |
Reporting UI components for ASP.NET Core |
| BoldReports.Net.Core |
6.3.18 |
BoldReports processing engine |
3.3 Document, PDF & OCR 📑
| Package |
Version |
Purpose |
| ClosedXML |
0.104.2 |
Fluent Excel file creation & manipulation |
| CsvHelper |
33.0.1 |
CSV reading & writing with mapping support |
| IronOcr |
2024.12.2 |
OCR engine for extracting text from images |
| IronPdf |
2024.12.9 |
PDF generation & modification |
| IronWebScraper |
2024.12.1 |
Web scraping framework |
| IronXL.Excel |
2025.2.5 |
High‑performance Excel manipulation |
| iTextSharp |
5.5.13.4 |
Classic .NET PDF library |
3.4 Data Access & ORM 💾
| Package |
Version |
Purpose |
| Microsoft.EntityFrameworkCore |
9.0.0 |
Core ORM for relational databases |
| Microsoft.EntityFrameworkCore.SqlServer |
9.0.0 |
SQL Server provider for EF Core |
| Microsoft.EntityFrameworkCore.InMemory |
9.0.0 |
In‑memory database for unit testing |
| Microsoft.EntityFrameworkCore.Tools |
9.0.0 |
CLI & design‑time tools for EF migrations |
| Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider |
5.1.0 |
Always Encrypted support with Azure Key Vault |
3.5 Authentication & Security 🔒
| Package |
Version |
Purpose |
| Microsoft.AspNetCore.Authentication.OpenIdConnect |
9.0.0 |
OpenID Connect authentication middleware |
| Microsoft.Identity.Web |
3.5.0 |
Azure AD & Microsoft Identity integration |
| Microsoft.Identity.Web.UI |
3.5.0 |
Blazor/UI helpers for Identity Web |
| Microsoft.AspNetCore.Identity.EntityFrameworkCore |
9.0.0 |
Identity stores backed by EF Core |
| Microsoft.AspNetCore.Identity.UI |
9.0.0 |
Razor pages for Identity flows |
3.6 Scheduling, Scraping & Automation 🤖
| Package |
Version |
Purpose |
| Quartz |
3.13.1 |
Job scheduling & background tasks |
| Selenium.WebDriver |
4.27.0 |
Browser automation |
| Selenium.Support |
4.27.0 |
Selenium abstractions & helpers |
| Selenium.WebDriver.ChromeDriver |
131.0.6778.20400 |
ChromeDriver binaries for Selenium |
3.7 UI Components & Syncfusion 🖥️
| Package |
Version |
Purpose |
| Syncfusion.EJ2.AspNet.Core |
28.1.33 |
Essential JS 2 components for ASP.NET Core Web |
| Syncfusion.EJ2.Spreadsheet.AspNet.Core |
28.1.33 |
Spreadsheet UI widget |
| Syncfusion.EJ2.WordEditor.AspNet.Core |
28.1.33 |
Rich text & word editor UI |
| Syncfusion.EJ2.PdfViewer.AspNet.Core.Windows |
28.1.33 |
PDF viewer control for ASP.NET Core |
| Syncfusion.XlsIO.Net.Core |
28.1.33 |
Excel file I/O library |
| Syncfusion.Pdf.Net.Core |
28.1.33 |
PDF creation & manipulation |
| Syncfusion.DocIO.Net.Core |
28.1.33 |
Word document I/O |
| Syncfusion.Presentation.Net.Core |
28.1.33 |
PowerPoint file manipulation |
| Syncfusion.Licensing |
28.1.33 |
Licensing for Syncfusion components |
| Syncfusion.Compression.Net.Core |
28.1.33 |
ZIP compression/decompression |
| Syncfusion.PMML.Net.Core |
20.4.0.44 |
Predictive model markup language support |
3.8 Code Analysis & Testing 🧪
| Package |
Version |
Purpose |
| Microsoft.CodeAnalysis.* |
4.12.0+ |
Roslyn analyzers, workspaces & scripting |
| Microsoft.CodeAnalysis.Razor |
6.0.36 |
Razor syntax analysis |
| Microsoft.CodeAnalysis.Elfie |
1.0.0 |
Roslyn data extraction utilities |
| Microsoft.CodeAnalysis.Analyzers |
3.11.0 |
Static code analysis rules |
| coverlet.collector |
6.0.2 |
Code coverage collector for .NET tests |
| Microsoft.NET.Test.Sdk |
17.12.0 |
Test SDK for MSTest, xUnit, NUnit |
| xunit.runner.visualstudio |
2.8.2 |
xUnit test runner integration for Visual Studio |
3.9 Miscellaneous & System 🔧
| Package |
Version |
Purpose |
| Microsoft.VisualStudio.Web.CodeGeneration.Design |
9.0.0 |
Scaffolding tools for ASP.NET Core |
| MimeKit |
4.9.0 |
MIME creation & parsing |
| NETCore.MailKit |
2.1.0 |
SMTP/IMAP mail client |
| Microsoft.Office.Interop.Outlook |
15.0.4797.1004 |
Outlook COM interop |
| Microsoft.SqlServer.* |
1.x / 172.x |
SMO & management objects for SQL Server |
| System.Data.SqlClient |
4.9.0 |
Legacy ADO.NET SQL client |
| System.DirectoryServices & .AccountManagement |
9.0.0 |
Active Directory integration |
| System.Net.Http |
4.3.4 |
HTTP client support |
| System.Text.RegularExpressions |
4.3.1 |
Regex engine |
🔗 Project References
<ItemGroup>
<ProjectReference Include="..\IrbyImaging.Utility\IrbyImaging.BLUtility.csproj" />
</ItemGroup>
- IrbyImaging.BLUtility
- Houses cross‑cutting helpers, extension methods, logging, configuration logic, and validation utilities used by DomainClasses and other projects.
🛠️ Build & Packaging
📈 UML Diagram
Below is a high‑level PlantUML showing the relationship between DomainClasses and its Utility dependency:
@startuml
package IrbyImaging {
[BLUtility] #LightBlue
[DomainClasses] #LightGreen
BLUtility <-- DomainClasses : uses
}
@enduml
🚀 Usage Examples
1. Reference in Another Project
<ItemGroup>
<ProjectReference Include="..\IrbyImaging.DomainClasses\IrbyImaging.DomainClasses.csproj" />
</ItemGroup>
2. Consuming a Domain Entity (Hypothetical)
using IrbyImaging.DomainClasses.Models;
namespace IrbyImaging.WebAPI.Controllers
{
public class ImagingStudiesController : ControllerBase
{
// Example: instantiate a domain entity
var study = new ImagingStudy
{
Id = Guid.NewGuid(),
PatientId = Guid.Parse("..."),
Modality = Modality.MRI,
DatePerformed = DateTime.UtcNow
};
// Business rules & validations live inside domain model
var isValid = study.IsValid();
...
}
}
Note: Actual model names and methods depend on the classes defined within DomainClasses.
📌 Conclusion
The IrbyImaging.DomainClasses project defines the core business entities and domain logic for the IrbyImaging solution. Its lightweight, SDK‑style configuration targets modern .NET 9.0 and brings in a diverse set of dependencies to support:
- Secure cloud configuration & storage
- Rich reporting, Excel, PDF, and OCR capabilities
- Robust ORM support with Entity Framework Core
- Comprehensive authentication, identity, and scheduling
- UI & document component libraries via Syncfusion
- End‑to‑end testing, code analysis, and CI/CD readiness
By isolating domain classes in a dedicated assembly, your application gains maintainability, testability, and a clear separation of concerns—empowering teams to evolve the imaging domain model independently of UI, persistence, or infrastructure layers. Enjoy building! 🚀