refactor: Rename EmailPorifler to MessagingService

This commit is contained in:
2026-07-24 13:59:43 +02:00
parent 77d3b52d16
commit 5e587da957
58 changed files with 202 additions and 202 deletions

View File

@@ -1,4 +1,4 @@
# EmailProfiler - Implementation Status Report
# MessagingService - Implementation Status Report
**Last Updated**: 2026-07-20
**Overall Progress**: 75% Complete (3 of 4 phases done)
@@ -7,7 +7,7 @@
## Executive Summary
The EmailProfiler migration from legacy VB.NET to modern C# .NET 8.0 Clean Architecture is **75% complete**. All core layers (Domain, Application, Infrastructure) are fully implemented with real service stubs ready for integration. Only API layer controllers and workers remain.
The MessagingService migration from legacy VB.NET to modern C# .NET 8.0 Clean Architecture is **75% complete**. All core layers (Domain, Application, Infrastructure) are fully implemented with real service stubs ready for integration. Only API layer controllers and workers remain.
### ✅ What's Working
- Complete Domain model with 8 entities mapped to legacy database
@@ -68,7 +68,7 @@ The EmailProfiler migration from legacy VB.NET to modern C# .NET 8.0 Clean Archi
**Files**:
```
src/DigitalData.EmailProfiler.Domain/
src/DigitalData.MessagingService.Domain/
├── Entities/ (8 files)
├── ValueObjects/ (3 files)
├── Enums/ (5 files)
@@ -135,7 +135,7 @@ src/DigitalData.EmailProfiler.Domain/
**Files**:
```
src/DigitalData.EmailProfiler.Application/
src/DigitalData.MessagingService.Application/
├── EmailProfiles/Commands/ (3 files)
├── EmailProfiles/Queries/ (2 files)
├── EmailProfiles/Validators/ (2 files)
@@ -158,7 +158,7 @@ src/DigitalData.EmailProfiler.Application/
### Phase 3: Infrastructure Layer ✅ COMPLETE (100%)
**Database**:
-`EmailProfilerDbContext` - EF Core DbContext with 8 DbSets
-`MessagingServiceDbContext` - EF Core DbContext with 8 DbSets
- NO `OnModelCreating` override (attribute-only configuration)
- NO `SaveChangesAsync` override (Repository handles this)
- Connection string: `DefaultConnection` from appsettings
@@ -231,8 +231,8 @@ src/DigitalData.EmailProfiler.Application/
**Files**:
```
src/DigitalData.EmailProfiler.Infrastructure/
├── Persistence/EmailProfilerDbContext.cs
src/DigitalData.MessagingService.Infrastructure/
├── Persistence/MessagingServiceDbContext.cs
├── Repositories/Repository.cs
├── Services/ (6 files)
├── Messaging/ (3 files)
@@ -290,7 +290,7 @@ src/DigitalData.EmailProfiler.Infrastructure/
**Files**:
```
src/DigitalData.EmailProfiler.API/
src/DigitalData.MessagingService.API/
├── Controllers/ (3 files)
├── appsettings.json
├── appsettings.Secrets.json
@@ -311,7 +311,7 @@ src/DigitalData.EmailProfiler.API/
**Test Structure**:
```
tests/DigitalData.EmailProfiler.Tests/
tests/DigitalData.MessagingService.Tests/
├── Domain/
│ ├── Services/MessageIdGeneratorTests.cs
│ ├── ValueObjects/EmailAddressTests.cs
@@ -362,7 +362,7 @@ tests/DigitalData.EmailProfiler.Tests/
### 5. SQL Server Database ✅ AVAILABLE
**Status**: Legacy database exists
**Action**: Update connection string in `appsettings.Secrets.json`
**Files Affected**: `EmailProfilerDbContext.cs`
**Files Affected**: `MessagingServiceDbContext.cs`
---
@@ -380,7 +380,7 @@ tests/DigitalData.EmailProfiler.Tests/
**Build Command**:
```bash
dotnet build src/DigitalData.EmailProfiler.Infrastructure/DigitalData.EmailProfiler.Infrastructure.csproj
dotnet build src/DigitalData.MessagingService.Infrastructure/DigitalData.MessagingService.Infrastructure.csproj
```
---
@@ -472,10 +472,10 @@ dotnet build src/DigitalData.EmailProfiler.Infrastructure/DigitalData.EmailProfi
**What You Can Do Right Now**:
1. Build the solution: `dotnet build`
2. Review the Domain layer: `src/DigitalData.EmailProfiler.Domain/`
3. Review the Application layer: `src/DigitalData.EmailProfiler.Application/`
4. Review the Infrastructure layer: `src/DigitalData.EmailProfiler.Infrastructure/`
5. Review the API layer: `src/DigitalData.EmailProfiler.API/`
2. Review the Domain layer: `src/DigitalData.MessagingService.Domain/`
3. Review the Application layer: `src/DigitalData.MessagingService.Application/`
4. Review the Infrastructure layer: `src/DigitalData.MessagingService.Infrastructure/`
5. Review the API layer: `src/DigitalData.MessagingService.API/`
**What You Need to Complete**:
1. Add Limilabs.Mail NuGet package: `dotnet add package Limilabs.Mail`