Convert MS Enterprise Library ORM to Dapper

@efanntyo

Hi there Thanks for posting this exciting project. I checked your project carefully, I think I can complete your project within your needed timeline. I am super professional in .NET, C# Programming, Software Development, Database Programming, Microsoft SQL Server, Dapper, Claude Code Please ping , I am always online here Thanks Efanntyo -.

@mykolaslip

Hi there, I’ll tackle converting the six data-access projects from Enterprise Library to Dapper, ensuring no public surface changes and compatibility with .NET Framework 4.8. You’ve already proven the approach with Claude Code, and I’ve spent the last 4 years solving exactly this type of migration, focusing on preserving API signatures while swapping the data access layer. My plan: replace Enterprise Library data access calls with Dapper, keep all public methods and properties unchanged, adapt any batching logic per your guidance, reference the latest Dapper version compatible with .NET Framework 4.8, ensure builds in Visual Studio 2022 with zero warnings, and deliver in one project batch at a time. Deliverables per project: updated source code with Dapper replacements, compiled and compliant to your coding standards document, ready for your functional validation. I’ll align with your templates and migration notes to ensure consistency across all six projects, and I’ll implement a robust approach that minimizes risk while maximizing performance. Best regards,

@Nabbpb

⭐Hello, I certainly understand your goal: migrating six C# data-access projects from Microsoft Enterprise Library to Dapper for .NET Framework 4.8, maintaining all public method signatures and properties exactly, so there are no breaking changes for callers. ✅My approach: I’ll update each project’s source code, replacing Enterprise Library calls with Dapper while keeping everything fully compatible with Visual Studio Community 2022. Each solution will compile cleanly without warnings, following your coding standards, and I’ll deliver them in the agreed-upon batches for your prompt review. I specialize in C# data-access refactoring and have already migrated one project successfully with Claude Code, ensuring a consistent and reliable process across all remaining projects. Past projects include Enterprise Library to Dapper migrations, performance optimizations, and clean refactors for large .NET applications, guaranteeing maintainable, warning-free code. Excited to help port these projects efficiently while keeping your code stable and consistent!

@dmytroy6

Hi there, I understand you need six remaining Enterprise Library-based data-access projects ported to Dapper for .NET Framework 4.8, preserving all public method signatures and public properties, so callers see no breaking changes. I’ve spent the last 8 years solving precisely this kind of migration, ensuring clean builds, stable APIs, and efficient data access. My plan for each project: 1) audit current Enterprise Library usage and contract surfaces; 2) implement a Dapper-based data layer that mirrors public APIs exactly; 3) introduce minimal, well-encapsulated data access wrappers and a small re-usable mapper to keep public signatures intact; 4) ensure the solution compiles cleanly in Visual Studio 2022 with the latest compatible Dapper version for .NET Framework 4.8; 5) batch the rollout per project, with clear migration notes and a non-breaking batching approach; 6) perform lightweight local builds to confirm zero warnings. The process will address the usual challenges, API compatibility, batching behavior, and performance, while delivering maintainable, test-friendly code. What is the exact batching cadence you want for the six-project sequence (e.g., one project per batch, with a fixed review window and optional hotfix batch) and any project-specific constraints I should honor beyond the documents you’ll supply? Thanks, Dmytro

@alexandrd24

Hi, This is a well-scoped migration task and the fact that you've already done one project successfully with a proven approach makes this very straightforward to execute consistently across the remaining six. My background: I work extensively with C# and .NET Framework data-access layers, including migrations away from Enterprise Library. I'm comfortable with Dapper patterns, connection management, parameterised queries, and mapping conventions that keep public signatures intact. Here's how I'll approach each project: I'll follow your existing migration notes and prompts exactly so every project matches the first one you completed. All public method signatures and public properties stay untouched — zero breaking changes for callers. I'll target the most recent Dapper version compatible with .NET Framework 4.8 (currently 2.1.x). Every solution will compile clean in Visual Studio Community 2022 with no warnings before I send it back. Work delivered one project at a time in your agreed batching format so you can review and give the go-ahead before I move to the next. I'll apply your coding standards document consistently from project one through six so the output feels like it came from a single hand. Ready to start as soon as you share the first project, the standards doc, and your migration notes.